WebPagetest Forums
99997 ??? - Printable Version

+- WebPagetest Forums (https://www.webpagetest.org/forums)
+-- Forum: WebPagetest (/forumdisplay.php?fid=7)
+--- Forum: Bugs/Issues (/forumdisplay.php?fid=10)
+--- Thread: 99997 ??? (/showthread.php?tid=11141)

99997 ??? - nilskuhn - 05-16-2012 11:52 PM

Hi Pat,

on private instance, version 2.5 I get the following error:
A scripted test returns result code 99997 even though on the agent in IE everything looks fine:
logData    0
navigate    http://www.otto.de/is-bin/INTERSHOP.enfinity/WFS/Otto-OttoDe-Site/de_DE/-/EUR/OV_ViewTemplate-View?Template=popups/shopfinder_frameset&ls=0#lmPromo=la,3,hk,,fl,Promo1
logData    1
setValue    class=text    hamburg
clickAndWait    name=btnSearch
For information (don't know whether that's relevant for the error):
The hole visible content of the site is in an iFrame, so using javascript directly fails:
logData    0
navigate    http://www.otto.de/is-bin/INTERSHOP.enfinity/WFS/Otto-OttoDe-Site/de_DE/-/EUR/OV_ViewTemplate-View?Template=popups/shopfinder_frameset&ls=0#lmPromo=la,3,hk,,fl,Promo1
logData    1
execAndWait    getElementsByClassName('text')[0].value='Test';
execAndWait    getElementsByName('btnSearch')[0].click;

Error reproduced on public agents:

Same test without logData works (but we need to measure single step):

Thanks for help,
regards Nils

RE: 99997 ??? - pmeenan - 05-18-2012 12:46 AM

I opened up a bug so I don't lose track of it: http://code.google.com/p/webpagetest/issues/detail?id=94

I tried it as a combined 2-step script and it still timed out: http://www.webpagetest.org/result/120517_SH_b424fff060311ab3a6eb3100eb2d115c/

I think the one without logdata only worked because the first step completed ok but the second step still caused a timeout on my side somewhere.

RE: 99997 ??? - nilskuhn - 06-13-2012 12:55 AM

something new about this?

RE: 99997 ??? - nmtd - 07-17-2013 09:15 PM

Hi Pat

I am working with Andy Davies on a private WPT project.

I am also getting occasional "result (error code) 99997" on tests targeted at Google Chrome. All other browser types are ok. Issue first occurred on July 10th but was fixed by an agent restart, but problem has just re-occurred and rebooting has not fixed it this time.

URL being tested www1.seatwave.com/the-o2-arena-tickets/venue but seems to do it for any of the url's (any domain) I am testing.

The waterfall appears to complete in the expected time, but the test itself is always recording a timeout.

This is in a private instance. I'm not quite sure of the version (is there a file that shows the version somewhere?) but its from around end April / early May this year.

The chrome agent is Version 28.0.1500.72 m

I have repeated against Dulles and it was OK.

Any ideas/suggestions?



RE: 99997 ??? - zeman - 07-18-2013 05:23 PM

Hi Pat,

I'm seeing a similar issue on SpeedCurve, the run last night generated hundreds of tests where the waterfall looks fine but the page still times out.



have hundreds more of these if you need to debug them. Agree that they all appear to be chrome related.

I'll try upgrading to the latest agent for tonights run.

RE: 99997 ??? - pmeenan - 07-20-2013 03:10 AM

Try updating the test agent. I know that I made changes in the last moth or so to deal with timeouts because of invisible browser activity that was dragging things out: https://sites.google.com/a/webpagetest.org/docs/private-instances#TOC-Updating-Test-Agents

RE: 99997 ??? - zeman - 07-20-2013 07:59 AM

Yep that fixed things for me. It looks like agents get updated quite regularly. Is there anyway for test agents to pull updates directly from the main webpagetest instance so they're always using the latest version?

RE: 99997 ??? - pmeenan - 07-20-2013 08:58 AM

Not currently. I've considered building in support for an update check directly in the server but I was a bit worried about the software automatically doing updates without someone being in control over it. Say it updated right in the middle of the night and broke your testing for example.

RE: 99997 ??? - stef - 07-27-2013 12:30 AM

Same issue here at Fasterize and updating the test agent fixed the issue.
Thanks !

RE: 99997 ??? - nmtd - 07-30-2013 07:18 PM

Thanks Pat.

Update of the agent also appears to have worked for me too.