Discussion:
Bug#979865: m2crypto FTBFS on IPV6-only buildds
Add Reply
Adrian Bunk
2021-01-12 06:30:02 UTC
Reply
Permalink
Source: m2crypto
Version: 0.37.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=m2crypto&arch=amd64&ver=0.37.1-1&stamp=1610432018&raw=0

...
I: pybuild base:232: cd /<<PKGBUILDDIR>>/.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: /<<PKGBUILDDIR>>
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.FFFF..FFFFFFFFFFFFFFF.FFFFF.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 = <tests.test_ssl.HttpslibSSLSNIClientTestCase testMethod=test_IP_call>

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 /<<PKGBUILDDIR>>/.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
Sebastian Andrzej Siewior
2021-01-24 19:00:02 UTC
Reply
Permalink
Post by Adrian Bunk
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
Debian Bug Tracking System
2021-01-29 20:00:01 UTC
Reply
Permalink
found -1 0.31.0-1
Bug #979865 [src:m2crypto] m2crypto FTBFS on IPV6-only buildds
Marked as found in versions m2crypto/0.31.0-1.
--
979865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979865
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Sandro Tosi
2021-02-22 05:00:02 UTC
Reply
Permalink
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
Sandro Tosi
2021-02-22 05:00:02 UTC
Reply
Permalink
Control: tag -1 pending

Hello,

Bug #979865 in m2crypto reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/m2crypto/-/commit/b793e3fc50971ce59d78dcb3b708a41d30dffeaa

------------------------------------------------------------------------
skip test_ssl.py during tests, more than 50% of its tests faol on an IPv6-only machine; Closes: #979865
------------------------------------------------------------------------

(this message was generated automatically)
--
Greetings

https://bugs.debian.org/979865
Debian Bug Tracking System
2021-02-22 05:00:02 UTC
Reply
Permalink
Post by Sandro Tosi
tag -1 pending
Bug #979865 [src:m2crypto] m2crypto FTBFS on IPV6-only buildds
Added tag(s) pending.
--
979865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979865
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Debian Bug Tracking System
2021-02-22 05:10:01 UTC
Reply
Permalink
Your message dated Mon, 22 Feb 2021 05:03:29 +0000
with message-id <E1lE3NZ-00079v-***@fasolo.debian.org>
and subject line Bug#979865: fixed in m2crypto 0.37.1-2
has caused the Debian Bug report #979865,
regarding m2crypto FTBFS on IPV6-only buildds
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
979865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979865
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...