| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Handle issues.guix GraphQL queries failing better | Christopher Baines | 2024-04-23 |
| | | |||
| * | Sort the patches before applying them to the git branch. | Vivien Kraus | 2024-04-16 |
| | | | | | | | | | | | | | | | | | | By default, the patches are not ordered. Because of the unreliability of e-mail delivery, they can be received completely out of order. Patchwork may also re-order them, and they may get ordered by commit author date (or, equivalently, e-mail Date header). Both possibilities lead to failure to apply patches if the order is incorrect for two patches that do not commute. The patch name contains a header: [bug#xxx,v12,i/n] where "i" is the variable part and indicates the patch number. Git pads "i" with zeros if needed. The string order of the names is thus the true commit order. * guix-qa-frontpage/manage-patch-branches.scm (create-branch-for-issue): Sort patches according to their "name". | ||
| * | Fix checking for unknown commits | Christopher Baines | 2024-04-02 |
| | | |||
| * | Fix ordering of simple-format call | Christopher Baines | 2024-04-02 |
| | | |||
| * | Add more logging around checking base branch changes | Christopher Baines | 2024-04-02 |
| | | |||
| * | Enable checking for base revision changes for all branches | Christopher Baines | 2024-04-02 |
| | | |||
| * | Fix not deleting some patch branches | Christopher Baines | 2024-04-01 |
| | | | | | When the patches were for a non-master branch. | ||
| * | Reduce the number of changes compared to master for branches | Christopher Baines | 2024-03-30 |
| | | | | | | As it was rather high, and it doesn't make sense to be merging a branch if there are lots of changes. | ||
| * | Try to better handle debbugs being unavailable | Christopher Baines | 2024-03-26 |
| | | |||
| * | Add a buffer to prevent deleting some branches that aren't found | Christopher Baines | 2024-03-17 |
| | | | | | To reduce instances of branches getting repeatedly deleted then recreated. | ||
| * | Make some module tweaks | Christopher Baines | 2024-03-17 |
| | | |||
| * | Update .envrc | Christopher Baines | 2024-02-26 |
| | | |||
| * | Add new TODO entry | Christopher Baines | 2024-02-26 |
| | | |||
| * | Ignore build-already-processed errors when canceling builds | Christopher Baines | 2024-02-26 |
| | | |||
| * | Account for builds to keep when canceling branch builds | Christopher Baines | 2024-02-22 |
| | | |||
| * | Add an information flow diagram | Christopher Baines | 2024-01-20 |
| | | |||
| * | Fix cancel-builds-not-for-revision | Christopher Baines | 2023-12-13 |
| | | | | | To actually cancel all the builds. | ||
| * | Cancel builds in a loop | Christopher Baines | 2023-12-13 |
| | | | | | | To ensure they're all canceled, since they might not all be returned initially when querying with #:relationship 'no-dependent-builds. | ||
| * | Make sure builds are canceled | Christopher Baines | 2023-12-13 |
| | | |||
| * | Cancel builds before submitting new ones | Christopher Baines | 2023-11-26 |
| | | | | | | This should handle the case where we want to cancel a build then submit a new one for the same output. | ||
| * | Cancel and resubmit builds where the derivation has changed | Christopher Baines | 2023-11-26 |
| | | | | | | | But the output remains the same. This will hopefully avoid some instances where the data service deletes the derivation as it corresponds to a removed revision and the build can't start because of the missing derivation. | ||
| * | Tweak error handling around talking to Mumi | Christopher Baines | 2023-11-06 |
| | | | | | | | I think requests to Mumi were being responded to with 502's, and that led QA to delete all the patch branches. This should hopefully stop that happening in the future. | ||
| * | Drop the number of patch issues to show/process | Christopher Baines | 2023-11-04 |
| | | | | | | As beid which currently runs data.qa.guix.gnu.org is running out of disk space. | ||
| * | Fix the package changes table on the branch page | Christopher Baines | 2023-11-03 |
| | | | | | And only display the "below systems" message if there are any. | ||
| * | Use a different symbol when waiting for build results | Christopher Baines | 2023-11-03 |
| | | | | | | And group these issues towards the top of the patches list since they potentially can be merged if there's not too many builds remaining. | ||
| * | Change text for the "waiting for build results" status | Christopher Baines | 2023-11-03 |
| | | |||
| * | Start to better describe when builds are waiting to happen | Christopher Baines | 2023-11-02 |
| | | | | | | Don't use the same styling as failed builds on the issue page, and also separate out the systems which don't count towards the issue status. | ||
| * | Add "i686-linux" back to systems to consider | Christopher Baines | 2023-11-02 |
| | | | | | As the substitute availability is better now. | ||
| * | Set higher rebuild number limit for patch series. | Julien Lepiller | 2023-11-02 |
| | | | | | | This allows building Java updates which impact 600 packages per architecture. | ||
| * | Add a few more items to the TODO list | Christopher Baines | 2023-11-02 |
| | | | | | From the discussions at the Reproducible Builds summit. | ||
| * | Use call-with-blocked-asyncs when calling call-with-zlib-input-port | Christopher Baines | 2023-11-01 |
| | | | | | Since it uses dynamic-wind that's incompatible with fibers. | ||
| * | Link to the /reproducible-builds page | Christopher Baines | 2023-11-01 |
| | | |||
| * | Make the branches table shorter | Christopher Baines | 2023-11-01 |
| | | |||
| * | Add a Guix logo to the header | Christopher Baines | 2023-11-01 |
| | | |||
| * | Properly handle multiple package outputs in reproducible.json.gz | Christopher Baines | 2023-11-01 |
| | | |||
| * | Add a simple package page | Christopher Baines | 2023-10-31 |
| | | |||
| * | Generate a reproducible.json file | Christopher Baines | 2023-10-31 |
| | | | | | Which can hopefully be consumed by https://ismypackagereproducibleyet.org/ | ||
| * | Add a reproducible-builds page to display data and issues | Christopher Baines | 2023-10-30 |
| | | | | | Maybe this will be a useful starting point. | ||
| * | Sort and filter the branch package reproducibility table | Christopher Baines | 2023-10-30 |
| | | | | | Removing systems for which substitutes aren't available. | ||
| * | Fetch and display package reproducibility information for branches | Christopher Baines | 2023-10-29 |
| | | | | | This involved some refactoring of branch data in general. | ||
| * | Make "large-number-of-builds" an issue status | Christopher Baines | 2023-10-29 |
| | | | | | Rather than these falling within the unknown status. | ||
| * | Avoid timeouts blocking creating issue branches | Christopher Baines | 2023-10-27 |
| | | |||
| * | Delete the create branch for issue logs | Christopher Baines | 2023-10-27 |
| | | | | | | When looking at creating the branch, to ensure the log inserted (if any) is fresh. | ||
| * | Fix checking for changes against master | Christopher Baines | 2023-10-22 |
| | | |||
| * | Support filtering by branch | Christopher Baines | 2023-10-21 |
| | | |||
| * | Handle the case when a series has no patches | Christopher Baines | 2023-10-21 |
| | | | | | In patchwork-series->branch. | ||
| * | Highlight the intended branch on the issue page | Christopher Baines | 2023-10-21 |
| | | |||
| * | Start applying patches to non-master branches | Christopher Baines | 2023-10-21 |
| | | | | | If this is indicated when the patch is submitted. | ||
| * | Check if all patches have been received earlier | Christopher Baines | 2023-10-21 |
| | | |||
| * | Add parse-patch-name | Vivien Kraus | 2023-10-21 |
| | | | | | | | | This is a cut down version of the original patch. Using this information will require some refactoring first. Signed-off-by: Christopher Baines <mail@cbaines.net> | ||