action #163622
closed
Scripts CI pipeline failing with invalid numeric literal error size:S
Added by livdywan about 2 months ago.
Updated about 1 month ago.
Category:
Regressions/Crashes
Description
Observation¶
Scripts CI pipeline on GitLab is failing with an error:
++ openqa-cli api --host http://openqa.suse.de jobs version=15-SP5 scope=relevant arch=x86_64 flavor=Server-DVD-Updates test=ovs-client latest=1
++ jq -r '.jobs | map(select(.result == "passed")) | max_by(.settings.BUILD) .settings.HDD_1'
jq: parse error: Invalid numeric literal at line 1, column 8
Acceptance Criteria¶
- AC1: Scripts CI pipeline consistently passes
- AC2: We have access to the input of jq and know the the HTTP error code
Suggestions¶
- Print the api output before passing it to jq to see what we actually got
- Consider other potentially related issues explaining the root cause triggering the problem, e.g. see #163592
- Ensure that openqa-cli api actually returns an error if the response is not something usable, e.g. an error and not JSON
- Check how we invoke
jq
in the scripts repo and maybe reuse the _common
file as we already download a file from that repo but should clone the repo or something
- Related to action #163592: [alert] (HTTP Response alert Salt tm0h5mf4k) size:M added
I am surprised you don't mention the relation to #163592
okurz wrote in #note-2:
I am surprised you don't mention the relation to #163592
I might have if I understood the error.
It ran at 4:13 GMT+2 so it doesn't seem related. We had already disabled the streaming route then, right?
- Description updated (diff)
- Target version set to Ready
- Subject changed from Scripts CI pipeline failing with invalid numeric literal error to Scripts CI pipeline failing with invalid numeric literal error size:S
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to jbaier_cz
Meh.. now we have too much information: Job's log exceeded limit of 4194304 bytes.
- Due date set to 2024-08-06
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Feedback
Printing API output everytime is not an option here (the output is too long), so I re-used the runjq wrapper from the _common
which should output some details in case of failure. So far all pipelines succeeded (or failed due to other reasons), so I cannot reliably say if AC2 was fulfiled.
I will put this on feedback for a while to monitor the impact of the change.
- Status changed from Feedback to Resolved
- Due date deleted (
2024-08-06)
- Copied to action #165620: [alert] OSD deployment pipeline failing with invalid numeric literal error added
Also available in: Atom
PDF