pulsar-edit
CI: Retry package test on segmentation fault
Have you checked for existing feature requests?
- [x] Completed
Summary
We've got a situation with package tests on CI where, on maybe 1% of runs, the editor immediately exits with a segmentation fault.
If this happened under normal circumstances at all to an end user, we'd want to drop everything and figure it out. But since it only seems to happen under CI, the only thing to do is shrug and retry the job.
We should automate the shrugging-and-retrying step somehow. We want to retry immediately on failure if the failure had to do with an immediate segmentation fault; but if the failure comes after a full test run and involves actual test failures, we don't want to retry.
What benefits does this feature provide?
Quicker to green on PRs.
Any alternatives?
Fixing the underlying segmentation fault! But I'm pessimistic about that. Those are hard enough to track down when they're reproducible on your own machine.
Other examples:
No response
