-
Notifications
You must be signed in to change notification settings - Fork 102
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
All problems in computer science can be solved by another level of indirection #3613
Conversation
Doesn't help. :( https://github.com/canonical/mir/actions/runs/11035413503/job/30651347065?pr=3613
...and https://github.com/canonical/mir/actions/runs/11035413503/job/30651343458?pr=3613
(Not a big sample, but did this actually make things WORSE?) |
8af5d1b
to
a4fabf3
Compare
A clean run twice! "That alone should encourage the crew..." |
'fraid not: https://github.com/canonical/mir/actions/runs/11037356604/job/30683939003?pr=3613
|
Still no
But this bit is interesting:
The previous server seems to be hanging about still? So you'd be right that it could be a shutdown (or a parallel test?) issue |
That shouldn't be an issue. That message happens whenever libwayland-server is searching for a socket to offer |
ad51d32
to
ab024f2
Compare
4978922
to
3367f71
Compare
The tests that have failed:
So both |
[Sigh!] I was beginning to hope I'd guessed a solution. But... fe1c4b8 failed once in four spread runs:
|
Just seen this:
I wonder if there's a segfault lurking in the testing stack that this test just happens to trigger |
5400e0d passed 5 repeats of the spread action without seeing this problem |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, yes!
The
miral::ConfigFile
"Watcher" can be destroyed before the main loop invokes the handler it supports. So add another level of indirection to check it is still there.Plus some hygienic improvements to the test fixture.
Fixes: #3612