#349 rpminspect-1.11's new DIAGNOSTICS result is mishandled as a failure
Closed by msrb. Opened by ppisar.

https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-pipeline/job/master/110808/testReport/(root)/tests/ reports:

/diagnostics    0 ms    Failed

The new diagnostics test output is https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-pipeline/job/master/110808/testReport/(root)/tests/_diagnostics/:

Result: DIAGNOSTICS
1) Version information for libraries and programs used by rpminspect as well as storage requirements.  This result is for informational and diagnostic purposes only.
Waiver Authorization: Not Waivable
Details:
rpminspect version 1.11
zlib version 1.2.11
libmagic version 541
libclamav version 0.103.6
librpm version 4.18.0-alpha1
libxml version 20914
json-c version 0.15
libcurl version 7.83.1 (OpenSSL/3.0.2 zlib/1.2.11 brotli/1.0.9 libidn2/2.3.2 libpsl/0.21.1 (+libidn2/2.3.2) libssh/0.9.6/openssl/zlib nghttp2/1.47.0 OpenLDAP/2.6.1)
libarchive version 3.6.1 (zlib/1.2.11 liblzma/5.2.5 bz2lib/1.0.8 liblz4/1.9.3 libzstd/1.5.2)
libyaml version 0.2.5
OpenSSL version 3.0.2 15 Mar 2022
xmlrpc-c version 1.51.0
msgunfmt (GNU gettext-tools) 0.21
annocheck version 10.73.
abidiff version 2.0.0
kmidiff version 2.0.0
Space required to download artifacts: 4201424 bytes (4 MiB)
Space required to unpack artifacts: 8861954 bytes (8 MiB)
Result: DIAGNOSTICS
2) Command line arguments used to invoke rpminspect.
Waiver Authorization: Not Waivable
Details:
/usr/bin/rpminspect -c /usr/share/rpminspect/fedora.yaml --format=json --output=results.json --verbose --release=fc37 --profile=rawhide perl-Text-Bidi-2.16-2.fc37 88877009

Yet Fedora CI evaluates it as a failure. DIAGNOSTICS result should not raise a failure.


Ouch, all new runs seem to fail on this.

Metadata Update from @msrb:
- Issue assigned to msrb

https://github.com/rpminspect/rpminspect/commit/c4b3399c51addb978ee04de2eb4b1f4b7f10898d

That's it. I have not idea why INFO was inappropriate.

I've patched CI so "DIAGNOSTICS" will be a "good" result. I also restarted bunch of affected jobs (many of them are still queued/running).

Metadata Update from @msrb:
- Issue status updated to: Closed (was: Open)

Metadata