test-hash-seed failing (consistently?) on rhel8

[aduh95]

Test

pummel.test-hash-seed

Platform

No response

Console output

not ok 3986 pummel/test-hash-seed
  ---
  duration_ms: 68409.43500
  severity: fail
  exitcode: 1
  stack: |-
    node:internal/errors:983
      const err = new Error(message);
                  ^
    
    Error: Command failed: /home/iojs/build/workspace/node/out/Release/node --allow-natives-syntax /home/iojs/build/workspace/node/test/fixtures/guess-hash-seed.js
    /home/iojs/build/workspace/node/test/fixtures/guess-hash-seed.js:163
      throw new Error('no candidates remaining');
      ^
    
    Error: no candidates remaining
        at Object.<anonymous> (/home/iojs/build/workspace/node/test/fixtures/guess-hash-seed.js:163:9)
        at Module._compile (node:internal/modules/cjs/loader:1738:14)
        at Object..js (node:internal/modules/cjs/loader:1903:10)
        at Module.load (node:internal/modules/cjs/loader:1473:32)
        at Function._load (node:internal/modules/cjs/loader:1285:12)
        at TracingChannel.traceSync (node:diagnostics_channel:322:14)
        at wrapModuleLoad (node:internal/modules/cjs/loader:234:24)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:151:5)
        at node:internal/main/run_main_module:33:47
    
    Node.js v24.0.0-pre
    
        at genericNodeError (node:internal/errors:983:15)
        at wrappedFn (node:internal/errors:537:14)
        at ChildProcess.exithandler (node:child_process:414:12)
        at ChildProcess.emit (node:events:507:28)
        at maybeClose (node:internal/child_process:1101:16)
        at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
      code: 1,
      killed: false,
      signal: null,
      cmd: '/home/iojs/build/workspace/node/out/Release/node --allow-natives-syntax /home/iojs/build/workspace/node/test/fixtures/guess-hash-seed.js',
      stdout: '',
      stderr: '/home/iojs/build/workspace/node/test/fixtures/guess-hash-seed.js:163\n' +
        "  throw new Error('no candidates remaining');\n" +
        '  ^\n' +
        '\n' +
        'Error: no candidates remaining\n' +
        '    at Object.<anonymous> (/home/iojs/build/workspace/node/test/fixtures/guess-hash-seed.js:163:9)\n' +
        '    at Module._compile (node:internal/modules/cjs/loader:1738:14)\n' +
        '    at Object..js (node:internal/modules/cjs/loader:1903:10)\n' +
        '    at Module.load (node:internal/modules/cjs/loader:1473:32)\n' +
        '    at Function._load (node:internal/modules/cjs/loader:1285:12)\n' +
        '    at TracingChannel.traceSync (node:diagnostics_channel:322:14)\n' +
        '    at wrapModuleLoad (node:internal/modules/cjs/loader:234:24)\n' +
        '    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:151:5)\n' +
        '    at node:internal/main/run_main_module:33:47\n' +
        '\n' +
        'Node.js v24.0.0-pre\n'
    }
    
    Node.js v24.0.0-pre
  ...

Build links

• https://ci.nodejs.org/job/node-test-commit-linux/62679/nodes=rhel8-x64/console
• https://ci.nodejs.org/job/node-test-commit-linux/62653/nodes=rhel8-x64/console
• https://ci.nodejs.org/job/node-test-commit-linux/62678/nodes=rhel8-x64/
• https://ci.nodejs.org/job/node-test-commit-linux/62675/nodes=rhel8-x64/console

Additional information

No response

[targos]

Do we know if it's caused by a recent commit to main ?

[targos]

I don't know if it will help but I updated and rebooted all rhel8 machines.

[targos]

There are two green runs now.

[aduh95]

I think we can be confident the test is not flaky then