Updated Chrome/Firefox Agent

WebPageTest Private Instances
1

The Chrome 16 update (and Firefox 8) changed some of the permissions that the browser extension we use needed to ask for so if you are seeing an issue on a private instance where Chrome launches but doesn’t start testing you should update the agent to see if that solves the issue.

You can get the latest wptdriver agent here: http://www.webpagetest.org/work/update/wptupdate.zip

You can install the update manually or by using the built-in agent update mechanism.

To update it manually:
[list]
[]Make sure there is no wptupdate.zip and wptupdate.ini in your work/update folder on the server
[]Stop wptdriver
[]Unzip the contents of wptupdate.zip over the directory where the old wptdriver was running from
[]Re-start wptdriver.exe
[/list]

To use the update mechanism:
[list]
[]Copy wptupdate.zip to the work/update folder on your server
[]Extract wptupdate.ini from wptupdate.zip and place it in the work/update folder next to the zip file
[/list]

I’m not quite ready for a 2.6 release yet which is why it is coming as a stand-alone agent update.

Thanks,

-Pat

2

Hi,
thanks for the hotfix, I was just wondering about chrome-test-failure.
Would you suggest to disable auto-updating of chrome-browser on agents to secure stable testing? Or is an occurrence of souch incompatibilities unlikely in nearer future?

3

I think after Chrome 17 is will be a lot less likely (next update). We were using some experimental APIs that migrated to the mainstream and the permissions requirements changed. With Chrome 17 I believe all the APIs we use are production ones so there should not be any more changes like that.

With how frequently Chrome updates, I think it would be a LOT more effort to keep up with releases if you disable the automatic updates. I’m actually trying to figure out a good way to auto-update Firefox as well because of the 6-week cycles.

One thing that may help that I’m going to look into is a way for private installs to automatically pull agent updates from the public webpagetest server. Still, that may be riskier than some people want to run.

4

I followed the instructions above to install the wpt update. But Chrome still just starts up on a request but does not load the page. My version of Chrome is 16.0.912.63.

I believe there were no errors during the update process. All of the wpt files have an updated date (12/21 or 12/22) and that includes the extension files.

Something else I should do or check? Thanks.

5

When chrome is launched, can you check chrome://extensions and make sure that the WebPagetest extension is loaded?

6

It is loaded and enabled.

7

Chrome is still not running the plugin. Should I just be waiting for the new version of WebPageTest? Or is there something else I can try?

8

I don’t think waiting would help because the same code works everywhere else I have tried it so we don’t have any fixes that would be targeting it. I may have to send you a debug build of wpthook that logs a bunch of information.

Any chance the agent update reverted? If you updated manually and the old automatic update files are still in work/update then the agent would have re-installed the old version automatically.

9

I am also seeing this behavior. I ran the update on one of the AMIs, rebooted, and chrome just stops at the about:blank page and eventually times out.

One thing I noticed is that after I run an update (either manual or with the updater) my wtpdriver.exe file is 247kb, but after I run it it stops, replaces itself with a 230kb file, and starts again. Is that normal?

10

Check the work/update folder on your server. The server is probably delivering the older version as an “update” (it will deliver whatever is in the folder as long as the versions don’t match - including downgrading).

11

Chrome Agent return deferent IEWTR.txt file format

IE URLblast return below contain schema (Date, Time, Event…)

Date Time Event Name IP Address Action Host URL Response Code Time to Load (ms) Time to First Byte (ms) Start Time (ms) Bytes Out Bytes In Object Size Cookie Size (out) Cookie Count(out) Expires Cache Control Content Type Content Encoding Transaction Type Socket ID Document ID End Time (ms) Descriptor Lab ID Dialer ID Connection Type Cached Event URL Pagetest Build Measurement Type Experimental Event GUID Sequence Number Cache Score Static CDN Score GZIP Score Cookie Score Keep-Alive Score DOCTYPE Score Minify Score Combine Score Compression Score ETag Score Flagged Secure DNS Time Connect Time SSL Time Gzip Total Bytes Gzip Savings Minify Total Bytes Minify Savings Image Total Bytes Image Savings Cache Time (sec) Real Start Time (ms) Full Time to Load (ms) Optimization Checked CDN Provider
… and Data

but wptDriver return only data without schema

… no Schema…!!
5/8/2012 7:34:48 202.131.30.12 GET www.naver.com / 200 37 26 135 543 28848 28454 no-cache, no-store, must-revalidate text/html gzip 3 11 172 1 -1 -1 100 -1 0 -1 -1 -1 -1 -1 0 0 -1 -1 -1 28848 0 0 0 0 0 -1 0 0 0 0 135 0 0
5/8/2012 7:34:48 175.158.0.74 GET nv1.ad.naver.com /adshow?unit=002AG 200 59 59 263 715 4058 3723 no-cache, no-store, must-revalidate text/html 3 18 322 2 -1 -1 0 -1 -1 -1 -1 -1 -1 -1 0 0 -1 -1 -1 4058 1888 0 0 0 0 -1 0 0 0 5 140 0 0
5/8/2012 7:34:48 222.122.212.108 GET castbox.shopping.naver.com /index.nhn 200 137 136 331 597 7799 7284 Thu, 01 Jan 1970 00:00:00 GMT no-cache text/html gzip 3 12 468 3 -1 -1 100 -1 -1 -1 -1 -1 -1 -1 0 0 -1 -1 -1 7799 0 0 0 0 0 -1 0 0 0 1 142 0 0

12

Yes, the header is stripped from the raw files. The WebPagetest code knows how to deal with the difference and if you retrieve through the csv.php entry point the headers will be applied automatically. Otherwise you can just check the first record in the file to see if it is “Date” and if not apply the header (or skip if it is).