Test results shared across multiple pull requests

psss commented

2026-01-29 14:12:25 +00:00

Owner

When a package uses identical commit across fedora/epel branches, results from the CI are displayed across all pull requests with the same commit. Here's an example of a set of pull requests created by packit for a recent tmt release:

The result is that it's a bit hard to identify which branches had the actual test failures and majority of the test results are confusing and irrelevant for that particular pull request.

When a package uses identical commit across fedora/epel branches, results from the CI are displayed across all pull requests with the same commit. Here's an example of a set of pull requests created by packit for a recent `tmt` release: * https://src.fedoraproject.org/rpms/tmt/pull-request/331 * https://src.fedoraproject.org/rpms/tmt/pull-request/332 * https://src.fedoraproject.org/rpms/tmt/pull-request/333 * https://src.fedoraproject.org/rpms/tmt/pull-request/334 * https://src.fedoraproject.org/rpms/tmt/pull-request/335 The result is that it's a bit hard to identify which branches had the actual test failures and majority of the test results are confusing and irrelevant for that particular pull request.

psss commented

2026-01-29 14:15:07 +00:00

Author

Owner

@lecris, @lachmanfrantisek, will this possibly be improved by Packit taking care of the Fedora CI testing?

lecris commented

2026-01-29 15:03:16 +00:00

Owner

@lecris, @lachmanfrantisek, will this possibly be improved by Packit taking care of the Fedora CI testing?

Unfortunately no. This is a Pagure issue primarily. But even with Forgejo, we do not have ways of linking a status to a PR. Made an issue on our forge to hopefully get this a stronger voice in forgejo: forge/forge#342

> @lecris, @lachmanfrantisek, will this possibly be improved by Packit taking care of the Fedora CI testing? Unfortunately no. This is a Pagure issue primarily. But even with Forgejo, we do not have ways of linking a status to a PR. Made an issue on our forge to hopefully get this a stronger voice in forgejo: https://forge.fedoraproject.org/forge/forge/issues/342

lecris commented

2026-01-29 20:36:09 +00:00

Owner

Well actually with Packit as Fedora CI things are slightly better because the branch name is in the check, example: https://src.fedoraproject.org/rpms/python3.14/pull-request/140

lachmanfrantisek commented

2026-02-01 06:33:38 +00:00

Owner

Packit tries to use a different name so it's differentiable.

How most forges attach status to a commit for a reason. UI just need to show the head commit status and that's all. It survives push to a PR smoothly. Pagure used to do PR flags, but it was very hard and unreliable to have

Packit tries to use a different name so it's differentiable. How most forges attach status to a commit for a reason. UI just need to show the head commit status and that's all. It survives push to a PR smoothly. Pagure used to do PR flags, but it was very hard and unreliable to have

lachmanfrantisek commented

2026-02-01 06:34:51 +00:00

Owner

But having it for a commit AND attach to a PR might help.