devops: simplify upload to flakiness.io#2735
Conversation
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
Greptile SummaryReplaces complex Node.js script (50 lines) with a simple Confidence Score: 5/5
Important Files Changed
Last reviewed commit: 8667f29 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8667f29c93
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| run: | | ||
| # Install the flakiness SDK | ||
| npm install @flakiness/sdk | ||
| find . -name report.json -exec npx -y flakiness upload {} + |
There was a problem hiding this comment.
Upload reports individually to avoid all-or-nothing failure
This find ... -exec ... {} + form batches all report.json paths into a single flakiness upload process, so in sharded CI runs (.github/workflows/ci.yml uses shard/shardTotal) one malformed report or transient upload error can make the step fail before the remaining shard reports are recorded. The previous flow handled each shard separately, which preserved partial uploads and avoided losing the entire run’s flakiness data when only one shard artifact is bad.
Useful? React with 👍 / 👎.
|
thanks! |
Uh oh!
There was an error while loading. Please reload this page.