99997 ???

Support
1

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:
http://www.webpagetest.org/result/120516_YW_CVH/

Same test without logData works (but we need to measure single step):
http://www.webpagetest.org/result/120516_6A_CVW/

Thanks for help,
regards Nils

2

I opened up a bug so I don’t lose track of it: Google Code Archive - Long-term storage for Google Code Project Hosting.

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.

3

something new about this?

4

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 Ticketmaster.co.uk - Resale Tickets | Sell Tickets | Ticket Exchange by Ticketmaster 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?

Regards

Perry

5

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.

http://donut.speedcurve.com/video/compare.php?tests=130718_M3_2-r%3A2-c%3A0-e%3Afull&thumbSize=200&ival=500&end=full

http://donut.speedcurve.com/video/compare.php?tests=130717_4W_36E&thumbSize=200&ival=500&end=full

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.

6

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

7

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?

8

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.

9

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

10

Thanks Pat.

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