Use Case

As a Node.js engineer
I want consistently green CI runs
So that I can ensure tests are covering real-world usage and correct code

Examples

• https://github.com/mongodb-js/mongodb-client-encryption/actions/runs/10167591009/job/28120331788

    addMongoOperationResponse
      ✔ throws if called with a non-Uint8Array
/Users/runner/work/_temp/0d62a77a-bdfa-41c6-b245-ab59a1bfa64a.sh: line 1:  5112 Abort trap: 6           npm run test
Error: Process completed with exit code 134.

• https://github.com/mongodb-js/mongodb-client-encryption/actions/runs/10167591009/job/28124784074

addMongoOperationResponse
      ✔ throws if called with a non-Uint8Array
/c/hostedtoolcache/windows/node/22.5.1/x64/npm: line 65:  1515 Segmentation fault      "$NODE_EXE" "$NPM_CLI_JS" "$@"
Error: Process completed with exit code 139.

User Impact

• Unknown but probably low to zero.
  • We have run the bindings sourced from the new repo 100s of times since https://github.com/mongodb/node-mongodb-native/pull/4141 merged and never observed a segfault in driver CI. We install directly from the repo in the "custom dep" variant, and use the linux prebuilds in our normal linux node.js matrix.

Dependencies

• GHA CI

Unknowns

• Why do the tests segfault? How do we collect more information about the segfault.

Acceptance Criteria

Implementation Requirements

• Determine the source of the issue and investigate mitigations

Testing Requirements

• Tests should consistently run to completion and pass.

Documentation Requirements

• None

Follow Up Requirements

• None