catchpoint/WebPageTest.bulk-tester

New test instances aren't recognized

Closed this issue · 3 comments

There are some new test instances, like Frankfurt_Ruxit, Falkenstein, Berlin, which haven't names like ec2-eu-central-1. On trying to add these instances like Frankfurt_Ruxit:Chrome, after update scenarios they aren't recognized in the list of test instances.

The email that had your API WebPageTest API key lists the location that an API key can be used with - primarily the Akamai supported locations, Dulles & London

There was an WebPageTest bug that allowed other locations to be used and this got fixed at some point (it's not known what fixed the bug)

So first thing to check is whether you API key actually supports the locations you're trying to use

Sure, it does. I run successful tests with locations like

Frankfurt, Safari, Cable | eu-central-1:Safari
Frankfurt_EC2, Chrome, Cable | ec2-eu-central-1:Chrome

These both working locations are listed under https://github.com/WPO-Foundation/webpagetest/blob/af73f7de8549f123df67d932eb91cd070ee26d01/www/settings/ec2_locations.ini.

But under https://www.webpagetest.org/getLocations.php?f=html are listed additional german locations (Frankfurt_Ruxit, Falkenstein, Berlin) - and i don't know how their instances are named correctly. These instances are working from the WPT GUI (webpagetest.org). I guess, i need their correct region name, as for Frankfurt - eu-central-1.

The wired thing is: if i look into the raw data of the test result i was running through webpagetest.org, i see as location just
<location>Berlin:Chrome</location>
This notation however doesn't work in Gtables.

Hi @e-orlov,

If I'm not mistaken, the list of locations at https://www.webpagetest.org/getLocations.php?f=html includes locations that are not available through the API.

This is the list of locations available through the API, the ones that you mention are not available there:
https://www.webpagetest.org/getLocations.php?f=html&k=A