Skip to content

Prebuild fails with non-userfriendly error message #9513

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

Open
Tracked by #9291
tnir opened this issue Apr 25, 2022 · 5 comments
Open
Tracked by #9291

Prebuild fails with non-userfriendly error message #9513

tnir opened this issue Apr 25, 2022 · 5 comments
Labels
meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code user experience

Comments

@tnir
Copy link
Contributor

tnir commented Apr 25, 2022

Bug description

Prebuild fails with non-userfriendly error message "Error: headless task failed: exit status 1".

Screenshot

x

Conditions

  1. On-fly launching workspace on the branch will fail as well.

Steps to reproduce

  1. Enable a project (from https://gitpod.io/new?user=1) if you do not have yet.
  2. Access to https://gitpod.io/projects/your-project/prebuilds.
  3. Click "Run Prebuild (branch-name)" from vertical ellipsis next to branch name (non-default branch like master or main)
  4. Wait for a while to see the system error

Workspace affected

No response

Expected behavior

User-friednly error message is expected.

Example repository

https://github.com/tnir/forem/tree/jammy-on-dev

Anything else?

No response

@axonasif axonasif added user experience type: improvement Improves an existing feature or existing code team: webapp Issue belongs to the WebApp team labels Apr 25, 2022
@jldec
Copy link
Contributor

jldec commented Apr 26, 2022

Thank you for providing this repro @tnir.
We are tracking improvements to our prebuild and imagebuild logging in our roadmap as part of #9291

@stale
Copy link

stale bot commented Jul 31, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jul 31, 2022
@tnir
Copy link
Contributor Author

tnir commented Jul 31, 2022

Un-stale

@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Jul 31, 2022
@stale
Copy link

stale bot commented Nov 9, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Nov 9, 2022
@tnir
Copy link
Contributor Author

tnir commented Nov 9, 2022

Un-stale

@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Nov 9, 2022
@axonasif axonasif added the meta: never-stale This issue can never become stale label Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code user experience
Projects
Status: No status
Development

No branches or pull requests

3 participants