QA » openQA Project

motivation¶

Make job failure investigation easier to save time and ensure we do not miss failures

ideas¶

• all package changes, e.g. save rpm -qa in file and provide diff and/or changelog for the worker and the SUT. For openSUSE e.g. read out changelog diff from https://openqa.opensuse.org/snapshot-changes/opensuse/Tumbleweed/ , for SLE from http://xcdchk.suse.de/

  • changes on worker #69088

• diff of test schedule

• if best needle candidate matches 0% it is most likely not a trivial needle issue

• In settings table mark origin of settings and changed settings, e.g. for setting "foo" instead of the table row "foo | 1" one could have

  • "foo | 1 (testsuites table)" when the settings comes from the test suites database table, e.g. compared to job templates, machines, etc. . This would also help when we allow even more sources for settings, e.g. load job templates from test distributions in parallel to database tables
  • update the settings table from vars.json after job run to included changes but then show which settings changed since the job was initially created
  • "foo | 1 (+)" when the setting is new in the scenario, with the table row and/or "(+)" in green (as in common colored diffs) and on hover it shows the explanation that this was added, linked to the commit, showing which job it compares against
  • "foo | 1 (<->)" or similar when the setting changed against "last good" where it was e.g. 0, with "(<->)" being a link to the "last good" job, with the table row in different color