-
Notifications
You must be signed in to change notification settings - Fork 36
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
Get list of installer image packages when probing boot.iso #1229
Get list of installer image packages when probing boot.iso #1229
Conversation
/test-os-variants |
006ad59
to
31837f4
Compare
/test-os-variants |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very useful thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Just a question below.
ISO_PACKAGES=$(echo "${output}" | grep 'PACKAGES=') | ||
ISO_PACKAGES="${ISO_PACKAGES##PACKAGES=}" | ||
echo Saving list of installer image packages to /var/tmp/kstest-image-packages.log | ||
echo $ISO_PACKAGES | tr ' ' '\n' | tee /var/tmp/kstest-image-packages.log |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I read this correctly then the list of packages will get printed to stdout. If this is correct I think it would spam the test results a lot wouldn't it? Isn't it enough to just store the list?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the tests pass, you do not need to worry about extra lines in the output, if there is a failure it might be handy to see the package versions right in the test output. I actually like it this way :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in this case it is handy to have this in the main log output without need of making sure we really pass / gather all the required logs (for example in GH actions). Also it is maybe more discoverable this way. Actually this information is very important when dealing with integration tests failures so let's make it as easily accessible as possible.
Yes, it seems to me that it creates a mess in GH actions console output: I think we should remove use of |
ISO_PACKAGES=$(echo "${output}" | grep 'PACKAGES=') | ||
ISO_PACKAGES="${ISO_PACKAGES##PACKAGES=}" | ||
echo Saving list of installer image packages to /var/tmp/kstest-image-packages.log | ||
echo $ISO_PACKAGES | tr ' ' '\n' | tee /var/tmp/kstest-image-packages.log |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the tests pass, you do not need to worry about extra lines in the output, if there is a failure it might be handy to see the package versions right in the test output. I actually like it this way :-)
I already replied earlier, also given we even already have the debugging shell output above I don't see it as a problem. |
You can see the change in action in the /test-os-variants workflow of this PR, step "Run kickstart tests in container" (near "Saving list of installer image packages to /var/tmp/kstest-image-packages.log")
or in logs / artefacts of the workflow (eg logs-daily-iso) where you can find kstest-image-packages.log.