action #48707
closed
Only parse logs in detect_yast2_failures instead of conducting full installation for online medium
Added by riafarov about 5 years ago.
Updated about 3 years ago.
Description
Motivation¶
We use RAID0 as a base test and then parse logs. Instead of repeating same installation steps twice, we should simply publish set of logs for RAID0 job and only parse them to detect if there are any new errors.
We can either chain jobs, boot into installed system and parse logs there, or publish logs as an asset and parse them either directly on the worker (might not work), or boot into any image (even support server) and parse logs there using same tools as before.
NOTE: we cannot optimize this scenario for the Full medium, as we do not execute RAID tests there
Acceptance criteria¶
- For online medium logs are parsed without conduction of the full installation
hm, is it worth the effort? Is it technically feasible in the scenarios where we run it, e.g. "bare-metal" or s390x z/VM? If it's about saving reviewer times then I suggest to schedule the detect_yast2_failures simply after RAID0 with START_AFTER_TEST
- Target version changed from Milestone 26 to future
- Project changed from openQA Tests to qe-yam
- Subject changed from [functional][y] Only parse logs in detect_yast2_failures instead of conducting full installation to Only parse logs in detect_yast2_failures instead of conducting full installation
- Category deleted (
Enhancement to existing tests)
- Subject changed from Only parse logs in detect_yast2_failures instead of conducting full installation to Only parse logs in detect_yast2_failures instead of conducting full installation for online medium
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to syrianidou_sofia
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF