test-string-decoder failing regularly on arm

[mhdawson]

• Version: master
• Platform: arm
• Subsystem:

What steps will reproduce the bug?

Run CI on PR

How often does it reproduce? Is there a required condition?

From runs today looks like most failed with that error

What is the expected behavior?

tests pass

What do you see instead?

node:assert:577
      throw err;
      ^

AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

+ Comparison {}
- Comparison {
-   code: 'ERR_STRING_TOO_LONG'
- }
    at Object.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-string-decoder.js:204:8)
    at Module._compile (node:internal/modules/cjs/loader:1108:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10)
    at Module.load (node:internal/modules/cjs/loader:973:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
    at node:internal/main/run_main_module:17:47 {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: RangeError: Array buffer allocation failed
      at new ArrayBuffer (<anonymous>)
      at new Uint8Array (<anonymous>)
      at new FastBuffer (node:internal/buffer:957:5)
      at Function.alloc (node:buffer:362:10)
      at assert.throws.code (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-string-decoder.js:205:42)
      at getActual (node:assert:700:5)
      at Function.throws (node:assert:840:24)
      at Object.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-string-decoder.js:204:8)
      at Module._compile (node:internal/modules/cjs/loader:1108:14)
      at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10),
  expected: { code: 'ERR_STRING_TOO_LONG' },
  operator: 'throws'
}

Additional information

[mhdawson]

Most recent change to the test: #36661

[mhdawson]

Looks like arm was not in the CI when #36661 was landed.

[mhdawson]

Well past my end of day but was sticking around to try and get #36478 landed before there were conflicts.

@targos unless you have an easy fix for the new test I suggest we revert #36661 so that we can get the CI passing in on ARM again.

[mhdawson]

A better option might be to just disable the test for ARM. I've not looked too closely at the test yet but I'm guessing it may just be using too much memory for the PIs'. If that makes sense I'm happy to open a PR to skip for ARM unless somebody else beats me to it.

[PoojaDurgad]

similar failure reported here as well: https://ci.nodejs.org/job/node-test-binary-arm-12+/8818/RUN_SUBSET=0,label=pi3-docker/console

[targos]

fix in #36795