Search results
Results from the WOW.Com Content Network
Hi all, Can someone help me with the following problem: locations.ini: [locations] 1=Test_loc 2=Public_Dulles 3=Appurify default=Test_loc ; ; These are the top-level locations that are listed in the location dropdown ; Each one points to one or more browser configurations ; [Test_loc] 1=IE 2=Test label=Test Location group=Desktop [Public_Dulles] 1=WPT_Dulles_IE8 label=“WebPagetest.org ...
; These are the browser-specific configurations that match the. configurations; defined in the top-level locations. Each one of these MUST match the. location; name configured on the test agent (urlblast.ini or wptdriver.ini); [IE] browser=IE 8 latency=0 label=“Test Location - IE 8”;browserExe=pagetest.exe key=webpagetest;
I’ve tried to run a test numerous times - tried a couple of different URLS from my site - but each time I get the following issue, “Timed out waiting for the browser to start” Any idea how I get round this ? Thanks.
FWIW I now had the browser fail to load from Israel, Petah-Tiqwa, Chrome, native testing www.universityguideonline.org “timed out waiting for browser to start”
I put some rate limiting on the browser installer yesterday and it looks like I broke a piece so the Chrome and Firefox installers wouldn’t download. I just fixed it but you might need to reboot or terminate and re-launch the ami for it to re-try the install.
Have been looking around trying to find an explanation on what the different colored bands in the “Browser Main Thread” waterfall breakout are representing, as they don’t appear to correlate with the main header coloration. In a discussion today someone mentioned that they might correspond to page events (processing, browser page draw, etc.) but I can’t find a definitive explanation ...
Hi, I have set up a private instance of wpt on aws using docker image. the tests are running every two minutes against the private instance. I have seen a crash in browser (both chrome and firefox) after running continuously every two minutes for a few days. I checked the container, there are no instance of firefox running and it is not able to launch the firefox. its being very inconsistent ...
Learn, share insights and get involved in the WebPageTest community.
I’ve set up a WPT Private Instance with auto-launching agents. Chrome works fine, but if I try to launch a test with Firefox, I get a result of: The testing completed but failed. Invalid browser - Firefox First View: Test Error: Invalid browser - Firefox. My config section in ec2_locations.ini looks like this: [us-west-2] browser=Chrome,Firefox
When using WPT the past couple days, every test (regardless of client domain I try testing), if I use the Chicago, IL servers / Chrome DSL emulator, it says the test completed but failed because it couldn’t load the browser. When I switch to your Denver server, it works fine. HELP! I rely on WPT religiously for my audit work and use multiple test locations. Exact Message: From: Chicago, IL ...