Opened 4 years ago
Last modified 2 years ago
#26085 new enhancement
Better error reporting for failed CI builds
| Reported by: | saraedum | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | sage-8.4 |
| Component: | build | Keywords: | ContinuousIntegration |
| Cc: | embray, slelievre | Merged in: | |
| Authors: | Julian Rüth | Reviewers: | |
| Report Upstream: | N/A | Work issues: | |
| Branch: | Commit: | ||
| Dependencies: | #24655 | Stopgaps: |
Status badges
Description
Currently, there are a bunch of confusing error codes that can show up at the end of CI builds. It would be nice to translate them to something more readable, e.g.,
- 137: the machine was preempted, please try again.
- timeout: there were too many SPKG changes and you are running on shared infrastructure that cannot handle that...
- no space left on device: essentially the same
- ...
Change History (5)
comment:1 Changed 4 years ago by
comment:2 Changed 4 years ago by
- Cc slelievre added
comment:3 follow-up: ↓ 5 Changed 4 years ago by
Forgot about this ticket. Yes, that's a good idea about a bot.
I wonder if there's a way--though it seems far-fetched--to detect how many packages need to be rebuilt for a given ticket and push the build off to a more powerful machine.
comment:4 Changed 2 years ago by
- Keywords ContinuousIntegration added
comment:5 in reply to: ↑ 3 Changed 2 years ago by
Replying to embray:
Forgot about this ticket. Yes, that's a good idea about a bot.
I wonder if there's a way--though it seems far-fetched--to detect how many packages need to be rebuilt for a given ticket and push the build off to a more powerful machine.
No, I don't think that's possible in GitLab CI currently.
For the 137s it would be nice to have a bot that clicks "Retry".