Project

General

Profile

Actions

action #115178

closed

openqa-investigate: Ensure proper error handling size:M

Added by tinita over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2022-07-21
Due date:
2022-08-26
% Done:

0%

Estimated time:

Description

Observation

In #114451 I found that it can happen that openqa-investigate can abort the script and therefore the bisect script is never run.
https://openqa.suse.de/tests/9298857
Also the error messages are not really helpful:

% env script_dir=/opt/os-autoinst-scripts enable_force_result=true host=openqa.suse.de exclude_group_regex='.*(Development|Public Cloud|Released|Others|Kernel|Virtualization).*' grep_timeout=60 nice ionice -c idle /tmp/openqa-label-known-issues-and-investigate-hook 9298857
Skipping investigation of job 9298857: job cluster is already being investigated, see comment on job 9298857
403 Forbidden
404 Not Found
{"error_status":404}
% echo $?
255

Acceptance criteria

  • AC1: openqa-investigate does exit with zero usually (if there is no fatal problem)
  • AC2: Errors from fetching urls should be handled better so we know which URL resulted in an error
  • AC3: Bisect jobs are run even if the investigation failed
  • AC4: :investigate: jobs are not bisected again

Related issues 1 (0 open1 closed)

Copied from openQA Project (public) - action #114451: Incidents from all test issues variables are collected during bisect size:MResolvedosukup2022-07-212022-09-07

Actions
Actions

Also available in: Atom PDF