You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
Activity
richardlau commentedon Apr 25, 2024
Given this stack trace
11:19:53 at main (/home/iojs/build/workspace/node-test-commit-linux/benchmark/crypto/timingSafeEqual.js:21:10)this is most likely going to be for the same reason as #38226.
jakecastelli commentedon Jun 14, 2024
Flaky again here in this PR
see Detail
test: mark `test-benchmark-crypto` as flaky
test: mark `test-benchmark-crypto` as flaky
github-actions commentedon May 22, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
trivikr commentedon Jul 16, 2026
Closing as last time this test was flaky was in Aug 2024
https://github.com/nodejs/reliability/issues?q=sort%3Aupdated-desc%20is%3Aissue%20state%3Aopen%20test-benchmark-crypto%20AssertionError
test: deflake test-benchmark-crypto
test: deflake test-benchmark-crypto
test: deflake test-http2-debug
test: deflake test-benchmark-crypto
test: deflake test-http2-debug