The issue with dnf debuginfo-install has been reported upstream in https://github.com/teemtee/tmt/issues/2988 It seems it hasn't reached downstream yet.

Meanwhile the rpminspect / annocheck issue was reported at https://github.com/fedora-ci/rpminspect-runner/issues/125

Tests timed out. I'm re-triggering them.

FTR: I believe I found the root cause and reported it at https://github.com/fedora-ci/rpminspect-runner/issues/125

FTR: I believe I found the root cause and reported it at https://github.com/fedora-ci/rpminspect-runner/issues/125

annocheck's lto tests should be skipped, but the arguments we set are not being respected and that's causing the failure. I'm going to waive this test result.

I run the annocheck test by hand and I can't reproduce this failure:

Running annocheck inspection...      pass

I'm re-triggering the tests. It looks like annocheck ignored its parameters.

I reported the issue with dnf debuginfo-install in https://github.com/teemtee/tmt/issues/2988

This update has been unpushed.

I confirmed that -z relro -z now is being used. I wonder if this test had a false positive...

We're getting a weird error here:

Package Vendor changed from "Fedora Project" to "unknown" in zlib-ng

I don't think we can progress with this error.

The new compat packages (e.g. clang17) requires an update to https://github.com/rpminspect/rpminspect-data-fedora/pull/46/files.

It looks like the CI is having issues to run all tests and results are still missing even after 7 hours of the submission. I cannot re-trigger the tests. We might need to waive these results.

The CI appears to be broken. I'm waiving the results.

Important detail: this new version depends on python3-specfile >= 0.25.0, but this is missing in the specfile. Without updating both packages we get the following error:

utils.py          ERROR  'Specfile' object has no attribute 'update_version'
Unexpected exception occurred,
please fill an issue here:
https://github.com/packit/packit/issues

After updating both packages, this is working well.

It seems there was a communication issue when running the lldb automated tests. I'm re-triggering them.

LLVM 17.0.2 has finally reached the stable repositories, so I'm re-enabling auto-stable on this update.

@decathorpe, ack. I have just disabled auto-stable based on karma or time. I will re-enable that after FEDORA-2023-67f0f8d186 is submitted to the repositories. Thanks!