| Commit message (Expand) | Author | Age |
|---|
| * | Start to better describe when builds are waiting to happen•••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.
| Christopher Baines | 2023-11-02 |
| * | Add "i686-linux" back to systems to consider•••As the substitute availability is better now.
| Christopher Baines | 2023-11-02 |
| * | Make "large-number-of-builds" an issue status•••Rather than these falling within the unknown status.
| Christopher Baines | 2023-10-29 |
| * | Add a new patches missing status | Christopher Baines | 2023-10-18 |
| * | Refactor fetching data from patchwork•••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.
| Christopher Baines | 2023-10-17 |
| * | 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•••So it's easier to find issues that have specific problems.
| Christopher Baines | 2023-09-27 |
| * | Make reviewed-looks-good an issue status | Christopher Baines | 2023-09-26 |
| * | Set thread names•••To help with debugging.
| Christopher Baines | 2023-07-25 |
| * | Add a new package changes page•••And make some refactoring to make this easier.
| Christopher Baines | 2023-07-05 |
| * | Improve error reporting on the issue page•••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.
| Christopher Baines | 2023-06-16 |
| * | Move issue related code from the server module | Christopher Baines | 2023-06-15 |
| * | Better manage the data for issues•••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.
| Christopher Baines | 2023-03-11 |
| * | Stop looking at i686-linux builds•••As they're unreliable at the moment.
| Christopher Baines | 2022-12-12 |
| * | Try to handle the case with more failures better•••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.
| Christopher Baines | 2022-12-05 |
| * | Stop looking at the succeeding count for the overall issue status•••Since if you remove some packages, the number of succeeding builds will be
lower, but this isn't strictly a bad thing.
| Christopher Baines | 2022-11-21 |
| * | 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•••Don't require some succeeding builds for every tested system.
| Christopher Baines | 2022-10-14 |
| * | Consider if builds haven't been submitted when computing overall status | Christopher Baines | 2022-10-05 |
| * | Fix computing the overall status•••Pick the highest index, since this corresponds to the "worst" state.
| Christopher Baines | 2022-10-05 |
| * | 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 |