Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
Fix Released
|
Undecided
|
Iain Lane | ||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm not sure this is the right place to report this, but apparently it's the best way to reach out to Dimitri John Ledkov (https:/
I'm copying the following verbatim from https:/
> The two PRs you referenced to fail in the `make check` unit tests (test-path).
That's correct that test-path failed but it failed in https:/
In https:/
summary: |
- Ubuntu CI that runs test via autopkgtest for systemd on GitHub reports + Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results |
It seems to me that the logs are internally consistent, i. e. the mentioned UPSTREAM_ PULL_REQUEST in the log does match the test results. But they get sent to the wrong PR, i. e. to the wrong statuses API.
E. g. https:/ /api.github. com/repos/ systemd/ systemd/ commits/ 99894b867f1293f 56d181d62f5015c 5a0a8adbda/ status was triggered by https:/ /github. com/systemd/ systemd/ pull/11682 but the referenced logs are for PR #11767. This caused the landing of a regression (that the tests would have noticed).