Test
test-crypto-key-objects
Platform
Linux x64
Console output
13:36:25 not ok 2003 parallel/test-crypto-key-objects
13:36:25 ---
13:36:25 duration_ms: 120.45
13:36:25 severity: fail
13:36:25 exitcode: -15
13:36:25 stack: |-
13:36:25 timeout
13:36:25 ...
Build links
Additional information
(CI links are restricted for the moment until the in progress security releases are done. We're seeing this test fail for v16.x while preparing the v16.x release (I'll post more information when the CI embargo is lifted) but it doesn't appear to be related to the security patches.)
Test usually completes quickly, so it's not a case of extending the timeout. Also we've manually reproduced the failure on one of the CI machines with the test harness test.py test/parallel/test-crypto-key-objects.js so is unlikely to be due to parallelism with other tests/resolved by moving the test to sequential.
@BethGriggs has pointed out that the test has previously timed out in earlier v16.x PRs: nodejs/reliability#451
Test
test-crypto-key-objects
Platform
Linux x64
Console output
Build links
Additional information
(CI links are restricted for the moment until the in progress security releases are done. We're seeing this test fail for v16.x while preparing the v16.x release (I'll post more information when the CI embargo is lifted) but it doesn't appear to be related to the security patches.)
Test usually completes quickly, so it's not a case of extending the timeout. Also we've manually reproduced the failure on one of the CI machines with the test harness
test.py test/parallel/test-crypto-key-objects.jsso is unlikely to be due to parallelism with other tests/resolved by moving the test to sequential.@BethGriggs has pointed out that the test has previously timed out in earlier v16.x PRs: nodejs/reliability#451