- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 115
Skip memory assignment on domain still starting #712
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
| 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 testsPerformance 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)