Skip to content

[prebuilds] Introduce 'failed' state for prebuilds #8602

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

Merged
merged 1 commit into from
Mar 7, 2022

Conversation

svenefftinge
Copy link
Member

Description

This PR introduces a "failure" state for prebuilds that have entirely failed to finish.
This is to distinguish them from failed tasks but finished rebuilds.

Related Issue(s)

fixes #8592

Release Notes

NONE

@svenefftinge
Copy link
Member Author

svenefftinge commented Mar 4, 2022

/werft run

👍 started the job as gitpod-build-se-prebuilds-failed.2

@svenefftinge svenefftinge force-pushed the se/prebuilds-failed branch from b8f3157 to 6dcafb8 Compare March 4, 2022 14:16
@svenefftinge
Copy link
Member Author

svenefftinge commented Mar 7, 2022

/werft run

👍 started the job as gitpod-build-se-prebuilds-failed.4

@codecov
Copy link

codecov bot commented Mar 7, 2022

Codecov Report

Merging #8602 (4769e41) into main (2863582) will decrease coverage by 17.80%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##             main    #8602       +/-   ##
===========================================
- Coverage   28.98%   11.17%   -17.81%     
===========================================
  Files         150       18      -132     
  Lines       23118      993    -22125     
===========================================
- Hits         6700      111     -6589     
+ Misses      15808      880    -14928     
+ Partials      610        2      -608     
Flag Coverage Δ
components-blobserve-app ?
components-blobserve-lib ?
components-common-go-lib ?
components-content-service-api-go-lib ?
components-content-service-app ?
components-content-service-lib ?
components-ee-agent-smith-app ?
components-ee-agent-smith-lib ?
components-ee-kedge-app ?
components-gitpod-cli-app 11.17% <ø> (ø)
components-ide-code-codehelper-app ?
components-image-builder-api-go-lib ?
components-image-builder-bob-app ?
components-image-builder-bob-runc-facade ?
components-image-builder-mk3-app ?
components-installation-telemetry-app ?
components-local-app-app-darwin-amd64 ?
components-local-app-app-darwin-arm64 ?
components-local-app-app-linux-amd64 ?
components-local-app-app-linux-arm64 ?
components-local-app-app-windows-386 ?
components-local-app-app-windows-amd64 ?
components-local-app-app-windows-arm64 ?
components-openvsx-proxy-app ?
components-openvsx-proxy-lib ?
components-registry-facade-app ?
components-registry-facade-lib ?
components-service-waiter-app ?
components-supervisor-app ?
components-workspacekit-app ?
components-ws-daemon-api-go-lib ?
components-ws-daemon-app ?
components-ws-daemon-lib ?
components-ws-daemon-nsinsider-app ?
components-ws-manager-api-go-lib ?
components-ws-manager-app ?
components-ws-proxy-app ?
dev-loadgen-app ?
dev-poolkeeper-app ?
install-installer-raw-app ?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
components/common-go/log/log.go
components/ws-daemon/pkg/content/config.go
...omponents/ws-manager/pkg/manager/pod_controller.go
components/ws-daemon/pkg/content/initializer.go
components/openvsx-proxy/pkg/config.go
components/registry-facade/pkg/registry/blob.go
...s/content-service/pkg/service/workspace-service.go
components/common-go/util/duration.go
components/ws-daemon/pkg/content/tar.go
components/ws-manager/pkg/manager/status.go
... and 122 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2863582...4769e41. Read the comment docs.

@svenefftinge svenefftinge marked this pull request as ready for review March 7, 2022 08:56
@svenefftinge svenefftinge requested a review from a team March 7, 2022 08:56
@github-actions github-actions bot added the team: webapp Issue belongs to the WebApp team label Mar 7, 2022
@svenefftinge svenefftinge force-pushed the se/prebuilds-failed branch from 6dcafb8 to 2d8d852 Compare March 7, 2022 10:07
@AlexTugarev
Copy link
Member

The error handling makes sense and the changes look good. I'm just not sure about the presentation on the dashboard, it seems to be the same as the "headless task failed" case. Could we render the "system error" case differently?

Distinguish between failed tasks but finished prebuilds
and fully failed prebuilds (no snapshot)

fixes #8592
@svenefftinge svenefftinge force-pushed the se/prebuilds-failed branch from 2d8d852 to 4769e41 Compare March 7, 2022 12:04
@svenefftinge
Copy link
Member Author

svenefftinge commented Mar 7, 2022

/werft run

👍 started the job as gitpod-build-se-prebuilds-failed.7

Copy link
Member

@AlexTugarev AlexTugarev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!
💯

@roboquat roboquat merged commit de84f28 into main Mar 7, 2022
@roboquat roboquat deleted the se/prebuilds-failed branch March 7, 2022 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note-none size/M team: webapp Issue belongs to the WebApp team
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[prebuilds] Failed Prebuilds without Snapshot are marked as 'available'
3 participants