aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Make datastore-call-with-transaction error messages more usefulChristopher Baines2023-04-21
|
* Fix agent-detailsChristopher Baines2023-04-21
|
* Deallocate canceled builds from agents when they startupChristopher Baines2023-04-21
|
* Include the submit_outputs information in the agent status responseChristopher Baines2023-04-21
| | | | | This means that agents will know whether to submit the outputs of builds, even if they're restarted.
* Include whether the build is canceled when listing agent buildsChristopher Baines2023-04-21
| | | | | | Canceled builds aren't unallocated from the agent immediately, so including the canceled status in the information given to the agent allows it to not start or potentially stop the build.
* Add some delay between optimize attemptsChristopher Baines2023-04-21
|
* Add some error handling to datastore-find-build-derivation-systemChristopher Baines2023-04-21
| | | | Not sure why I'm seeing errors here now, but I am.
* Add error handling around some date parsingChristopher Baines2023-04-21
|
* Handle COMMIT erroring with busy in datastore-call-with-transactionChristopher Baines2023-04-21
|
* Turns out COMMIT can return busy, so increase the timeoutChristopher Baines2023-04-21
|
* Add missing sqlite-step and sqlite-resetChristopher Baines2023-04-20
|
* Improve datastore-call-with-transactionChristopher Baines2023-04-20
| | | | | Include exception in log message, and separate out exception handling for the transaction start and body.
* Don't truncate the wal from reader threadsChristopher Baines2023-04-20
|
* Revert "Retry inside the worker thread"Christopher Baines2023-04-20
| | | | | | As this blocks other database operations that wouldn't wait. This reverts commit 42bf1086d588081548fb1efb0b4cf1e5ad119763.
* Drop the busy timeout for the write connectionChristopher Baines2023-04-20
| | | | Since I don't think it should be busy, so don't wait as long if it is.
* Instrument datastore-fetch-builds-to-allocateChristopher Baines2023-04-20
|
* Retry inside the worker threadChristopher Baines2023-04-20
| | | | To prevent other operations getting in the way.
* Raise an error on blocked wal checkpointsChristopher Baines2023-04-20
| | | | | And tweak the retry configuration. I'm not sure how this can happen, but hopefully this'll help actually perform the checkpoints.
* Look at the output from running the wal checkpointChristopher Baines2023-04-20
| | | | As I think it might be blocked sometimes.
* Use set-car! when sorting the prioritised work queueChristopher Baines2023-04-20
| | | | | As stable-sort! probably doesn't guarantee to alter the list as I was previously expecting.
* Increase frequency of database maintenanceChristopher Baines2023-04-20
| | | | Also log more. This is because I've seen issues with the WAL growing too much.
* More reliably delete the compressed outputsChristopher Baines2023-04-20
|
* Remove redundant appendChristopher Baines2023-04-20
|
* Log more about temporary files in the agentChristopher Baines2023-04-18
|
* Attempt to make with-port-timeouts handle the GC restarting pollChristopher Baines2023-04-17
| | | | | | From what I'm seeing in strace, I think the GC is breaking the timeout behaviour by restarting the syscall, these changes should work around that behaviour.
* Remove the GC protection mechanismChristopher Baines2023-04-17
| | | | Hopefully this is unused now.
* Guard against the hash file being emptyChristopher Baines2023-04-13
|
* Prioritise post build actionsChristopher Baines2023-04-11
| | | | | | | By the priority of the build, and then by the bytes that need uploading. This should help ensure that priority builds get handled first when there's congestion getting data back to the coordinator. Prioritising builds with less data to upload should also keep things moving when uploads are slow as well.
* Add priority support to create-work-queueChristopher Baines2023-04-11
| | | | | | | This isn't ideal as the process-job interface changes when you enable prioritisation, but that's not a big issue. This should enable prioritising post build operations.
* Change - to _ to fix listing post build job derivationsChristopher Baines2023-04-11
| | | | Signed-off-by: Christopher Baines <mail@cbaines.net>
* Add missing joinChristopher Baines2023-04-11
|
* Use underscores for derivation_nameChristopher Baines2023-04-11
| | | | | | As this is more consistent in the JSON responses. Signed-off-by: Christopher Baines <mail@cbaines.net>
* Expose the derived priority to agentsChristopher Baines2023-04-11
| | | | | Rather than the priority, as it's the derived priority that they should be using for decision making.
* Remove datastore-select-allocated-buildsChristopher Baines2023-04-11
| | | | As it's a less well named copy of datastore-list-agent-builds.
* Drop the delay for retrying uploads on failureChristopher Baines2023-04-11
|
* Remove the crude alarm based timeout for submitting outputsChristopher Baines2023-04-11
| | | | | This should be unnecessary now that there's progress on getting the I/O operations to timeout.
* Reduce logging on build failuresChristopher Baines2023-04-11
|
* Include build priority when selecting allocated buildsChristopher Baines2023-04-11
|
* Strip down the guix-dev.scm fileChristopher Baines2023-04-10
| | | | Assume that a recent version of guix will be used.
* Include the build priority when agents fetch buildsChristopher Baines2023-04-10
| | | | This means the agent can use it to prioritise various things.
* Change allocate-builds to update-build-allocation-planChristopher Baines2023-04-10
| | | | As this is a better name.
* Use a timeout when substituting derivations in the publish hookChristopher Baines2023-04-10
| | | | As this can block if the store GC is running.
* Improve event/state id support for eventsChristopher Baines2023-04-03
| | | | | Support the Last-Event-ID header in the events endpoint, and include the event id's in the responses.
* Try to improve hook exception handlingChristopher Baines2023-04-02
| | | | | This should lead to more concise backtraces at least although it may reintroduce the problem where backtraces lead to excessive memory usage.
* Don't call (backtrace) in the build allocatorChristopher Baines2023-04-01
| | | | | It seems to cause the same memory issues as calling (backtrace) with the hooks.
* Give up printing backtraces for exceptions in hooksChristopher Baines2023-03-29
| | | | I think it's causing problems that I'm struggling to reproduce and debug.
* Try and ensure that the non-fibers sleep is used in placesChristopher Baines2023-03-29
| | | | | | When not using fibers. I don't know if a different sleep is being used, and I don't think I've read anything about having to avoid this, but I'm running out of ideas.
* Provide more information in process-event error handlingChristopher Baines2023-03-29
| | | | There's still problems here, but it's unclear where.
* Remove backtrace printing from create-thread-poolChristopher Baines2023-03-29
| | | | | Just in case this is causing a problem with the exception handling within proc.
* Always keep one thread running to process hooksChristopher Baines2023-03-29
| | | | This should reduce the need to keep stopping and starting threads.