aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* WIPwip-reproducibility-pie-chartChristopher Baines2019-12-15
|
* Improve the revision derivation-outputs pageChristopher Baines2019-12-15
| | | | Neaten up the display of the hashes, and add a reproducibility status column.
* Fix group-to-alistChristopher Baines2019-12-15
| | | | To not just append elements to the alist.
* Move group-to-alist to the model utils moduleChristopher Baines2019-12-15
| | | | So it can be more widely used.
* Show the possible failure reasons on the build pageChristopher Baines2019-12-15
| | | | When the build status is "Failed (dependency)".
* Add a function to find the builds required for a build that failedChristopher Baines2019-12-15
|
* Link to the build pages from the derivation pageChristopher Baines2019-12-15
|
* Add a page for each buildChristopher Baines2019-12-15
|
* Split out select-build-by-build-server-and-derivation-file-nameChristopher Baines2019-12-15
| | | | | | Create select-build-id-by-build-server-and-derivation-file-name, which just returns the id, and then a variant that returns more fields for making a page for each build.
* Improve select-builds-with-context-by-derivation-file-nameChristopher Baines2019-12-15
| | | | To find builds for equivalent derivations.
* Add a builds page for a specific revisionChristopher Baines2019-12-14
| | | | Like the /builds page, but filtered for a specific revision.
* Extend select-build-stats to allow filtering by revisionChristopher Baines2019-12-14
|
* Break down the build stats by build serverChristopher Baines2019-12-14
|
* Drop the default number of results on the derivation outputs pageChristopher Baines2019-12-14
| | | | To have it load quicker, but also because 100 results aren't necessary.
* Add "Fixed output" to the options for Reproducibility statusChristopher Baines2019-12-14
| | | | | On the derivation outputs page, as some derivations are reproducible by definition, so it's good to identify and exclude these.
* Implement the reproducibility status filterChristopher Baines2019-12-14
| | | | On the derivation-outputs page.
* Add a parameter to form-horizontal-control affect multiple valuesChristopher Baines2019-12-14
| | | | | Previously, the behaviour was to accept multiple values, but enable just allowing one value to be entered.
* Improve the next page links on the revision pagesChristopher Baines2019-12-13
| | | | | To add or update the relevant query parameter, rather than replacing all the query parameters with the new value.
* Add a utility to help generate next page linksChristopher Baines2019-12-13
|
* Improve the select-build-stats functionChristopher Baines2019-12-12
| | | | Account for equivalent derivations, rather than counting them as unknown.
* Fix the select-derivations-with-no-known-buildChristopher Baines2019-12-12
| | | | | | | | The equivalent_derivations table was an experiment that didn't work, so switch to using the derivations_by_output_details_set table. Also take the build server id as input, as this allows selecting derivations which have no known build for the relevant build server.
* Add options to the query-build-servers scriptChristopher Baines2019-12-12
| | | | So you can select to query specific build servers.
* Remove non-existent export from the derivation moduleChristopher Baines2019-12-12
|
* Add a page to show derivation outputs for a revisionChristopher Baines2019-12-12
|
* Add a function to select the outputs in a revisionChristopher Baines2019-12-12
|
* Add a results count to the revision derivations pageChristopher Baines2019-12-12
|
* Fix the all-results/limit handling in the revision derivatinos controllerChristopher Baines2019-12-12
|
* Fix related builds in select-derivations-in-revisionChristopher Baines2019-12-12
| | | | | | Rather than just counting builds where the derivation matches, select builds based on the derivation outputs, which accounts for different but equivalent derivations.
* Add new derivation_output_details_set_id column to the builds tableChristopher Baines2019-12-12
| | | | | As this will hopefully provide a faster way of associating derivations with builds.
* Start storing and identifying sets of derivation outputsChristopher Baines2019-12-12
| | | | | | | | | | | Derivations are effectively equivalent if they produce the same set of outputs, which is possible because of the equivalence of fixed output derivations. A fixed output derivation can be different, but equivalent, because it produces the same fixed output. To better allow tracking equivalent derivations, primarily to allow working out what derivations might correspond to a build, store the sets of derivation outputs, and which derivations they relate to.
* Add some database indexesChristopher Baines2019-12-12
|
* Add a page to show the derivations in a revisionChristopher Baines2019-12-12
|
* Add a utility to generate a span for the status of a buildChristopher Baines2019-12-12
|
* Add a function to select derivations in a revisionChristopher Baines2019-12-12
|
* Fix and improve fetching outputs to fetch from build serversChristopher Baines2019-12-12
| | | | | | | | | | | The join on derivation_outputs was completely wrong, so fix that. Also, rather than only selecting outputs where there's a corresponding build, just eliminate outputs where there is an entry in the nars table, fetched from the relevant build server. Also just look at x86_64-linux derivations, because there's no filtering on relevant derivations for a build server at the moment.
* Fix query in select-derivations-with-no-known-buildChristopher Baines2019-12-12
| | | | | | | | | | | | | Rather than eliminating any derivation that has a known build, eliminate those derivations, but also equivalent derivations as well. For selecting the derivations in a revision, join on the equivalent derivations, as all the equilalent derivations need checking as well, as it's unknown which one Cuirass would have associated the build against. Also, filter for x86_64-linux, to avoid checking for crossbuilt things. This should be replaced by some way of describing what derivations a build server has.
* Display the build server URL when fetching dataChristopher Baines2019-12-12
|
* Fix the match statement in select-build-by-build-server-and…Christopher Baines2019-12-12
|
* Improve variable names in fetch-narinfo-filesChristopher Baines2019-12-12
|
* Populate the narinfo_fetch_records tableChristopher Baines2019-12-12
|
* Deduplicate builds and add a unique indexChristopher Baines2019-12-12
| | | | | | | Duplicate builds could creep in if the code to create them ran concurrently. I didn't exclude them initially, as I was unsure if there should be such a restriction, but at least for now, Cuirass builds map exactly to a single derivation, so use the same restriction here.
* Change nar_urls size to bigintChristopher Baines2019-12-12
| | | | As some nars can be bigger than the size of an int.
* Change nars size to bigintChristopher Baines2019-12-12
| | | | As some nars can be bigger than the maximum size of an int.
* Add a table to record where narinfo files were fetched fromChristopher Baines2019-12-12
| | | | Otherwise it's hard to associated narinfo files to build servers.
* Add an index on the derivation_file_name field in the builds tableChristopher Baines2019-12-12
| | | | As this helps when finding builds relating to specific derivations.
* Move build-status helpers to the html-utils moduleChristopher Baines2019-12-12
|
* Include nars on the output pageChristopher Baines2019-12-12
|
* Add a new page for the narinfos associated with an outputChristopher Baines2019-12-12
|
* Add a page for each signing keyChristopher Baines2019-12-12
|
* Add a new html-utils moduleChristopher Baines2019-12-12
| | | | To store code used for rendering HTML across multiple controllers.
generated by cgit v1.2.3 (git 2.25.4) at 2024-05-05 12:26:43 +0000