-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Apply workaround for highstate rendering failure #28
Conversation
Unbreak salt using dirty hack, until upstream applies the proper fix. This is executed in a DispVM, so the change is not persistent - when upstream fix will be there, it's enough to simply drop this line. Workaround for saltstack/salt#60003 Fixes QubesOS/qubes-issues#6580
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/17327#dependencies Failed tests
New failuresCompared to: https://openqa.qubes-os.org/tests/12774#dependencies
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/12774#dependencies
|
I wonder if we should check the explicit |
I intentionally didn't do that, so I don't need to update it whenever new update without the fix appears. The change should not be that harmful even if the problem gets fixed somewhere else - it just disables some of the caching. And the pattern should be unique enough to not hit other places in the file. |
Unbreak salt using dirty hack, until upstream applies the proper fix.
This is executed in a DispVM, so the change is not persistent - when
upstream fix will be there, it's enough to simply drop this line.
Workaround for saltstack/salt#60003
Fixes QubesOS/qubes-issues#6580