| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
When processing jobs, this is mostly to allow setting GUIX_DOWNLOAD_METHODS.
|
| |
|
|
|
| |
The guix-dameon WAL is still growing excessively, so avoid doing anything with
the long running store connection except registering temporary roots.
|
| | |
|
| |
|
|
|
|
|
|
| |
Just have one fiber at the moment, but this will enable using fibers for
parallelism in the future.
Fibers seemed to cause problems with the logging setup, which was a bit odd in
the first place. So move logging to the parent process which is better anyway.
|
| |
|
|
| |
This is a bit ugly, but might speed up computing derivations for system tests.
|
| |
|
|
|
|
|
|
|
|
|
| |
Generating system test derivations are difficult, since you generally need to
do potentially expensive builds for the system you're generating the system
tests for. You might not want to disable grafts for instance because you might
be trying to test whatever the test is testing in the context of grafts being
enabled.
I'm looking at skipping the system tests on data.guix.gnu.org, because they're
not used and quite expensive to compute.
|
| | |
|
| |
|
|
| |
It now returns #f or a list, rather than the empty list or a nested list.
|
| | |
|
| |
|
|
| |
To help with getting them running on Guile 3.
|
| | |
|
| | |
|
| |
|
|
|
| |
As entries from incomplete previous runs can effect the test, so clean out any
old data before the test begins.
|
| |
|
|
| |
So that the tests don't require a store connection.
|
| |
|
|
|
| |
As this will enable registering temporary roots, to avoid store items being
garbage collected.
|
| |
|
|
| |
These are the ones that relate to Guix pull.
|
| | |
|
| |
|
|
| |
If the channel-news-for-commit function is present.
|
| |
|
|
| |
To allow for passing the channel to channel-news-for-commit.
|
| |
|
|
|
| |
These changes allow processing emails again, and just creating job and branch
entries where data is missing.
|
| |
|
|
|
| |
The load-new-guix-revision tests aren't transactional, so truncate some tables
after running the tests.
|
| |
|
|
|
|
| |
This should speed up processing new revisions, reduce latency between finding
out about new revisions and processing them, as well as help manage memory
usage, by processing each job in a process that then exits.
|
| | |
|
| |
|
|
| |
This helps when working out which connection to the database is doing what.
|
| |
|