Re: [PATCH] netapi32/test: Add trace to help narrow down failing test.
On Tue, 2016-11-08 at 10:07 +0000, Alistair Leslie-Hughes wrote:
Based off a test run with extra traces https://testbot.winehq.org/JobDetails.pl?Key=26512&log_201=1#k201 the intermittently failing test is in test_DavGetUNCFromHTTPPath.
The failure is a timeout, so you're likely to find a random test. I think we should concentrate on the earlier tests and figure out where all that time is spent.
On 08/11/16 21:21, Hans Leidekker wrote:
On Tue, 2016-11-08 at 10:07 +0000, Alistair Leslie-Hughes wrote:
Based off a test run with extra traces https://testbot.winehq.org/JobDetails.pl?Key=26512&log_201=1#k201 the intermittently failing test is in test_DavGetUNCFromHTTPPath.
The failure is a timeout, so you're likely to find a random test. I think we should concentrate on the earlier tests and figure out where all that time is spent.
My first attempt at narrowing down this intermittent failure shows that its in test_DavGetUNCFromHTTPPath. Which happens to be the only time this test failed. I've tried to run the test multiple times but without it failing. Having this trace in place until the failing test can be found should hurt to much. Alistair.
participants (2)
-
Alistair Leslie-Hughes -
Hans Leidekker