Hi Thiago, maybe https://codereview.qt-project.org/#/c/233693/ helps with this case.
Cheers, Lars On 30 Jun 2018, at 18:14, Thiago Macieira <thiago.macie...@intel.com<mailto:thiago.macie...@intel.com>> wrote: It has failed now four times in the last 24 hours and is responsible for all failures that didn't fail with a network issue first. I ran it on my machine and it took about a minute, while I was also compiling something else. Given the usual 30:1 slowness of the CI, it could take as much as half an hour there. I tried to add a change to increase the timeout https://codereview.qt-project.org/233691 but Liang pointed out that my inspiration is a change by Rohan McGovern back in 2012: dd3e4f1dbe8 tests/auto/network/access/qnetworkreply/test/test.pro (Rohan McGovern 2012-05-29 16:20:22 +1000 2) testcase.timeout = 600 # this test is slow So it's highly unlikely that the current CI still obeys this setting. I'm assuming therefore that it's hidden somewhere non-obvious (= anywhere not next to the test itself) and therefore I'm just bugging you. I'll create a P0 if my current integration fails again. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
