aboutsummaryrefslogtreecommitdiff
path: root/guix-build-coordinator
Commit message (Collapse)AuthorAge
* Log when output files are renamedChristopher Baines2022-10-22
|
* Add more logging when output files are deletedChristopher Baines2022-10-22
|
* Log the time for parts of the datastore metric initialisationChristopher Baines2022-10-21
|
* Tweak upload handling againChristopher Baines2022-10-21
| | | | | | This partially reverts some recent changes. There should now be better handling of when all the bytes have been sent, but the hash hasn't yet been computed.
* Copy upload error handling to the partial routeChristopher Baines2022-10-21
|
* Log the file size and md5 hash on the agent sideChristopher Baines2022-10-21
| | | | When errors occur during upload.
* Include the file size and md5 hash in error messagesChristopher Baines2022-10-21
| | | | | When an error occurs while trying to compute the hash, as I hope this information will help to identify where things have gone wrong.
* Tweak output uploading codeChristopher Baines2022-10-19
| | | | Force sending the file from the start the first time the upload is attempted.
* Move SIGPIPE handling in to the scriptChristopher Baines2022-10-19
| | | | Just in case there's places where the previous handling didn't catch it.
* Raise exceptions when port-poll times outChristopher Baines2022-10-16
| | | | Otherwise port-poll will just be called again.
* Use suspendable ports for the agent, with timeoutsChristopher Baines2022-10-16
| | | | | | | | This seems like a way of making the Guile internals for doing network I/O reliable. Currently, there are problems where things on the network timeout, but the Guile code for reading/writing just sits there, hung. This seems like it might help.
* Throttle calling alarmChristopher Baines2022-10-15
| | | | Just in case calling it frequently causes problems.
* Reset the upload progress when appropriateChristopher Baines2022-10-14
|
* Add more logging around file uploadsChristopher Baines2022-10-14
|
* Shorten timeout when submitting outputsChristopher Baines2022-10-14
| | | | By resetting the timeout while the file is being uploaded.
* Tweak output upload timeoutChristopher Baines2022-10-14
| | | | | Make it longer to avoid timeouts for large files, and increase the delay before restarting the upload.
* Add some more logging when agents submit outputsChristopher Baines2022-10-14
|
* Guard against canceling builds required by othersChristopher Baines2022-10-11
|
* Support listing builds and including/excluding builds by relationshipChristopher Baines2022-10-11
| | | | | This is to help cancel builds, but where you want to avoid builds that are still needed by others.
* Allow specifying the maximum number of allocated buildsChristopher Baines2022-10-10
| | | | For an agent.
* Add system information in to listing the build allocation planChristopher Baines2022-10-10
|
* Include priority information in the allocation plan outputChristopher Baines2022-10-09
| | | | Also switch derivation-name to use an underscore.
* Improve listing agent build allocation plansChristopher Baines2022-10-09
|
* Don't crash on chunked input exceptionsChristopher Baines2022-10-08
|
* Check the dynamic auth token before creating new agentsChristopher Baines2022-10-08
|
* Properly handle build failure statusesChristopher Baines2022-09-02
|
* Don't record the build as failed if the exception is unknownChristopher Baines2022-09-02
| | | | As this can cause spurious failures.
* Fix adding GC roots for built outputsChristopher Baines2022-09-02
|
* Fix triggering build allocations for a couple of actionsChristopher Baines2022-07-15
|
* Add a couple of missing build allocation triggersChristopher Baines2022-07-08
|
* Fix bug when handling missing output detailsChristopher Baines2022-07-07
|
* Support updating build priorities through the command lineChristopher Baines2022-07-07
|
* Send more information on derivation outputs to the Guix Data ServiceChristopher Baines2022-07-07
| | | | | | This will enable it to join builds to derivations, even if it doesn't know about the derivation being built, since it'll be able to match the outputs with other derivations it knows about.
* Record the details of derivation outputsChristopher Baines2022-07-07
| | | | | | | I believe this will be useful when linking builds to other services, like the Guix Data Service, since this information might be useful when joining up the derivation being built to other derivations through the details of the outputs produced.
* Update the derived priorities when a build is cancelledChristopher Baines2022-07-07
|
* Support updating the priorities of buildsChristopher Baines2022-07-07
|
* Support listing builds by priorityChristopher Baines2022-07-07
|
* Allow changing the agent parallel uploadsChristopher Baines2022-07-06
|
* Move getting output details soon after the outputs are generatedChristopher Baines2022-07-05
| | | | Like compressing the outputs, it's worth doing this sooner rather than later.
* Add temp roots for built outputsChristopher Baines2022-07-05
| | | | In case these need sending to the coordinator.
* Fix match error when populating the running-ids hashChristopher Baines2022-07-03
|
* Support processing hook events in parallelChristopher Baines2022-06-30
| | | | | | | | | | Forcing hooks to be sequential simplifies them, and the implementation, but it doesn't always scale well. I'm particularly thinking about the build-submitted hook and built-success hooks, the processing of which can back up if there's lots of builds being submitted or finishing successfully. This new functionality allows hooks to be processed in parallel, which should allow to manage this more effectively.
* Pull fetching the event to process out of the process-event procedureChristopher Baines2022-06-30
| | | | This will make introducing processing hook events in parallel easier.
* Fix read-drv/substitute not actually reading the derivationChristopher Baines2022-06-15
| | | | If it is already in the store.
* Fallback to reading derivations directly from substitute serversChristopher Baines2022-06-15
| | | | | | | Rather than doing this always, since it's not currently performant enough. Once it's possible to read derivations in lazily, then this might be feasible, but for now, just fall back to it if substituting times out, which can happen if garbage collection is running.
* Set thread names to help with debuggingChristopher Baines2022-06-15
|
* Double check when to actually store builds as askedChristopher Baines2022-05-22
| | | | | | | | This should ensure that the ignore-if-build-for-derivation-exists? and ignore-if-build-for-output-exists? options work even if two builds are submitted for the same derivation at the same time. Since one transaction should commit first, then the other transaction will notice this, even if the checks prior to the transaction have not shown another build.
* Drop the fibers #:hzChristopher Baines2022-05-22
| | | | As this may help to avoid unnecessary switching between things.
* Use the substitutes channel for reading derivationsChristopher Baines2022-05-22
| | | | | I think the use of gnutls for the network requests, or the network requests themselves may be causing fibers to block.
* Add delay logging around submitting buildsChristopher Baines2022-05-22
|