| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Use Guile Knots | Christopher Baines | 2024-12-17 |
| | | | | | Rather than the build coordinator for fibers utilties. | ||
| * | Refresh issues less often and reduce the parallelism | Christopher Baines | 2024-08-15 |
| | | | | | To try and avoid overloading the QA data service. | ||
| * | Use guix-data-service-error->sexp in issue-data | Christopher Baines | 2024-06-22 |
| | | |||
| * | Query for branch changes by system | Christopher Baines | 2024-06-22 |
| | | | | | | | And don't store the full data in the database, just the counts. This should avoid timeout issues with the data service and speed up storing and fetching the data from the cache. | ||
| * | Reduce issue-data parallelism | Christopher Baines | 2024-06-20 |
| | | | | | To avoid overloading data.qa.guix.gnu.org. | ||
| * | Improve issue-data parallelisation | Christopher Baines | 2024-06-08 |
| | | |||
| * | Add delay logging to issue-data | Christopher Baines | 2024-06-08 |
| | | |||
| * | Cache series entries for each individual issue | Christopher Baines | 2024-05-18 |
| | | | | | So that you don't have to load the whole list from the cache each time. | ||
| * | Use fibers for refreshing issue and branch data | Christopher Baines | 2024-05-17 |
| | | |||
| * | 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. | ||
| * | Make "large-number-of-builds" an issue status | Christopher Baines | 2023-10-29 |
| | | | | | Rather than these falling within the unknown status. | ||
| * | Add a new patches missing status | Christopher Baines | 2023-10-18 |
| | | |||
| * | Refactor fetching data from patchwork | Christopher Baines | 2023-10-17 |
| | | | | | | | | | | Fetch pages one at a time until the required number of patch series has been fetched. This commit also changes the ordering from issue number to the series ID, which will mean that series associated with older issues will be prefered over newer issues with older series. | ||
| * | Instrument the refresh patch data thread | Christopher Baines | 2023-10-16 |
| | | |||
| * | Show the changes to cross derivations on issue pages | Christopher Baines | 2023-10-15 |
| | | |||
| * | Add some more issue statuses | Christopher Baines | 2023-09-27 |
| | | | | | So it's easier to find issues that have specific problems. | ||
| * | Make reviewed-looks-good an issue status | Christopher Baines | 2023-09-26 |
| | | |||
| * | Set thread names | Christopher Baines | 2023-07-25 |
| | | | | | To help with debugging. | ||
| * | Add a new package changes page | Christopher Baines | 2023-07-05 |
| | | | | | And make some refactoring to make this easier. | ||
| * | Improve error reporting on the issue page | Christopher Baines | 2023-06-16 |
| | | | | | | | This regressed when more data started to be cached, since the exceptions couldn't be stored in the db, but now some of the information makes it through. | ||
| * | Move issue related code from the server module | Christopher Baines | 2023-06-15 |
| | | |||
| * | Better manage the data for issues | Christopher Baines | 2023-03-11 |
| | | | | | | | Don't use the full derivation changes data when trying to render the page, as that might be quite large. Instead, compute and cache the counts, and then use this for rendering. | ||
| * | Stop looking at i686-linux builds | Christopher Baines | 2022-12-12 |
| | | | | | As they're unreliable at the moment. | ||
| * | Try to handle the case with more failures better | Christopher Baines | 2022-12-05 |
| | | | | | | | If more builds are failing in the target revision, but because those builds were previously blocked, this shouldn't be treated the same as if these packages are broken. | ||
| * | Stop looking at the succeeding count for the overall issue status | Christopher Baines | 2022-11-21 |
| | | | | | | Since if you remove some packages, the number of succeeding builds will be lower, but this isn't strictly a bad thing. | ||
| * | Look at a subset of the systems for the overall issue status | Christopher Baines | 2022-11-20 |
| | | |||
| * | Fix issues with unknown builds being seen as good | Christopher Baines | 2022-11-17 |
| | | |||
| * | Start highlighting build issues in the overall patch status | Christopher Baines | 2022-11-17 |
| | | |||
| * | Split out blocked builds from unknown builds | Christopher Baines | 2022-11-15 |
| | | |||
| * | Tweak issue overall status criteria | Christopher Baines | 2022-10-14 |
| | | | | | Don't require some succeeding builds for every tested system. | ||
| * | Consider if builds haven't been submitted when computing overall status | Christopher Baines | 2022-10-05 |
| | | |||
| * | Fix computing the overall status | Christopher Baines | 2022-10-05 |
| | | | | | Pick the highest index, since this corresponds to the "worst" state. | ||
| * | Improve overall statuses to take tags in to account | Christopher Baines | 2022-10-05 |
| | | |||
| * | Try to start highlighting patch issues which pass some checks | Christopher Baines | 2022-09-17 |