Bug#979865: m2crypto FTBFS on IPV6-only buildds
Hi, On 22-02-2021 05:48, Sandro Tosi wrote: >>> it would be easier to enforce to have all buildds configured equally so >>> the package does not fail on a random buildd. >> >> I *guess* that's not trivial as I think it depends on the network their in. > > OTOH it's not ideal to have machines that are supposed to be similar, > being different enough to cause build failure (due to their > configuration, not due to resource constraint). Some discussion has evolved from this and somebody promised me to talk to the responsible people to see if this could be improved. >> m2crypto needs another upload anyways. Without a proper IPv6 solution >> for the tests, can the failing network tests please be disabled in the >> next upload? > > given the 29 failures are all part of test_ssl.py (and make up more > than half of the tests in it) i'm going to skip that file entirely. i > would argue that testing SSL is important for this package, so this > solution is very suboptimal. Ack and agree. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#979865: m2crypto FTBFS on IPV6-only buildds
> > it would be easier to enforce to have all buildds configured equally so > > the package does not fail on a random buildd. > > I *guess* that's not trivial as I think it depends on the network their in. OTOH it's not ideal to have machines that are supposed to be similar, being different enough to cause build failure (due to their configuration, not due to resource constraint). > m2crypto needs another upload anyways. Without a proper IPv6 solution > for the tests, can the failing network tests please be disabled in the > next upload? given the 29 failures are all part of test_ssl.py (and make up more than half of the tests in it) i'm going to skip that file entirely. i would argue that testing SSL is important for this package, so this solution is very suboptimal. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#979865: m2crypto FTBFS on IPV6-only buildds
Hi, On Fri, 29 Jan 2021 20:50:07 +0100 Sebastian Andrzej Siewior wrote: > > The release team considers these bugs release critical. > > it would be easier to enforce to have all buildds configured equally so > the package does not fail on a random buildd. I *guess* that's not trivial as I think it depends on the network their in. m2crypto needs another upload anyways. Without a proper IPv6 solution for the tests, can the failing network tests please be disabled in the next upload? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#979865: m2crypto FTBFS on IPV6-only buildds
control: found -1 0.31.0-1 On 2021-01-24 23:08:27 [+0200], Adrian Bunk wrote: > > The release team considers these bugs release critical. it would be easier to enforce to have all buildds configured equally so the package does not fail on a random buildd. > > and let it migrate to > > testing. After all this bug did not first appear in 0.37.1-1, > >... > > If this is true, then the proper action would be a found indicating the > first broken version. Ah. Looking at all the ipv6 testsuite bugs I saw so far, all of them were there from the very beginning. My guess is that it isn't any different here. I reassigned it to the first upload of 31 which is in stable because 0.31.0-4+deb10u1 failed to build on amd64 for the same reason. A retry passed. > cu > Adrian Sebastian
Bug#979865: m2crypto FTBFS on IPV6-only buildds
On Sun, Jan 24, 2021 at 07:48:55PM +0100, Sebastian Andrzej Siewior wrote: > On 2021-01-12 08:22:05 [+0200], Adrian Bunk wrote: > > Source: m2crypto > > Version: 0.37.1-1 > > Severity: serious > > Tags: ftbfs > > I suggest to lower the severity to important The release team considers these bugs release critical. > and let it migrate to > testing. After all this bug did not first appear in 0.37.1-1, >... If this is true, then the proper action would be a found indicating the first broken version. > Sebastian cu Adrian
Bug#979865: m2crypto FTBFS on IPV6-only buildds
On 2021-01-12 08:22:05 [+0200], Adrian Bunk wrote: > Source: m2crypto > Version: 0.37.1-1 > Severity: serious > Tags: ftbfs I suggest to lower the severity to important and let it migrate to testing. After all this bug did not first appear in 0.37.1-1, it has been exposed after it hit buildd that is IPv6 only. The package built on all release architectures by now. Sebastian
Bug#979865: m2crypto FTBFS on IPV6-only buildds
Source: m2crypto
Version: 0.37.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=m2crypto=amd64=0.37.1-1=1610432018=0
...
I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_m2crypto/build;
python3.9 -m pytest tests
= test session starts ==
platform linux -- Python 3.9.1+, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /<>
collected 374 items
tests/test_aes.py [ 1%]
tests/test_asn1.py [ 3%]
tests/test_authcookie.py ... [ 8%]
tests/test_bio.py ...[ 17%]
tests/test_bio_file.py ... [ 19%]
tests/test_bio_iobuf.py [ 21%]
tests/test_bio_membuf.py .. [ 24%]
tests/test_bio_ssl.py ...[ 26%]
tests/test_bn.py ... [ 27%]
tests/test_dh.py .. [ 28%]
tests/test_dsa.py ...[ 31%]
tests/test_ec_curves.py .. [ 32%]
tests/test_ecdh.py ... [ 32%]
tests/test_ecdsa.py ... [ 34%]
tests/test_engine.py .. [ 36%]
tests/test_err.py . [ 36%]
tests/test_evp.py .. [ 51%]
[ 53%]
tests/test_obj.py .. [ 54%]
tests/test_rand.py ..[ 56%]
tests/test_rc4.py .. [ 56%]
tests/test_rsa.py .. [ 63%]
tests/test_smime.py .[ 69%]
tests/test_ssl.py ...s..F..F...FFF.F.FFs.F.. [ 83%]
... [ 84%]
tests/test_ssl_offline.py . [ 86%]
tests/test_threading.py .. [ 86%]
tests/test_timeout.py ...[ 90%]
tests/test_util.py [ 92%]
tests/test_x509.py ... [100%]
=== FAILURES ===
__ HttpslibSSLSNIClientTestCase.test_IP_call ___
self =
def test_IP_call(self):
no_exception = True
runs_counter = 0
pid = self.start_server(self.args)
for entry in socket.getaddrinfo(self.srv_host, self.srv_port,
socket.AF_INET,
socket.SOCK_STREAM,
socket.IPPROTO_TCP):
ipfamily, socktype, _, _, sockaddr = entry
ip = sockaddr[0]
sock = socket.socket(ipfamily, socktype)
conn = SSL.Connection(self.ctx, sock=sock)
conn.set_tlsext_host_name(self.srv_host)
conn.set1_host(self.srv_host)
runs_counter += 1
try:
conn.connect((ip, self.srv_port))
except (SSL.SSLError, socket.error):
log.exception("Failed to connect to %s:%s", ip, self.srv_port)
no_exception = False
finally:
conn.close()
out, _ = self.stop_server(pid)
> self.assertEqual(
out.count('Hostname in TLS extension: "%s"' % self.srv_host),
runs_counter)
E AssertionError: 0 != 2
tests/test_ssl.py:306: AssertionError
...
=== 29 failed, 343 passed, 2 skipped, 5 warnings in 77.18s (0:01:17) ===
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.9_m2crypto/build; python3.9 -m pytest tests
rm -fr -- /tmp/dh-xdg-rundir-3bUiHX0w
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
make: *** [debian/rules:17: build-arch] Error 25
