Version
24.21.0
Platform
Linux lal 7.2.8+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 7.2.8-1 (2026-09-26) x86_64 GNU/Linux
Subsystem
tests, uv
What steps will reproduce the bug?
Run parallel/test-uv-errmap, parallel/test-uv-errno
How often does it reproduce? Is there a required condition?
Not sure, may be when shared libuv1 is built before the symbol for EFTYPE is defined,
then build nodejs when the symbol after EFTYPE is defined.
What is the expected behavior? Why is that the expected behavior?
I think the problem lies in the fact that nodejs copies uv errors codes at build time.
What do you see instead?
Two tests failures
not ok 3930 parallel/test-uv-errmap
duration_ms: 70.42400
severity: fail
exitcode: 1
stack: |-
node:assert:152
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ 'EFTYPE'
- 'Unknown system error -134'
at /tmp/tmp.1Ynu00pL9e.nodejs/test/parallel/test-uv-errmap.js:23:10
at Array.forEach (<anonymous>)
at Object.<anonymous> (/tmp/tmp.1Ynu00pL9e.nodejs/test/parallel/test-uv-errmap.js:17:8)
at Module._compile (node:internal/modules/cjs/loader:1929:14)
at Object..js (node:internal/modules/cjs/loader:2060:10)
at Module.load (node:internal/modules/cjs/loader:1651:32)
at Module._load (node:internal/modules/cjs/loader:1443:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 'EFTYPE',
expected: 'Unknown system error -134',
operator: 'strictEqual',
diff: 'simple'
}
Node.js v24.21.0
...
not ok 3931 parallel/test-uv-errno
duration_ms: 69.43600
severity: fail
exitcode: 1
stack: |-
node:assert:152
throw new AssertionError(obj);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
+ actual - expected
+ 'EFTYPE'
- 'Unknown system error -134'
at /tmp/tmp.1Ynu00pL9e.nodejs/test/parallel/test-uv-errno.js:25:10
at Array.forEach (<anonymous>)
at Object.<anonymous> (/tmp/tmp.1Ynu00pL9e.nodejs/test/parallel/test-uv-errno.js:19:6)
at Module._compile (node:internal/modules/cjs/loader:1929:14)
at Object..js (node:internal/modules/cjs/loader:2060:10)
at Module.load (node:internal/modules/cjs/loader:1651:32)
at Module._load (node:internal/modules/cjs/loader:1443:12)
at wrapModuleLoad (node:internal/modules/cjs/loader:261:19)
at Module.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:154:5)
at node:internal/main/run_main_module:33:47 {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 'EFTYPE',
expected: 'Unknown system error -134',
operator: 'strictEqual',
diff: 'simple'
}
Node.js v24.21.0
Additional information
node is build with --shared-uv.
Version
24.21.0
Platform
Subsystem
tests, uv
What steps will reproduce the bug?
Run parallel/test-uv-errmap, parallel/test-uv-errno
How often does it reproduce? Is there a required condition?
Not sure, may be when shared libuv1 is built before the symbol for EFTYPE is defined,
then build nodejs when the symbol after EFTYPE is defined.
What is the expected behavior? Why is that the expected behavior?
I think the problem lies in the fact that nodejs copies uv errors codes at build time.
What do you see instead?
Two tests failures
not ok 3930 parallel/test-uv-errmap
duration_ms: 70.42400
severity: fail
exitcode: 1
stack: |-
node:assert:152
throw new AssertionError(obj);
^
...
not ok 3931 parallel/test-uv-errno
duration_ms: 69.43600
severity: fail
exitcode: 1
stack: |-
node:assert:152
throw new AssertionError(obj);
^
Additional information
node is build with --shared-uv.