coordination #19720
Updated by okurz over 4 years ago
## motivation Make job failure investigation easier to save time and ensure we do not miss failures ## ideas * provide more data in the job logs itself for https://progress.opensuse.org/projects/openqav3/wiki#Further-decision-steps-working-on-test-issues * e.g. [gh#os-autoinst/os-autoinst#805](https://github.com/os-autoinst/os-autoinst/pull/805) -> providing also git hash for needles repo so we could also compare the differences in needles * See https://github.com/okurz/openqa_review/tree/feature/investigate especially https://github.com/okurz/openqa_review/blob/feature/investigate/openqa_review/investigate.py * provide diff of failed job vs. "last good" * git log or diff for test+needle changes -> test git log done with https://github.com/os-autoinst/openQA/pull/2609 * list of changed files * os-autoinst version in vars.json * all package changes, e.g. save `rpm -qa` in file and provide diff and/or changelog * diff of test schedule * exclude context in vars.json diff, distinguish change and add/remove * exclude merges from test git log * if best needle candidate matches 0% it is most likely not a trivial needle issue