[Bug 2045000] [NEW] nvme-stas 2.3-1ubuntu1 autopkgtest hanging on s390x

Launchpad Bug Tracker 2045000 at bugs.launchpad.net
Tue Nov 28 11:39:09 UTC 2023


You have been subscribed to a public bug by Olivier Gayot (ogayot):

On s390x, the test-suite for nvme-stas hangs and then times out:

596s test_clear (test-gtimer.Test.test_clear) ... ok
596s test_new_timer (test-gtimer.Test.test_new_timer) ... ok
596s test_start_timer (test-gtimer.Test.test_start_timer) ... ok
596s test_AsyncTask (test-gutil.GutilUnitTest.test_AsyncTask) ... ok
596s test__data_matches_ip (test-iputil.Test.test__data_matches_ip) ... ok
596s test_get_interface (test-iputil.Test.test_get_interface)
10600s Check that get_interface() returns the right info ...

I am able to reproduce the issue consistently on a s390x host.

The function that is hanging is the following:

> def net_if_addrs():
>     with socket.socket(socket.AF_NETLINK, socket.SOCK_RAW) as sock:
>         sock.sendall(GETADDRCMD)
>         nlmsg = sock.recv(8192)     # This call blocks forever

where:

> GETADDRCMD = _nlmsg(RTM_GETADDR, NLM_F_REQUEST | NLM_F_ROOT,
_ifaddrmsg())

and

> def _ifaddrmsg(family=0, prefixlen=0, flags=0, scope=0, index=0):
>     '''Implement this C struct:
>     struct ifaddrmsg {
>         __u8   ifa_family;
>         __u8   ifa_prefixlen;  /* The prefix length        */
>         __u8   ifa_flags;      /* Flags            */
>         __u8   ifa_scope;      /* Address scope        */
>         __u32  ifa_index;      /* Link index           */
>     };
>     '''
>     return struct.pack('<BBBBL', family, prefixlen, flags, scope, index)

This is presumably an endianness issue since s390x uses big-endian.

** Affects: nvme-stas (Ubuntu)
     Importance: Undecided
     Assignee: Olivier Gayot (ogayot)
         Status: New

** Affects: nvme-stas (Debian)
     Importance: Unknown
         Status: Unknown


** Tags: update-excuse
-- 
nvme-stas 2.3-1ubuntu1 autopkgtest hanging on s390x
https://bugs.launchpad.net/bugs/2045000
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.




More information about the Ubuntu-sponsors mailing list