action #95117
closed[qe-core] figure out how to reduce the dependencies on other team's scenarios/test modules.
0%
Description
partitioning_raid module should not be in use. (ping george)
Updated by szarate almost 3 years ago
- Related to action #90329: [qe-core] 15SP2 QU - test fails in raid_gpt on ppc64le added
Updated by geor almost 3 years ago
- Status changed from New to Workable
- Assignee set to geor
Updated by geor almost 3 years ago
- Description updated (diff)
Turns out partitioning_raid is (only) used in some other QR jobs (both for 15-SP2 and 15-SP3) just not failing (yet). There will be actual progress on this side with an upcoming QU.
For now I will do some research on avoiding our schedules having modules that at some point get deprecated by other squads. My direction will be however to do this by increasing our dependency to other squads' scenarios instead of decreasing it, at least for the QU. I will follow up later with more info.
Updated by szarate almost 3 years ago
geor wrote:
Turns out
partitioning_raidis (only) used in some other QR jobs (both for 15-SP2 and 15-SP3) just not failing (yet). There will be actual progress on this side with an upcoming QU.For now I will do some research on avoiding our schedules having modules that at some point get deprecated by other squads. My direction will be however to do this by increasing our dependency to other squads' scenarios instead of decreasing it, at least for the QU. I will follow up later with more info.
That's a good approach, the main part here is to avoid running deprecated code.
Updated by okurz almost 3 years ago
- Category set to Enhancement to existing tests
Updated by apappas over 2 years ago
- Assignee set to szarate
Santiago please link the ticket from the yast team.
Updated by slo-gin over 1 year ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.
Updated by szarate over 1 year ago
- Status changed from Workable to Rejected
In the meantime we fixed this by moving away from having installation scenarios using legacy installer