| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
As it uses a transaction with a wider scope.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, a connection was passed through the code handling the
request. When queries were performed, this could block the thread though,
potentially leaving the server unable to serve other requests.
Instead, this now runs queries in a pool of threads. This should remove the
possibility of blocking the threads used by the web server, and in doing so,
some of the queries have been parallelised.
I''m still not sure about the naming and syntax, but I think the functionality
is a sort of step forward.
|
| |
|
|
|
| |
Use the derivation-file-name from the database, rather than the query
parameter.
|
| |
|
|
|
| |
Because the Guix Build Coordinator doesn't mark builds blocked by failures as
failed-dependency, they're just left as scheduled.
|
| |
|
|
|
|
| |
Builds from the Guix Build Coordinator might not have timestamps, and the id
from the build server is more important, as one build server can build the
same derivation many times.
|
| |
|
|
|
| |
This is to allow for build servers where only the substitutes should be
queried, and it shouldn't be assumed that they're running Cuirass.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
When the build status is "Failed (dependency)".
|
| | |
|
| | |
|
|
|
Allow for build status information to be submitted by POST request. This
required some changes to the builds and build_status tables, as for example,
the Cuirass build id may not be available, and the derivation may not be know
yet, so just record the derivation file name.
|