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 mad skills in:

openqa webapps javascript

This project is part of:

Hack Week 16

Activity

  • over 1 year ago: ancorgs liked Add a y2log viewer to openQA's WebUI
  • over 1 year ago: okurz liked Add a y2log viewer to openQA's WebUI
  • over 1 year ago: cwh started Add a y2log viewer to openQA's WebUI
  • over 1 year ago: cwh added keyword "javascript" to Add a y2log viewer to openQA's WebUI
  • over 1 year ago: cwh added keyword "webapps" to Add a y2log viewer to openQA's WebUI
  • Show History

    Comments

    • okurz
      over 1 year 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/selectpatternsand_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

    This project is one of its kind!