retry every failed meta build each round, a timeout included, and drop the attempt count
This commit is contained in:
parent
99d2ed5b9e
commit
59456c3c58
1 changed files with 251 additions and 435 deletions
|
|
@ -142,12 +142,13 @@ pub enum FromMetaReply {
|
|||
/// The toplevel built; `out_path` is its store path in the builder host's
|
||||
/// store and `system` the platform the builder host builds for.
|
||||
Built { out_path: String, system: String },
|
||||
/// `nix` ran and exited with an error: the last lines it printed. The
|
||||
/// controller builds once more, and holds the deploy back if that fails too.
|
||||
/// The build did not succeed: the last lines `nix` printed, or why it
|
||||
/// stopped (it timed out, or could not start). The controller holds the
|
||||
/// deploy back and builds again on its next round.
|
||||
Failed { error_tail: String },
|
||||
/// `nix` gave no exit: the build slot stayed busy, the forge token could
|
||||
/// not be read, `nix` could not start, or it hit its deadline. Says nothing
|
||||
/// about the config, so the controller tries again.
|
||||
/// The builder did not get to run `nix`: the build slot stayed busy or the
|
||||
/// forge token could not be read. The controller holds the deploy back and
|
||||
/// builds again on its next round.
|
||||
Unavailable { reason: String },
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue