Adam Williamson

We have rather more 'flavors' than just server and workstation; some tests run on server, workstation and kde, so cannot be properly distinguished if we're only tagging server and workstation....

Waivers should include the test 'scenario' if the gating policy specifies one. If they don't, they're overbroad (they may match more results than intended) and trigger an issue in Greenwave...

### Explain what happens Looking through Fedora openQA test failures, I caught one where the FreeIPA realm join test failed because it just span forever after hitting the Join button:...

With the new release of mock - 3.2 - it seems that one can no longer run mock as root. If you try to do so, you get an error...

Docs refer to `Mojo::IOLoop::Delay`, which has been removed in 9.0

3

The examples in the docs include one that relies on `Mojo::IOLoop::Delay`, which has been removed from Mojolicious 9.0. Not sure if there's an alternative way to do what that example...

Test fails on 32-bit

1

Similar to [core](https://github.com/roboptim/roboptim-core/issues/102), one of the trajectory tests fails on 32-bit compile (with GCC 5.1.1): ``` 15: /builddir/build/BUILD/roboptim-trajectory-3.1/tests/cubic-b-spline-matplotlib.cc(113): error in "trajectory_cubic_b_spline_matplotlib": check output->match_pattern () failed. Mismatch at position 8040 ```...

If you try to use `e2fsck` from e2fsprogs 1.46.5 or earlier to check a filesystem created with e2fsprogs 1.47.0, it fails: May 25 14:08:46 fedora systemd-fsck[566]: /dev/vda2 has unsupported feature(s):...

docker-podman: stricter container ID regex to avoid bad matches

5

In testing an environment using the docker provider backed by podman-docker, I kept running into a problem where the first time I tried to bring up a container it would...

When an auto-obsoleted update is edited with a new build, it does not go back to testing and no koji-build-group.build.complete message is published

3

Just noticed this when fixing https://bodhi.fedoraproject.org/updates/FEDORA-2024-c0e4857caa . It got auto-unpushed for -3 karma. I edited the update with a new build, and its karma was reset, but it stayed in...

RFE: ability to designate updates as addressing issues in any tracker, not just Bugzilla

4

These days, all tracking of Fedora issues no longer happens in bugzilla.redhat.com: * The desktop team directs issues for GNOME to gitlab.gnome.org in almost all cases * The IoT team...