Quite a big part of openQA is testing the installation of SUSE products. All of them are installed by YaST. So a big quantity of problems found during openQA testruns are YaST problems.
To find out what has gone wrong during installation YaST developers need to download the tarball containing the logs, unpack it and find the y2log among many other log files. That makes it quite complicated to just have a quick view on a problem.
To speed that up I want to implement an automated unpack-and-show functionality right in the openQA WebUI to be able to just point and click onto a y2log to show it – ideally including error-level highlighting and a simple filter and search mechanism.
Looking for hackers with the skills:
This project is part of:
Hack Week 16
Activity
Comments
-
over 4 years ago by okurz | Reply
I don't want to discourage you but aren't our openQA tests already doing that? E.g. take a look in https://openqa.suse.de/tests/1245564#step/select_patterns_and_packages/145
What is done here is that the y2log file is parsed within the SUT for curious sections and likely errors and presenting these as text popup windows from which one can also easily copy-paste
Similar Projects
Learn PostgreSQL advanced features by okurz
Motivation
The PostgreSQL database implement...
Give back to Wezterm by mpagot
[comment]: # (Please use the project descriptio...
Having closer look at openQA and search for comparably simple improvement options by clanig
Project Description
The project is about ge...
Weekly balanced family menu planner (learn JS, Node.JS, React, MongoDB) by pherranz
Project Description
We're always struggling...
Port the Minion job queue to TypeScript by kraih
Project Description
As part of the [mojo....
YaST log grouping, better visualization of the log by lslezak
Description
TL;DR: I'd like to have som...
Dochazka by smithfarm
Dochazka is a long-term project to replace the ...
Adopt Typescript in D-Installer by IGonzalezSosa
Project Description
In January, we announ...