Test completed, but no waterfall displayed and no requests information


I have problem with some of my agents. I tried to reinstall them but problem persists on some machines.

All metrics are present in test results but request list is empty and as a result waterfall is not displayed.

I did some investigation and found that 1_IEWTR.txt.gz file is not present in test results.

Example of the test results is available here: https://www.dropbox.com/s/fa4rmbyhjzy1six/84f1b22753c4cb9a1e42f41e6fde5110.tgz?dl=0.

I use wptdriver version 190 and HEAD version of WPTServer.

How can I diagnose what problems wptdriver faces? Is it possible to activate any debugging and logging?

I’ve just checked that urlblast works correctly at the same machine.

You can grab a debug build here: http://www.webpagetest.org/releases/debug/ and then run debugView ( http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx ) to get a detailed trace. (run it as an administrator and enable global capture).

Do you see issues for non-SSL sites as well?

Thanks, I will try it tomorrow.

Yes, it happens to any test I run on these particular machines. I do not have control on how OS is installed on them so I cannot correlate this problem to anything I know.

Seems that debug version upgrades itself to the newest, not debug (190).

Is it OK?

Is debug version 190 of wptdiver available?

I just pushed release and debug versions of 192 though it’s probably easiest for your debugging if you just disable updates on your server (rename work/update/wptupdate.ini) while you’re debugging.


Finally I managed to collect debug log from the test with no waterfall data.

I cannot find anything from it that can help to solve this problem unfortunately.

Patrick, are you able to find anything obvious in logs attached? Apparently something is being automatically deployed on my agent workstatnions one by one and all my test environment gradually becomes useless.

Sorry, I’ve been traveling (getting back tonight) and haven’t had a chance to look yet.

I just took a quick look and it looks like all the pieces are hooked up and working so it’s not clear where it is broken. I may have to send you a debug build with more tracing (the winsock hooks don’t log any data by default and the end of the test doesn’t log anything about the requests it sees).

I’ll work on the added tracing on my flight back but in the meantime does your update history show anything that might be suspicious? Browser, Antivirus, EMET or other updates?

It is really hard for me to get any information about what and when was updated. Machines I use for running wpt agents are provided to me as a courtesy of remote branches of company I work for. I would like to avoid asking them embarrassing questions :wink:

I think that debugging this problem can have added value for further development of WPT.

Thanks Patrick for your help!

Best regards,

I just updated the 192 debug build to trace a lot more detail in the sockets path. From the looks of the traces you sent I don’t see any of the traffic that I’d normally expect to see around data we get from the raw sockets so I suspect that’s probably the source of the issue.

It might be impossible to fix if I can’t reproduce it locally though because I’ll need to figure out what is going on with the winsock calls and why they aren’t visible.


I’ll try to collect as much information as it is possible.

let’s try with these results

I don’t know,I’ve done something,but it doesn’t work…

[color=#8e8e97]etui samsung galaxy note 4[/color]
[color=#8e8e97]coque samsung galaxy s5[/color]

I might not be able to make any progress with it if I can’t reproduce it myself. I don’t see any of the actual socket send or recv calls (though there are some socket connect calls so it should be the correct process). If it was an IE change I’d expect to see all of the IE 11 agents having issues so I’m not really sure where to go with it.

Thanks for investigating it, Patrick. Maybe one day I will be able to identify what has been deployed to machines I use. I requested to reinstall one of them but it has not changed anything.

Was there any resolution for this, I am trying to setup a new pvt inactance of wpt on Win 7-64 bit machine and am facing the same issue

No, I still have this problem for some PCs. One of them was renstalled but it persists. The only workaround is to use urlBlaster but it is not compatible with IE versions greater than 9 nor any other browser.

Installing IE11 solved the problem. Probably somehow it was related to wptdriver working with IE9 or some updates installed together with IE11 removed the cause of the problem.