| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Avoid some threads and locks when running on the hurd | Christopher Baines | 2021-02-15 |
| | | | | | I've see the process hang on the hurd, and I think this might help. | ||
| * | Increase the derivation ordered allocator default planned builds | Christopher Baines | 2021-02-15 |
| | | | | | | As the derivation ordered allocator is quite slow when there's a large number of builds to consider. | ||
| * | Revert "Speed up the explicit WAL checkpoints" | Christopher Baines | 2021-02-14 |
| | | | | | | | I'm not sure this is helping. This reverts commit ac6a85af9770fa2e2ac33ac20fbdf91103b32f21. | ||
| * | Tweak the S3 publish hook to avoid issues for not submitted outputs | Christopher Baines | 2021-02-14 |
| | | | | | | | | | | | | | Agents can skip submitting outputs where those outputs have already been received, this saves some work when all the information is communicated in the build status. The publish hook worked with this change, because it checks for narinfo files, and would not bother about the missing outputs if the corresponding narinfo existed. This didn't quite work with the s3 publish hook though, but these changes address that by getting the two hooks to write and check for narinfo files in the same location. | ||
| * | Show backtraces upon hook errors | Christopher Baines | 2021-02-14 |
| | | | | | | This might not be helpful, but I think it's still worth trying, even if all the line numbers are within Guile itself... | ||
| * | Add a log message at the end of a build | Christopher Baines | 2021-02-14 |
| | | | | | So it's clearer that it's ended. | ||
| * | Speed up the explicit WAL checkpoints | Christopher Baines | 2021-02-14 |
| | | | | | To try and curtail the WAL growth. | ||
| * | Remove unused coordinator module from the http agent messaging module | Christopher Baines | 2021-02-13 |
| | | |||
| * | Disable the local agent-messaging backend | Christopher Baines | 2021-02-13 |
| | | | | | | It's causing issues with trying to run the agent on the hurd, as it pulls in the datastore and sqlite along with it. | ||
| * | Remove (guix-build-coordinator datastore) import from agent module | Christopher Baines | 2021-02-13 |
| | | | | | I'm seeing this pull in sqlite3 unnecessarily on the hurd. | ||
| * | Adjust guix-dev.scm for more compatability with old Guix versions | Christopher Baines | 2021-02-12 |
| | | |||
| * | Fix use of assoc | Christopher Baines | 2021-02-12 |
| | | |||
| * | Tweak trying to safely load the (guix narinfo) module | Christopher Baines | 2021-02-10 |
| | | | | | | I think the eval-when thing might help given narinfo-references is a syntax thing, rather than a normal procedure. | ||
| * | Add fallback package for guile-prometheus | Christopher Baines | 2021-02-09 |
| | | |||
| * | Add fallback package for guile-lzlib | Christopher Baines | 2021-02-09 |
| | | |||
| * | Add fallback package for guile-zlib | Christopher Baines | 2021-02-09 |
| | | |||
| * | Add fallback guile-json-4 package | Christopher Baines | 2021-02-09 |
| | | | | | For old versions of Guix. | ||
| * | Try to fix using narinfo-references | Christopher Baines | 2021-02-09 |
| | | |||
| * | Fix compatability with newer versions of Guix | Christopher Baines | 2021-02-09 |
| | | | | | | With respect to narinfo-references, which moved from (guix scripts substitute) to (guix narinfo). | ||
| * | Add a roadmap to the README | Christopher Baines | 2021-02-09 |
| | | |||
| * | Add more logging around build result processing | Christopher Baines | 2021-02-08 |
| | | |||
| * | Remove mentions of prototype from the readme | Christopher Baines | 2021-02-06 |
| | | | | | As it's a bit more than that now. | ||
| * | Trigger build allocations when necessary for deferred builds | Christopher Baines | 2021-02-06 |
| | | |||
| * | Use srfi-19 in the coordinator module | Christopher Baines | 2021-02-06 |
| | | |||
| * | Fix datastore-list-builds failing if systems isn't specified | Christopher Baines | 2021-02-05 |
| | | |||
| * | Filter out not-tags which don't exist | Christopher Baines | 2021-02-05 |
| | | |||
| * | Make it possible to look for blocking builds for a specific system | Christopher Baines | 2021-02-02 |
| | | |||
| * | Copy build tags in the failure retry hook | Christopher Baines | 2021-02-02 |
| | | | | | As this probably makes sense to do. | ||
| * | Allow specifying the build-canceled-hook on the command line | Christopher Baines | 2021-02-02 |
| | | |||
| * | Stop the derivation ordered allocator from logging lots | Christopher Baines | 2021-02-02 |
| | | | | | | This value was unintentionally changed, it's just intended for local debugging. | ||
| * | Don't crash if builds don't have a created at date | Christopher Baines | 2021-01-31 |
| | | |||
| * | Fix ignoring builds with no tags in datastore-list-builds | Christopher Baines | 2021-01-31 |
| | | |||
| * | Remove the created after derivation ordered allocator argument | Christopher Baines | 2021-01-31 |
| | | | | | As this is preventing some builds from excuting. | ||
| * | Only require matching tags when the build and agent keys match | Christopher Baines | 2021-01-31 |
| | | |||
| * | Deduplicate agent-tags-match-build-tags | Christopher Baines | 2021-01-31 |
| | | |||
| * | List more information about agents | Christopher Baines | 2021-01-31 |
| | | |||
| * | Include allocated builds in the agents response | Christopher Baines | 2021-01-31 |
| | | |||
| * | Add agent tags to the agents response | Christopher Baines | 2021-01-31 |
| | | |||
| * | Include tags in the agents response | Christopher Baines | 2021-01-31 |
| | | |||
| * | Improve agent tags message | Christopher Baines | 2021-01-31 |
| | | |||
| * | Support listing and canceling builds by derivation system | Christopher Baines | 2021-01-31 |
| | | |||
| * | Exclude allocated builds from setup failures | Christopher Baines | 2021-01-26 |
| | | | | | As I think this is causing the allocator to crash. | ||
| * | Try to simplify part of the basic allocator | Christopher Baines | 2021-01-26 |
| | | | | | As there has been exceptions in this area, the required build priority is #f. | ||
| * | Fix a crash when rendering the client builds response | Christopher Baines | 2021-01-26 |
| | | |||
| * | Don't use with-exception-handler with (backtrace) | Christopher Baines | 2021-01-22 |
| | | | | | | | | | | | | With with-exception-handler being called with #:unwind? #f (implicitly). This breaks Guile internals used by (backtrace) [1], meaning you get a different exception/backtrace when Guile itself breaks. This should avoid the "string->number: Wrong type argument in position 1 (expecting string): #f" exception I've been haunted by for the last year. 1: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=46009 | ||
| * | Rework client error handling | Christopher Baines | 2021-01-19 |
| | | | | | To see if that produces better logging. | ||
| * | Fix up a load of the tag related code | Christopher Baines | 2021-01-17 |
| | | | | | | Turns out vector-fold and vector-map don't work like I'd expected them to, like fold and map for vectors. | ||
| * | Sure up handling of exceptions within Guile (backtrace) | Christopher Baines | 2021-01-17 |
| | | |||
| * | Fix bug in allocators from alist to vector switch for tags | Christopher Baines | 2021-01-17 |
| | | |||
| * | Stop treating collections of tags as alists | Christopher Baines | 2021-01-17 |
| | | | | | | | | This translates poorly to JSON, as you can't have multiple values for one name in a JSON object. Is also is risky in terms of assoc-ref being used, and not considering more than one key. Using a vector of pairs should help in both situations. | ||