-
Notifications
You must be signed in to change notification settings - Fork 28.7k
-
Notifications
You must be signed in to change notification settings - Fork 28.7k
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
errors & strange traces in linux build #142572
errors & strange traces in linux build #142572
Comments
Same here and just when I updated too.
will need to look into rolling back version if this isn't fixed by morning please let me know if I can help in any way |
@EricTulowetzke the issue you are facing should be fixed with latest insiders, please give it a try. Thanks! |
@deepak1556 please see 7dbd736 for a change to disable crash reporting in Linux CI. |
Oh and also in smoke tests: 5faea71 |
thanks @bpasero :) |
dbus errors continues with the crash reporter disabled, one of the recent runs https://dev.azure.com/monacotools/Monaco/_build/results?buildId=156012 after the above commits. I will continue to investigate this via the Electron 17 branch, the errors are harmless and looks like we will need the crash reporter back on in the azure CI to capture a recent regression in the native-keymap module https://vscodeteam.slack.com/archives/C1Y427SES/p1644923219041849?thread_ts=1644922937.657609&cid=C1Y427SES @bpasero can we revert your above commits ? |
@deepak1556 ok I have pushed 2 reverts, however one thing to keep in mind is that on Linux at least I see dozens of crash dumps being attached as artefacts and I wonder if that slows down the CI sufficient enough that we end up in our timeouts. Have we figured out what these crash dumps actually are? I am referring to #143000 |
Just looked into them, they are related to this issue. All of them have crash when attempting to connect with dbus,
I will push up this issue to be tackled this iteration as it does make our builds flaky, will look into why the connection failes. |
👏 |
https://dev.azure.com/monacotools/Monaco/_build/results?buildId=154859&view=logs&j=963754b8-394e-5caf-de5d-2790b068caec&t=6b00722f-1101-5770-9e0c-f427af83d823
The text was updated successfully, but these errors were encountered: