Actions
action #164153
closedcoordination #102915: [saga][epic] Automated classification of failures
coordination #166655: [epic] openqa-label-known-issues
Errors in gru journal: openqa-label-known-issues error fetching JSON output size:S
Start date:
2024-07-11
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
Jul 11 15:15:07 openqa openqa-gru[7683]: curl (173 /opt/os-autoinst-scripts/openqa-label-known-issues): Error fetching (-L --user-agent openqa-label-known-issues -sS https://progress.opensuse.org/projects/openqav3/issues.json?limit=200&subproject_id=*&subject=~auto_review%3A): {"issues":[{"id": ....... very long JSON output
and the JSON ends with:
...{"id":135839,"project":{"id":36,"name":"openQA Tests"},"tracker":{"id":4,"name":"action"},"status":{"id":1,"name":"New","is_closed":false},"priority":{"id":4,"name":"Normal"},"author":{"id":17668,"name":"okurz"},"category":{"id":152,"name":"Bugs in existing tests"},"subject":"[desktop] test fails in login_test auto_review:\"no candidate needle.*gnome-settings\":retry","description":"## Observation\r\n\r\nopenQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktcurl: (18) Recv failure: Connection reset by peer
Acceptance criteria¶
- AC1: Log output is short enough to be understood by humans
Suggestions¶
- The output is annoyingly long and it's hard to find the actual failure. But if we cut off the end, we won't see it, but we also want to see the start. Maybe the content should be cut in the middle.
Updated by livdywan 4 months ago
- Copied from action #163769: Errors in gru journal: jq (173 /opt/os-autoinst-scripts/openqa-label-known-issues): parse error: Invalid numeric literal at line 1, column 8 (rc: 4 Input: >>>Waiting 1s until retry #12 added
Actions