ci(coverity): surface download errors instead of bare exit code#447
Closed
djowel wants to merge 1 commit into
Closed
ci(coverity): surface download errors instead of bare exit code#447djowel wants to merge 1 commit into
djowel wants to merge 1 commit into
Conversation
The "Download Coverity Build Tool" step used `wget -q`, which hid the server's response. When scan.coverity.com rejected the request (bad/expired token, quota, or server error) the step failed with only `exit code 8`. - Use `wget -S` to print the HTTP response headers. - Validate the download is actually a gzip archive (Coverity serves an error page on a bad token), and dump the server response on failure. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Member
Author
|
Superseded by #448 — removing the Coverity workflow entirely instead of diagnosing it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The scheduled Coverity scan has been failing at the Download Coverity Build Tool step with only
Process completed with exit code 8(example run).Exit code 8 from
wgetmeans "Server issued an error response" —scan.coverity.comreturned an error instead of the build-tool tarball. The step usedwget -q, so the actual cause (bad/expired token, quota exceeded, or a server-side error) was hidden.Change
wget -Sto print the HTTP response headers in the log.This does not fix the underlying download failure — it makes the next run report why it failed. The most likely root cause is an invalid/expired
COVERITY_SCAN_TOKENsecret or a Coverity Scan quota/server issue. Trigger via Run workflow (workflow_dispatch) after merge to see the real error.🤖 Generated with Claude Code