https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65785
Bug ID: 65785
Summary: libgo TestIPv4MulticastListener test fails on machine
with no network connection
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: vries at gcc dot gnu.org
I observed the following failure:
...
--- FAIL: TestIPv4MulticastListener (0.00s)
testing.go:278: First ListenMulticastUDP on <nil> failed: listen udp
224.0.0.254: setsockopt: no such device
FAIL
FAIL: net
src/libgo/testsuite/gotest: line 514: gotest-timeout: No such file or directory
...
Once in a while my test machine loses the wlan0 interface, which is it's only
connection to the internet. My guess is that this makes this libgo test fail.
This seems to be confirmed by this timeline:
1. my first test run (using a non-bootstrap compiler) completed libgo.log
without failures (well, apart from the usual TestMemoryProfiler fail, see
PR64683)
(16:10)
2. kernel log shows: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
(16:50)
3. my second test run (using a bootstapped compiler) completed libgo.log
with above failure twice, once with and once without -m32.
(20:10)
4. I ran ifconfig, and found that wlan0 is not connected
I saw a related PR48017: Network tests should fail gracefully without network
connectivity. A variable GCCGO_RUN_ALL_TESTS was introduced to manage this
problem, but subsequently removed (as noted here:
https://gcc.gnu.org/ml/gcc-patches/2011-09/msg01568.html ), though the variable
is still listed in the README.gcc.
It was removed because
(https://gcc.gnu.org/ml/gcc-patches/2011-09/msg01652.html ):
...
Running the net test now is intentional--it used to depend on an
Internet connection, but it no longer does.
...
