| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Support listing builds and including/excluding builds by relationship | Christopher Baines | 2022-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 builds | Christopher Baines | 2022-10-10 |
| | | | | | For an agent. | ||
| * | Add system information in to listing the build allocation plan | Christopher Baines | 2022-10-10 |
| | | |||
| * | Include priority information in the allocation plan output | Christopher Baines | 2022-10-09 |
| | | | | | Also switch derivation-name to use an underscore. | ||
| * | Improve listing agent build allocation plans | Christopher Baines | 2022-10-09 |
| | | |||
| * | Don't crash on chunked input exceptions | Christopher Baines | 2022-10-08 |
| | | |||
| * | Check the dynamic auth token before creating new agents | Christopher Baines | 2022-10-08 |
| | | |||
| * | Properly handle build failure statuses | Christopher Baines | 2022-09-02 |
| | | |||
| * | Don't record the build as failed if the exception is unknown | Christopher Baines | 2022-09-02 |
| | | | | | As this can cause spurious failures. | ||
| * | Fix adding GC roots for built outputs | Christopher Baines | 2022-09-02 |
| | | |||
| * | Fix triggering build allocations for a couple of actions | Christopher Baines | 2022-07-15 |
| | | |||
| * | Add a couple of missing build allocation triggers | Christopher Baines | 2022-07-08 |
| | | |||
| * | Fix bug when handling missing output details | Christopher Baines | 2022-07-07 |
| | | |||
| * | Support updating build priorities through the command line | Christopher Baines | 2022-07-07 |
| | | |||
| * | Send more information on derivation outputs to the Guix Data Service | Christopher Baines | 2022-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 outputs | Christopher Baines | 2022-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 cancelled | Christopher Baines | 2022-07-07 |
| | | |||
| * | Support updating the priorities of builds | Christopher Baines | 2022-07-07 |
| | | |||
| * | Support listing builds by priority | Christopher Baines | 2022-07-07 |
| | | |||
| * | Allow changing the agent parallel uploads | Christopher Baines | 2022-07-06 |
| | | |||
| * | Move getting output details soon after the outputs are generated | Christopher Baines | 2022-07-05 |
| | | | | | Like compressing the outputs, it's worth doing this sooner rather than later. | ||
| * | Add temp roots for built outputs | Christopher Baines | 2022-07-05 |
| | | | | | In case these need sending to the coordinator. | ||
| * | Fix match error when populating the running-ids hash | Christopher Baines | 2022-07-03 |
| | | |||
| * | Support processing hook events in parallel | Christopher Baines | 2022-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 procedure | Christopher Baines | 2022-06-30 |
| | | | | | This will make introducing processing hook events in parallel easier. | ||
| * | Fix read-drv/substitute not actually reading the derivation | Christopher Baines | 2022-06-15 |
| | | | | | If it is already in the store. | ||
| * | Fallback to reading derivations directly from substitute servers | Christopher Baines | 2022-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 debugging | Christopher Baines | 2022-06-15 |
| | | |||
| * | Double check when to actually store builds as asked | Christopher Baines | 2022-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 #:hz | Christopher Baines | 2022-05-22 |
| | | | | | As this may help to avoid unnecessary switching between things. | ||
| * | Use the substitutes channel for reading derivations | Christopher Baines | 2022-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 builds | Christopher Baines | 2022-05-22 |
| | | |||
| * | Refactor build-for-output-already-exists? to only call read-drv once | Christopher Baines | 2022-05-22 |
| | | | | | This should have effectively happened due to caching, but make it explicit. | ||
| * | Fix spacing in a logging message | Christopher Baines | 2022-05-21 |
| | | |||
| * | Remove the timeout from the allocation process | Christopher Baines | 2022-05-21 |
| | | | | | It's quick and always finishes, so it doesn't need one any longer. | ||
| * | Fix the guix-data-service request timeout | Christopher Baines | 2022-05-21 |
| | | | | | Which was 30,000 seconds, rather than 30 seconds. | ||
| * | Add more logging and timeouts around fetching inputs | Christopher Baines | 2022-05-21 |
| | | |||
| * | Make the derivation cache a doubly weak hash table | Christopher Baines | 2022-05-19 |
| | | | | | As I have a suspicion that the weak key hash table is keeping stuff around. | ||
| * | Avoid substituting derivations when builds are submitted | Christopher Baines | 2022-05-15 |
| | | | | | | When the derivation substitute URLs are known. This avoids having to add the derivation to the store, which can be blocked by garbage collection. | ||
| * | Add a way of reading derivations directly from substitutes | Christopher Baines | 2022-05-15 |
| | | | | | | This avoids having to add the derivations to the store which can be blocked by garbage collection. | ||
| * | Increase the parallelism of the substitutes thread channel | Christopher Baines | 2022-04-28 |
| | | | | | As this looks to be a bottleneck. | ||
| * | Guard against inserting unnecessary related builds | Christopher Baines | 2022-04-23 |
| | | |||
| * | Take the max of the derived priority and priority | Christopher Baines | 2022-04-23 |
| | | | | | | | I believe this fixes an issue where the derived priority could be lower than the priority, if the build being inserted isn't at the edge of the derivation graph. | ||
| * | Guarantee the order of related derivations when listing them | Christopher Baines | 2022-04-23 |
| | | | | | | | | Since I believe this is important when inserting builds, as for the derived priorities to be computed correctly, the derivations closet in the graph need to be processed first, so that their derived priority informs that of builds that depend on them. | ||
| * | Add some extra logging when an output has been submitted | Christopher Baines | 2022-04-09 |
| | | |||
| * | Remove double retry-on-error for submitting outputs | Christopher Baines | 2022-04-09 |
| | | | | | As submit-output retries on failure. | ||
| * | Move retry in submit-output | Christopher Baines | 2022-04-09 |
| | | |||
| * | Add a timeout for submitting outputs | Christopher Baines | 2022-04-09 |
| | | |||
| * | Fix timeout when fetching inputs | Christopher Baines | 2022-04-08 |
| | | | | | The timeout is in seconds, not milliseconds. | ||
| * | Simplify with-timeout | Christopher Baines | 2022-04-08 |
| | | |||