Skip to content
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

Automated tests: display openQA 'machine' rather than arch #5533

Merged
merged 2 commits into from
Nov 24, 2023

Conversation

AdamWill
Copy link
Contributor

In the little lozenges we show on the Automated Tests tab rows to differentiate multiple runs of the same test case, currently we show 'arch' and 'flavor' for openQA tests. However, this doesn't sufficiently distinguish some tests: e.g.
install_default_update_netinst, which is run on both BIOS and UEFI on x86_64. Both of these are listed as
"x86_64 everything-boot-iso" at present.

This makes us display the openQA "machine" instead of the arch, if we can determine it (from the scenario). As "machine" will always be more distinguishing than "arch" when present, we don't show "arch" if we can find "machine".

This will make the two install_default_update_netinst runs show as "64bit everything-boot-iso" and "uefi everything-boot-iso". Other tests will also now show "64bit" (the x86_64 BIOS 'machine' name in openQA) rather than "x86_64", which might be a bit more confusing I guess; if that's a problem, we can consider changing the machine names in openQA to something clearer like "x86_64-uefi" and "x86_64-bios" or something, I'd just have to think about what other things might need changing in that case.

In the little lozenges we show on the Automated Tests tab rows
to differentiate multiple runs of the same test case, currently
we show 'arch' and 'flavor' for openQA tests. However, this
doesn't sufficiently distinguish some tests: e.g.
install_default_update_netinst, which is run on both BIOS and
UEFI on x86_64. Both of these are listed as
"x86_64 everything-boot-iso" at present.

This makes us display the openQA "machine" instead of the arch,
if we can determine it (from the scenario). As "machine" will
always be more distinguishing than "arch" when present, we
don't show "arch" if we can find "machine".

This will make the two install_default_update_netinst runs show
as "64bit everything-boot-iso" and "uefi everything-boot-iso".
Other tests will also now show "64bit" (the x86_64 BIOS 'machine'
name in openQA) rather than "x86_64", which might be a bit more
confusing I guess; if that's a problem, we can consider changing
the machine names in openQA to something clearer like
"x86_64-uefi" and "x86_64-bios" or something, I'd just have to
think about what other things might need changing in that case.

Signed-off-by: Adam Williamson <[email protected]>
@AdamWill AdamWill requested a review from a team as a code owner November 17, 2023 18:04
Copy link
Contributor

@mattiaverga mattiaverga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Test failures are unrelated (still need to find some time to understand what recent update in Rawhide/F39 started the failures - my 2cents are on python-sqlalchemy 1.4.50)

@mergify mergify bot merged commit cf96d56 into fedora-infra:develop Nov 24, 2023
31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants