feat: Store Logs from CI Runs for Debugging and Offline Analysis - #115
Merged
Conversation
anokfireball
force-pushed
the
feat/ci-emergency-logging
branch
2 times, most recently
from
August 5, 2025 05:21
30d5efb to
36cb834
Compare
longer initial boot timeouts, shorter post-migration timeouts
anokfireball
force-pushed
the
feat/ci-emergency-logging
branch
from
August 5, 2025 05:47
36cb834 to
91152e9
Compare
toanju
approved these changes
Aug 5, 2025
fwiesel
self-requested a review
August 5, 2025 06:57
fwiesel
approved these changes
Aug 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After successfully failing to debug or reproduce yesterday's CHV failure, let's store some logs from the tests for offline analysis/comparison to working states/debugging. Unfortunately, CHV via libvirt does not yet support logging the serial console.
I also adjusted the VM startup timeouts a bit: Give more time on initial boot should this take longer (e.g. due too runner VM contention) and less time after migration (they are live migrations, so it should be instantaneous).