-
Notifications
You must be signed in to change notification settings - Fork 71
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
Analysis step in a transient state #685
Comments
An example from
The git commit in question does not belong to any branch on this repository, and may belong to a fork outside of the repository. Looking at the PR for that job ocaml/opam-file-format#47 that commit is available. Rerunning the
|
Sometimes this requires that the worker's cache be wiped. Rebuilding a step from the UI results in the same worker being picked (unless it has been paused or taken down). Is it possible to improve the results of a rebuild by choosing a different worker for the rebuild? |
This might occasionally make the rebuild work where it previously failed, but on the whole, this would be a significant performance hit. Better to try to detect the issue on the worker and get it to fix/delete the cache. Such as what @kit-ty-kate did here ocurrent/ocluster@318a69f |
Sometimes, when running the analysis step, it wouldn't rebuild, get stuck and would always show the same error message. To solve that locally, the solution is to clean the local state and rerun the CI.
It needs more investigation but it could be solved by the
solver-service
.The text was updated successfully, but these errors were encountered: