Control: stunnel4: runtime check on openssl too tight
Hi Sebastian, On 07-05-2022 18:22, Sebastian Andrzej Siewior wrote:
Usertags: flaky
Why do you conclude that? Normally we call something flaky if it has a reasonable amount of failures in pure testing environments (so no migration runs). I'm not seeing that for tunnel4 on amd64, nor arm64.
The debci testsuite failed for all architectures after the recent
openssl upload
https://ci.debian.net/data/autopkgtest/testing/amd64/s/stunnel4/21436404/log.gz
Am I right to assume as per
| logs/results.log:DEBUG: 2022-05-07 04:07:41,445: [get_version] Trying to
obtain the version of
/tmp/autopkgtest-lxc.algiqp59/downtmp/build.oOV/src/tests/../src/stunnel
| logs/results.log:DEBUG: 2022-05-07 04:07:41,446: [get_version] Started
`/tmp/autopkgtest-lxc.algiqp59/downtmp/build.oOV/src/tests/../src/stunnel
-version` as process 1544
| logs/results.log:CRITICAL: 2022-05-07 04:07:41,449: [main] Something went
wrong: Stunnel was compiled and run with various OpenSSL versions
…
| autopkgtest [04:07:41]: test upstream: -----------------------]
| upstream FAIL non-zero exit status 1
| autopkgtest [04:07:41]: test upstream: - - - - - - - - - - results - - - - -
- - - - -
| autopkgtest [04:07:41]: @@@@@@@@@@@@@@@@@@@@ summary
| debian-python PASS
| upstream FAIL non-zero exit status 1
that the error is that it was compiled against one version (1.1.1n)
and then tested against another version (1.1.1o)?
stunnel4 -version reports:
| Compiled with OpenSSL 1.1.1n 15 Mar 2022
| Running with OpenSSL 1.1.1o 3 May 2022
and it is fine, the ABI is stable.
If your claim is true (and I trust it is), I do agree that it seems that the test (and I guess this comes from a runtime check) is too strict. Retitling accordingly.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
