| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
| |
For the new and removed package sections.
|
| | |
|
| |
|
|
| |
As it's a bit unnecessary.
|
| |
|
|
|
|
|
|
|
| |
Split the derivations up in to some groups, and run
invalidate-derivation-caches! inbetween to try and reduce the memory
usage.
Also make a couple of other changes to reduce memory usage or protect
against errors.
|
| |
|
|
| |
This is useful for debugging purposes.
|
| |
|
|
|
| |
In particular, things like undefined variables in the package
definition.
|
| |
|
|
|
| |
Just load in the ones that are not already in the database, as this
will hopefully be faster and require less memory.
|
| |
|
|
|
|
| |
Compute all derivations at once in the inferior, avoiding round trips
to hopefully speed it up. Close the inferior earlier to free up
memory, and add more debugging output.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A large proportion of these changes relate to changing the way
packages relate to derivations. Previously, a package at a given
revision had a single derivation. This was OK, but didn't account for
multiple architectures.
Therefore, these changes mean that a package has multiple derivations,
depending on the system of the derivation, and the target system.
There are multiple changes, small and large to the web interface as
well. More pages link to each other, and the visual display has been
improved somewhat.
|
| | |
|
| |
|
|
| |
To try and process the backlog a bit.
|
| | |
|
| |
|
|
| |
As I don't think these endpoints can return more than 1 result.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
For showing more information about builds, revisions and derivations.
|
| |
|
|
| |
On the comparison page.
|
| | |
|
| |
|
|
| |
These will allow tracking what's going on with build servers.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Currently, I think the desired commit can be missing, if patches come
in gradually, and the series changes after the first laminar job has
been run. Therefore, try to ignore some errors and just delete the
job.
|
| | |
|
| |
|
|
| |
To describe why this job was enqueued.
|
| |
|
|
|
| |
Both to the packages and derivations packages, as well as the JSON
representation of the pages.
|
| |
|
|
|
| |
The primary use I have in mind for this is producing a list of strings
suitable for building a limited Cuirass job with.
|
| |
|
|
|
|
| |
Provide JSON versions of the existing HTML compare and
compare/derivations pages. Refactor the code and extract some
functions to make this a little less painful.
|
| |
|
|
|
| |
Previously, some extra data from the query would be added on to the
end of the version. This change prevents that from happening.
|
| | |
|
| | |
|
| |
|
|
|
| |
Use some experimental functionality to run the inferior repl in a
container. This provides some isolation.
|
| |
|
|
|
| |
Once inferiors can provide some isolation, this will make building
guix in this way safer.
|
| | |
|
| |
|
|
|
|
| |
These changes mean that more information about derivations is
recorded. There are a number of corresponding changes in the database
schema that are not tracked in the repository unfortunately.
|
| | |
|
| |
|
|
|
|
| |
Previously, the connections were not closed, so eventually PostgreSQL
would run out. Using a pool of connections would be better, but as a
short term solution, just close the connection after each request.
|
|
|
This is a service designed to provide information about Guix. At the
moment, this initial prototype gathers up information about packages,
the associated metadata and derivations.
The initial primary use case is to compare two different revisions of
Guix, detecting which packages are new, no longer present, updated or
otherwise different.
It's based on the Mumi project.
[1]: https://git.elephly.net/software/mumi.git
|