Current time: 08-26-2019, 07:23 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
problems with Chrome 16 / FF 3.6
01-11-2012, 11:44 PM
Post: #1
problems with Chrome 16 / FF 3.6
Hi,

I am using version 2.5 of wpt.

I've problems running tests with Chrome 16 / FF 3.6 on Windows XP-Agents in a LAN (wpt-server on another machine in same LAN). I've installed the agent-patch from http://www.webpagetest.org/work/update/wptupdate.zip. Cause I wasn't sure whether automatic update worked I installed the patch manually. Both Browsers open, try to load the URL to test after some seconds but fail and run into timeout. Opening the browsers manually I can load the URL.

Tests run with urlblast-controlled IE 7/8 work on same agents.

Any suggestions/ideas?
Regards, Nils
Find all posts by this user
Quote this message in a reply
01-13-2012, 06:06 AM
Post: #2
RE: problems with Chrome 16 / FF 3.6
Check to make sure you don't have any files in work/update on your server. The distributions usually include the agent update there and the auto-update may be reverting your agents to the version that shipped with 2.5.

Thanks,

-Pat
Visit this user's website Find all posts by this user
Quote this message in a reply
01-13-2012, 08:18 PM
Post: #3
RE: problems with Chrome 16 / FF 3.6
The problem was due to http-proxy configured on agent-machine. I removed the chrome-option "--no-proxy-server" from chrome-section of wptdriver.ini. Now tests with chrome are working.

For FF these settings seem to be managed through profiles. In default-profile the proxy-settings are correct and manually opened I can use the proxy-settings and reach any url's. Which profile is used for wpt-testruns with FF? And how can I configure a http-proxy or just to use the system-proxy-settings for that profile?

Regards, Nils
Find all posts by this user
Quote this message in a reply
01-13-2012, 10:26 PM
Post: #4
RE: problems with Chrome 16 / FF 3.6
WPT isn't generally meant to test through proxies (they completely change how browsers work and fetch resources). You can look at templates/Firefox/prefs.js and compare that one to the one in your default Firefox profile. Any settings you add/change there will get used by the WPT firefox profile.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 2 Guest(s)