Source: node-foreground-child
Version: 1.5.6-4
Severity: serious
Some recent change in unstable makes node-foreground-child FTBFS:
https://tests.reproducible-builds.org/debian/history/node-foreground-child.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-foreground-child.html
...
# Subtest: test/immortal-child.js
not ok 1 - should match pattern provided
---
found:
out: ''
err: ''
code: null
signal: SIGINT
pattern:
out: >-
/^(child alive\n)*child SIGINT received\n(child
alive\n)*child exit null
SIGTERM\n$/
err: /^parent \d+\nchild \d+\n$/
code: null
signal: SIGTERM
at:
line: 37
column: 7
file: test/immortal-child.js
type: ChildProcess
stack: |
ChildProcess. (test/immortal-child.js:37:7)
source: |
t.match(actual, expect)
...
1..1
# failed 1 test
# time=224.905ms
