-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing
-
None
-
None
-
Developer Tools
Under Node.js nightly builds (v26+) on the linux_node_nightly Evergreen variant (ubuntu2004), two native addons misbehave:
- glibc-version: dlsym for gnu_get_libc_version returns null, so mongosh --build-info reports runtimeGlibcVersion: "N/A" even though Node's own process.report still sees the host's glibc.
- native-machine-id: throws on load, causing the telemetry deviceId to fall back to the literal string "unknown".
Both point at the same loader/dlsym behavior under the prebuilt nightly binary, so they likely share a root cause (ABI/N-API mismatch or symbol lookup change in Node v26).
The corresponding e2e tests are currently skipped under process.version.includes('-nightly'):
- packages/e2e-tests/test/e2e.spec.ts — --build-info JSON test
- packages/e2e-tests/test/e2e.spec.ts — sets device ID for telemetry
Investigate the addons' loader behavior under the nightly prebuilt binary and re-enable the tests.
Follow-up from MONGOSH-2969.