ci dos'es itself when a build fails #4

Closed
opened 2024-03-10 07:43:19 +00:00 by pennae · 3 comments
Owner

if a nix build would fail CI will attempt the build not just twice (initial + retry) but 2(n+1) times: twice initially, and twice for every reverse dependency. this causes a failing build to hold up CI for a lot longer than a succeeding build

if a `nix build` would fail CI will attempt the build not just twice (initial + retry) but 2(n+1) times: twice initially, and twice for every reverse dependency. this causes a failing build to hold up CI for *a lot* longer than a succeeding build
Author
Owner

might it be a good idea to remove retries themselves too? so far we've not seen a failure that was retried into success

might it be a good idea to remove retries themselves too? so far we've not seen a failure that was retried into success
Owner

Retries were removed, @pennae ; is it still a concern?

Retries were removed, @pennae ; is it still a concern?
Owner

This is no longer a strong concern with #5 merged in; CI no longer retries and no longer builds builds with failed dependencies.

This is no longer a strong concern with #5 merged in; CI no longer retries and no longer builds builds with failed dependencies.
puck closed this issue 2024-03-11 13:58:58 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
3 participants
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: lix-project/buildbot-nix#4
No description provided.