Test runner doesn't run worker tests properly

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 by @plehegar on 25 Oct 2016, 12:46 UTC:

http://w3c-test.org/tools/runner/index.html
will attempt to run
http://w3c-test.org/hr-time/basic.worker
instead of
http://w3c-test.org/hr-time/basic.worker.html

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 (comment) by @Ms2ger on 25 Oct 2016, 15:16 UTC:

@youennf

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 (comment) by @youennf on 25 Oct 2016, 15:20 UTC:

Will look at it tomorrow

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 (comment) by @Ms2ger on 25 Oct 2016, 15:30 UTC:

FTR, caused by #126

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 (comment) by @halindrome on 25 Oct 2016, 17:23 UTC:

Actually, my PR is bogus. If your system is trying to access "*.worker" it means the manifest is messed up. Re-run the manifest generation and it should sort out.

./manifest -r

I am going to withdraw that PR.

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 (comment) by @youennf on 26 Oct 2016, 09:15 UTC:

Fixing manifest generation at w3c/wpt-tools#132

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 (comment) by @gsnedders on 30 Oct 2016, 17:06 UTC:

So, this is fixed?

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 (comment) by @halindrome on 31 Oct 2016, 13:39 UTC:

As far as I know this is fixed. @plehegar should confirm though.

[wpt-issue-mover]

Originally posted as w3c/wpt-tools#129 (comment) by @plehegar on 09 Nov 2016, 19:06 UTC:

[this is in progress but I'm having problems to run wptserve and no time to debug it :(]