-
-
Notifications
You must be signed in to change notification settings - Fork 76
Apply fix for quick network reconnect after backend destroy #1193
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
Conversation
d1c8da5 to
fa30238
Compare
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025103005-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025081011-4.3&flavor=update
Failed tests19 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/149225#dependencies 82 fixed
Unstable testsDetailsPerformance TestsPerformance degradation:13 performance degradations
Remaining performance tests:165 tests
|
Didn't help :( |
fa30238 to
e151ced
Compare
3968b6c to
9483bfe
Compare
9483bfe to
de2472c
Compare
|
PipelineRetry |
0761190 to
d119ef7
Compare
d119ef7 to
b7af870
Compare
This especially is relevant for paused VMs (like preloaded disposables). If backend was restarted while frontend was paused, qubesd will attempt to reconnect it on unpause, which will trigger the race condition.
b7af870 to
2b1f93a
Compare
This especially is relevant for paused VMs (like preloaded disposables).
If backend was restarted while frontend was paused, qubesd will attempt
to reconnect it on unpause, which will trigger the race condition.