-
Notifications
You must be signed in to change notification settings - Fork 1.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
Nightly Dotty workflow of 2023-12-18 failed #19285
Comments
|
This was caused by 10f2c10. |
I seems that 10f2c10 was not the cause after all. See #19289 (comment). |
This issue started with 1f7aa24. We need to clean the project to reproduce the issue. |
Follow up of scala#19182. Using `fullName` causes the the `parallelBackend` tests to loop forever. Fixes scala#19285 Fixes scala#19281 Fixes scala#19278
This issue is spurious. I am not sure if 1f7aa24 started it anymore. I will need to test this in depth. |
Executing
showed with more confidence that the issue comes from 2dcd64a |
This reverts commit 2dcd64a. This caused the the `parallelBackend` tests to loop forever. Fixes scala#19285 Fixes scala#19281 Fixes scala#19278
This reverts commit 2dcd64a. This caused the `parallelBackend` tests to loop forever. Fixes scala#19285 Fixes scala#19281 Fixes scala#19278
I have spurious parallel backend failures in my local runs all the time (maybe one in three runs fails). I suspect a race condition in parallel backend. What is the status of it? Do we run that in production? |
#19290 fixes the issue on the CI. However, we should try to figure out why accessing the symbol of an enum there fails with a race condition. |
I can't see how such a commit could make any difference if parallel backend would not have some underlying race problems. |
I assume it is only triggering the issue much more often. |
See https://github.com/lampepfl/dotty/actions/runs/7243042276
The text was updated successfully, but these errors were encountered: