Fix builder timeout #135

New issue

Closed

opened 2026-03-31 23:02:29 +00:00 by anton · 3 comments

anton commented

2026-03-31 23:02:29 +00:00

(Migrated from codeberg.org)

The build process should be checked for progress or errors rather than relying on the env var for BUILDER_TIMEOUT which could cause build jobs to be terminated even though the build is still in progress

anton commented

2026-04-29 21:44:18 +00:00

(Migrated from codeberg.org)

"maybe a heartbeat updater that runs in the background every minute" - Ryan

This seems like a better way to do this, instead of a hard-coded timeout

"maybe a heartbeat updater that runs in the background every minute" - Ryan This seems like a better way to do this, instead of a hard-coded timeout

modalala commented

2026-05-03 23:59:41 +00:00

(Migrated from codeberg.org)

I do think it's likely that for more testing, we'll want to adjust the timeout up, or reconsider the way that the builder fails out.

anton commented

2026-05-18 18:01:32 +00:00

(Migrated from codeberg.org)

This has been resolved with @ryansquared 's work on health check code.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

public/platform#135

No description provided.

Rows
Columns