Closed
Description
- Test: pummel/test-crypto-timing-safe-equal-benchmarks
- Platform: Linux
- Console Output:
08:05:52 not ok 66 pummel/test-crypto-timing-safe-equal-benchmarks
08:05:52 ---
08:05:52 duration_ms: 6.629
08:05:52 severity: fail
08:05:52 exitcode: 1
08:05:52 stack: |-
08:05:52 assert.js:385
08:05:52 throw err;
08:05:52 ^
08:05:52
08:05:52 AssertionError [ERR_ASSERTION]: timingSafeEqual should not leak information from its execution time (t=7.814360810767208)
08:05:52 at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-custom-suites-freestyle/test/pummel/test-crypto-timing-safe-equal-benchmarks.js:109:1)
08:05:52 at Module._compile (internal/modules/cjs/loader.js:1217:30)
08:05:52 at Object.Module._extensions..js (internal/modules/cjs/loader.js:1238:10)
08:05:52 at Module.load (internal/modules/cjs/loader.js:1066:32)
08:05:52 at Function.Module._load (internal/modules/cjs/loader.js:954:14)
08:05:52 at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
08:05:52 at internal/main/run_main_module.js:17:47 {
08:05:52 generatedMessage: false,
08:05:52 code: 'ERR_ASSERTION',
08:05:52 actual: false,
08:05:52 expected: true,
08:05:52 operator: '=='
08:05:52 }
08:05:52 ...
- Build Links:
https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/15073/console started via https://ci.nodejs.org/job/node-daily-master/1949/
Daily master builds appear to have been consistently broken (for at least as long as we have history (27 May, we only keep a month's worth of results)) due to this test.
Previous issues with this test: