-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Task times out on the terminal smoke tests #223490
Comments
Crash stack shows the pty module was waiting on the exit status of the process
While the main thread aborted
|
I am not sure what could have caused this state, but the only change that might be relevant was electron/electron@f3cc8cb which came in with the Electron update 2 days ago #222756. I will revert the update for now since I will be out next week and revisit this in August. |
Change has been reverted, adjusting labels accordingly. I will keep this issue open to track the root cause and bring back the update in August. |
Still failing with the revert |
CI runs have been stable after triggering an insiders with the reverted change, so maybe it was a false alarm. Will watch for the next failure. PR pipeline failed on the reverted commit https://monacotools.visualstudio.com/Monaco/_build/results?buildId=284901&view=results Both use the same linux build agents and both of them did recompile the native modules, there should be no difference in module headers since they use the same electron version. Given the failure was linux specific, I was wondering if io_uring got reenabled since we know pty module does not work well in this mode. But I don't see any changes in the runtime related, also given only smoke tests are affected points that might not be the case. @Tyriar if you have the chance please try the smoke tests on the commit before the revert locally and let me know if the failures are consistent. |
Merging to #216564 |
Smoke tests regularly fails with the error:
Example build: https://dev.azure.com/monacotools/Monaco/_build/results?buildId=284839&view=logs&j=7a91b4be-20b5-51ee-04c3-33f03492145f&t=3255846e-ed0b-5948-a22e-d5f1a1fdd237
The text was updated successfully, but these errors were encountered: