Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-09-13 Thread Tony Sarajärvi
This is information I could look up, but would take time, so let's see if you already have the answers  Does this fail 100% of the time now, and since when? Or when did it become flaky? We noticed on our servers, that when we moved the VMs to run on different physical machines in different

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-06-20 Thread Thiago Macieira
On Tuesday, 20 June 2017 02:14:20 PDT Morten Sørvig wrote: > Yes, but the system under test is the Qt network stack, not the OS network > stack. So if the OS network stack is missing or not operable that’s a N/A > result, not a fail. It's not too difficult to write the native code to do the same.

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-06-20 Thread Simon Hausmann
The upmerge went in this morning. qtbase dev should be fine again. In parallel we're investing the root cause. Simon From: Development on behalf of Edward Welbourne Sent:

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-06-20 Thread Edward Welbourne
Morten Sørvig (20 June 2017 11:14): > I agree that getting to the root cause is preferable. We can do both: > blacklist immediately to get integrations going again while > investigating. https://codereview.qt-project.org/196699 has done that, in 5.9; we just need an upmerge to dev to get going

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-06-19 Thread Thiago Macieira
On Monday, 19 June 2017 03:48:42 PDT Morten Sørvig wrote: > - Can we self-test the network interface and QSKIP if it’s not in working > order? That's the test itself: it tries to send a packet back to itself and see if it arrives. > - We can blacklist on CI only: >

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-06-19 Thread Morten Sørvig
> On 16 Jun 2017, at 23:21, Thiago Macieira 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! :

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-06-19 Thread Simon Hausmann
Hi, I've checked that all iptables for IPv4 and IPv6 are empty. Simon From: Development on behalf of Edward Welbourne Sent: Monday, June 19, 2017 11:36:19 AM To: Thiago

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-06-19 Thread Edward Welbourne
Thiago Macieira (16 June 2017 22:23) > 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)] I

Re: [Development] What changed in the RHEL 6.6 machines that cause tst_QUdpSocket::linkLocalIPv6 to fail?

2017-06-16 Thread Thiago Macieira
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: