ci: detect errors only from stderr #128
Merged
Conversation
This file contains 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
Search for potential errors only in the kernel logs and the scheduler stderr. In this way we can use "error keywords" in the scheduler's output without triggering false positives in the CI (see for example #127). NOTE: this works, because virtme-ng, when executed in verbose mode, sends the kernel messages to stderr (together with the command's stderr) and it channels the command's stdout to the stdout of the host. Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
htejun
approved these changes
Feb 5, 2024
Byte-Lab
approved these changes
Feb 5, 2024
lol you guys approved it and I don't even know if it works. Well, in theory it should work... let's wait for the current run to complete, if CI is happy I'll merge this. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Search for potential errors only in the kernel logs and the scheduler stderr.
In this way we can use "error keywords" in the scheduler's output without triggering false positives in the CI (see for example #127).
NOTE: this works, because virtme-ng, when executed in verbose mode, sends the kernel messages to stderr (together with the command's stderr) and it channels the command's stdout to the stdout of the host.