> On 16 Jun 2017, at 23:21, Thiago Macieira <[email protected]> wrote: > > On Friday, 16 June 2017 13:23:07 PDT Thiago Macieira wrote: >> QDEBUG : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) >> QHostAddress("fe80::250:56ff:feab:4818%eth1") >> FAIL! : tst_QUdpSocket::linkLocalIPv6(WithoutProxy) >> '(neutralReadSpy.count() >>> 0)' returned FALSE. () >> >> Loc: [../tst_qudpsocket.cpp(1600)] > > Emergency workaround: https://codereview.qt-project.org/197753 > (compiles and works for me on bare metal, no test on a VM) > > This commit basically disables the test entirely on virtual machines. If any > QtNetwork developers use virtual machines, please make sure you get > bare-metal > hardware for all three platforms. You won't be doing your job if you continue > with VMs.
This does seem a bit heavy-handed to me. - Can we self-test the network interface and QSKIP if it’s not in working order? - We can blacklist on CI only: https://codereview.qt-project.org/#/c/197692/ (modifying that patch to blacklist all Linux CI if needed.) Morten _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
