network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Bug #1731283 reported by Seth Forshee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned
Revision history for this message
Seth Forshee (sforshee) wrote :

autopkgtest [13:37:31]: test wpa-dhclient: [-----------------------
modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.14.0-6-generic
ERROR

======================================================================
ERROR: setUpClass (__main__.T)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/autopkgtest.J2UcbH/build.Dbb/network-manager-1.8.4/debian/tests/network_test_base.py", line 47, in setUpClass
    subprocess.check_call(['modprobe', 'cfg80211'])
  File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['modprobe', 'cfg80211']' returned non-zero exit status 1.

----------------------------------------------------------------------
Ran 0 tests in 0.002s

FAILED (errors=1)
autopkgtest [13:37:32]: test wpa-dhclient: -----------------------]

tags: added: kernel-adt-failure
Revision history for this message
Seth Forshee (sforshee) wrote :

This and other errors are related to lacking the cfg80211 module, which we do not build for s390. However we did not build it in artful either, and we currently have the same version of network-manager in artful and bionic, so it's odd that the tests are failing in bionic and not in artful.

Revision history for this message
Seth Forshee (sforshee) wrote :

Tests were previously getting skipped for s390, due to "Restrictions: ... isolation-machine" in the test control file. Possibly some sort of infrastructure problem detecting that the tests are running in a container.

Revision history for this message
Seth Forshee (sforshee) wrote :

Seems that s390x ADT does now run in VMs, which explains the change.

Since we don't have wireless support in our s390x kernels, these failures are expected. Seems the tests will need to be changed to skip these tests or make them expected failures.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.