| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
| |
As this will be useful for QA to say whether the package builds reproducibly
or not.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Move in the direction of being able to run multiple inferior REPLs, and use
some vectors rather than lists in places (maybe this is more efficient).
|
|
|
|
| |
And remove the monitor, as I'm not sure it's necessary.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Listing remote branches through libgit2 will list branches that don't exist on
the remote. I think branch-list is more listing branch references, and you can
have references to a remote branch where the remote branch doesn't exist. This
isn't very useful here though, as I'm trying to work out what remote branches
exist.
There's remote-ls which might help, but I can't figure out how to get the
commits for branches from that.
Therefore, just bodge the two things together in to a big mess. I seem to be
able to get commits from branch-list that hopefully match what's on the
remote (although I'm not confident about this), and I think remote-ls does
allow checking what branches exist.
|
|
|
|
| |
To go along with just-update-cached-checkout.
|
|
|
|
| |
As it's causing problems with the guix-patches repository.
|
|
|
|
| |
As getmail treats output to stderr as the operation failing.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is mostly a workaround for the occasional problems with the guix-commits
mailing list, as it can break and then the data service doesn't learn about
new revisions until the problem is fixed.
I think it's still a generally good feature though, and allows deploying the
data service without it consuming emails to learn about new revisions, and is
a step towards integrating some kind of way of notifying the data service to
poll.
|
| |
|
| |
|
|
|
|
| |
To handle characters like +.
|
|
|
|
|
| |
I'm not sure why this wasn't the way it worked previously. This should avoid
unconstrained use of PostgreSQL connections.
|
| |
|
| |
|
|
|
|
| |
To avoid a long blocking query.
|
| |
|
|
|
|
| |
As previously it only applied to system tests.
|
|
|
|
| |
Use fibers more, leaning in on the non-blocking use of Squee for parallelism.
|
|
|
|
| |
As the ordering from Guix seems to be non-deterministic.
|
|
|
|
|
|
|
|
| |
There's an issue where sometimes for i686-linux and armhf-linux, only a few
package derivations are computed.
This commit tries to simplify the code, and adds some conditional logging for
the guix package, which might help reveal what's going on.
|
| |
|
| |
|
|
|
|
|
| |
This helps with replacements, as the original package is usually higher up in
the file.
|
|
|
|
|
| |
Make sure to log any errors, and also use a more efficient approach sending
less data to the inferior.
|
| |
|
|
|
|
| |
Better to timeout early.
|
|
|
|
| |
As one thread per core is probably unnecessary.
|
|
|
|
| |
To help with debugging
|
| |
|
| |
|
|
|
|
|
|
| |
Now that squee cooperates with suspendable ports, this is unnecessary. Use a
connection pool to still support running queries in parallel using multiple
connections.
|
| |
|
| |
|
| |
|
|
|
|
| |
In the compare package derivations response.
|
| |
|
| |
|
|
|
|
|
| |
This will allow restarting them independently, leaving it up to the operator
to ensure that all processes are compatible.
|
|
|
|
| |
This will keep the substitute information more up to date.
|
|
|
|
| |
So that triggering a check for substitutes can be integrated in.
|
| |
|
|
|
|
|
|
| |
So that this can be used by the qa-frontpage.
This should be improved and generalised.
|
|
|
|
|
| |
The previous changes only affected searching for package derivations, and they
also didn't work.
|
|
|
|
|
| |
This will help when using this to submit builds, since you won't end up
ignoring derivations with canceled builds.
|
|
|
|
| |
As this will help identify when the service restarts.
|
| |
|