I'm having some problems getting a private instance of WPT working with Firefox. I'm reasonably sure the problem is configuration related, but I can't spot exactly where. IE works OK. I am guessing the problem is in WPT retrieving the job - they queue up and never go anywhere.

Below are my config files for URLBlast and the WPT driver, as well as locations.ini. I have made a couple of changes / additions in an effort to get things working, so some of the config entries are probably unnecessary. Can anyone spot where I'm going wrong?

Also of interest: If I try to kick off a test pointed at my Firefox instance, WPT reports that there are 6 other tests waiting. This doesn't seem right as the work/jobs/<etc> folders are empty, so I'm not sure how it calculates this figure?

;
; Tese 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)
;

;
; For a wptdriver configuration (chrome, firefox), the browser labels here
; MUST match the labels used in wptdriver.ini
;

[Local-WPTDriver]
browser=Chrome,Firefox
label="Local"
connectivity=LAN
;
; This is an exaple of a "remote" configuration where tests can be proxied to a remote
; webpagetest instance. The test will be run by the remote server but the results
; will be downloaded to the local server and deleted from the remote agent
;
; Each location that you want to use from the remote server needs to be configured
; individually on the local configuration (location names do not need to match)
;
; To use the public webpagetest.org instance you will need an API key
;

Yes, chrome and IE are working fine. The problem seem to exist with Firefox only. The firefox browser launches with url - "http://127.0.0.1:8888/blank.html" but doesn't run the test cases.
I've updated the agent folder with the 6 files available in the wptupdate.zip but it doesn't seem to work out in my case.