Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinguish connection errors from "real" errors in nightly builds #422

Closed
andrewmogan opened this issue Jan 9, 2025 · 1 comment
Closed

Comments

@andrewmogan
Copy link
Collaborator

Over the past few months, we've had transient failures in the nightly builds due to spack FetchErrors. This indicates a simple connection error where the solution is to manually rerun the build until the connection is resolved. This issue is not reproducible since it occurs sporadically and does not necessarily affect the same package every time. When this occurs, we could automatically rerun the build by scanning the GitHub Actions output for a FetchError and returning a specific exit code in our workflow which can then be passed to this external retry action to automatically rerun the failed step.

andrewmogan added a commit that referenced this issue Jan 9, 2025
andrewmogan added a commit that referenced this issue Jan 10, 2025
andrewmogan added a commit that referenced this issue Jan 10, 2025
andrewmogan added a commit that referenced this issue Jan 14, 2025
andrewmogan added a commit that referenced this issue Jan 14, 2025
andrewmogan added a commit that referenced this issue Jan 14, 2025
andrewmogan added a commit that referenced this issue Jan 15, 2025
jcfreeman2 pushed a commit that referenced this issue Jan 24, 2025
… reporting; alsa opportunistically drop dbe-build logic from the v4 nightly build since dbe isn't a thing in v4
@andrewmogan
Copy link
Collaborator Author

Addressed by #423.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant