Add record_info for each test case #5807
Conversation
mloviska
commented
Sep 20, 2018
mloviska
commented
- Related ticket: poo#33160
- Verification runs:
- sle-12-SP4-Server-DVD-x86_64-Build0393-btrfs+warnings@64bit
- sle-15-SP1-Installer-DVD-x86_64-Build43.1-btrfs+warnings@64bit
mloviska
force-pushed
the
partition_warnings
branch
from
4bc116f
to
c248f59
Compare
| process_warning(warning => 'no-space-for-kernel', key => 'alt-o'); | ||
| remove_partition; | ||
|
|
||
| ## Add wrong or small boot partition | ||
| foreach (keys %roles) { |
There was a problem hiding this comment.
Ok, missed that in VR, this introduces weird behavior, as we test boot/zipl and ofw on x86_64, which is non-sense. I will add this to the follow up ticket we have in the next sprint.
There was a problem hiding this comment.
In fact, that was an intention to check if the partitioner will trigger a warning when there is wrong boot partition ID.
There was a problem hiding this comment.
You mean that we create /boot/zipl on x86_64 and check if there is still warning about bios_boot? I guess it's a bit of overkill, considering stability and scalability of our GUI tests =(
There was a problem hiding this comment.
Technically, user should be warned when the boot partition does not match the arch. Storage-ng checks the size for all boot partition IDs and for some it checks either ID or mount point or file system, depending on what kind of arch we are running the installer. Also the warning message is still the same, so from the point of stability, we are expecting the same needle to appear for each boot partition ID on tested architecture.
