-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: CI
-
None
-
3
-
Iteration Xantic Sargo
-
Not Needed
Problem Statement/Rationale
What is going wrong? What action would you like the Engineering team to take?
Please be sure to attach relevant logs with any sensitive data redacted.
CI randomly fails with the error: https://github.com/mongodb-js/vscode/actions/runs/4059474537/jobs/6987553352#step:9:1085
Steps to Reproduce
How could an engineer replicate the issue you’re reporting?
Run CI on GitHub and observe the following error:
Cannot call write after a stream was destroyed: Error: Cannot call write after a stream was destroyed
1 failing
at __node_internal_captureLargerStackTrace (node:internal/errors:464:5)
1) Telemetry Controller Test Suite
at new NodeError (node:internal/errors:371:5)
track aggregation exported to language:
at errorBuffer (node:internal/streams/writable:517:14)
TypeError: Cannot read properties of null (reading 'args')
at afterWrite (node:internal/streams/writable:501:5)
at Context.<anonymous> (d:\a\vscode\vscode\out\test\suite\telemetry\telemetryService.test.js:240:58)
at onwrite (node:internal/streams/writable:477:7)
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:87:12)
[main 2023-02-01T00:11:11.273Z] Waiting for extension host with pid 1188 to exit.
[main 2023-02-01T00:11:12.965Z] Extension host with pid 1188 exited with code: 0, signal: null.
Exit code: 1
Failed to run tests:
Failed
Failed with exit code: 1
Output:
Error: Process completed with exit code 127.
Expected Results
What do you expect to happen?
CI is green.
Actual Results
What do you observe is happening?
CI fails.
Additional Notes
Any additional information that may be useful to include.