| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | 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 |