You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Right now, the preparation worker conflates different errors into a single DidntMakeIt artifact status. Worse, this is reported by the execution worker as "preparation timeout" which is extremely confusing. Untangling this would be the result of completion of this issue.
At the moment of writing, that error can be reported on the following conditions:
the response from the worker is received, but the file cannot be renamed (moved) to the final destination location
the response from the worker is received, but it is not what we expected
an IO error occurred while receiving the result from the worker process
the worker took too much time to finish preparation
All these issues should be properly reported separately. This means we should probably list those conditions in the ArtifactState enum.
The text was updated successfully, but these errors were encountered:
I noticed this too. Glad there is already an issue for it, I can take this up in the near future. Maybe after #6282 is done to prevent merge conflicts.
Right now, the preparation worker conflates different errors into a single
DidntMakeIt
artifact status. Worse, this is reported by the execution worker as "preparation timeout" which is extremely confusing. Untangling this would be the result of completion of this issue.At the moment of writing, that error can be reported on the following conditions:
All these issues should be properly reported separately. This means we should probably list those conditions in the
ArtifactState
enum.The text was updated successfully, but these errors were encountered: