Created attachment 600628 [details]
rng-tools 6.7: tests/test-suite.log
# TOTAL: 3
# PASS: 2
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
rngtest: bits received from input: 2000064
rngtest: bits sent to output: 1980000
rngtest: FIPS 140-2 successes: 99
rngtest: FIPS 140-2 failures: 1
rngtest: FIPS 140-2(2001-10-10) Monobit: 0
rngtest: FIPS 140-2(2001-10-10) Poker: 0
rngtest: FIPS 140-2(2001-10-10) Runs: 1
rngtest: FIPS 140-2(2001-10-10) Long run: 0
rngtest: FIPS 140-2(2001-10-10) Continuous run: 0
rngtest: input channel speed: (min=794.729; avg=2033.421; max=3814.697)Mibits/s
rngtest: FIPS tests speed: (min=16.984; avg=30.165; max=31.064)Mibits/s
rngtest: output channel speed: (min=1.693; avg=9.655; max=18.626)Gibits/s
rngtest: Program run time: 64926 microseconds
FAIL rngtesturandom.sh (exit status: 1)
Created attachment 600630 [details]
In the log it says "See tests/test-suite.log". So I need that file for further analysis. Can you consistently reproduce this? Were you running rngd already at the time of this merge? If you system was low on entropy, this test may fail. It's not an indication of the package failure however.
tests/test-suite.log is pasted in the first comment - that's its whole content.
This is not a new installation, but just a world update, so I think I had the package installed before. I don't know what is rngd is, and I don't have it in "ps aux", and I don't have it in /usr/bin
> If you system was low on entropy, this test may fail.
I think the tests should be hermetic and not depend on state of my system at that moment in time. I'll try to rebuild it to check whether it happens again.
Eh. I think in the installation guide I missed the step of adding it to the boot level... And it's in usr/sbin, which is why I didn't see it in bin
So, if the test relies on rngd running already, is it testing the rngd which is running, or the new version of the package which is being installed?