-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Some failed prebuilds use a wrong status label #5611
Comments
@gtsiolis does it stay like this on the Prebuild Page on reload after +10 seconds? |
@AlexTugarev yes, you can also try this using the example link above:
|
This seems to be still an issue, see another example:
However, let's move this to the Next Iteration in the relevant project board[1] as this affects a really small set of prebuilds.
|
Indeed, good catch! I think that in some cases, when the prebuild instance fails (i.e. the WorkspaceInstance has a failure condition and stops), for some reason the prebuild status is not updated (i.e. PrebuiltWorkspace remains in EDIT: Ah, if I remember correctly, I think this might be the case when the prebuild instance cannot even start. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
No longer relevant as we do not include the second status label in the header. However, we still need to handle links to |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been resolved in #8805 |
Bug description
Some failed prebuilds use a wrong status label.
Steps to reproduce
N/A
Expected behavior
No response
Example repository
See prebuild for
gitpod-io/gitpod
ingitpod.io
.Anything else?
No response
The text was updated successfully, but these errors were encountered: