Skip memory assignment on domain still starting#712
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #712 +/- ##
==========================================
- Coverage 70.53% 70.41% -0.12%
==========================================
Files 61 61
Lines 13546 13516 -30
==========================================
- Hits 9554 9517 -37
- Misses 3992 3999 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025080604-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=2025061004-4.3&flavor=update
Failed tests9 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/142375#dependencies 10 fixed
Unstable testsDetailsPerformance TestsPerformance degradation:9 performance degradations
Remaining performance tests:164 tests
|
|
Looking at the test run at https://openqa.qubes-os.org/tests/148784#live I still see a bunch of "Failed to set memory" messages, but no traceback anymore. It's still in progress, but I think it will finish soon. |
For: QubesOS/qubes-issues#1512
This does not fix all cases of Failed to set memory (but lowers it a lot) and does fix the TypeError exception being raised when
mem_usedisNone: #708 (comment)