Stability checker does not recognize "multi-global" test modifications

[annevk]

#5129
https://travis-ci.org/w3c/web-platform-tests/jobs/210612033

Not entirely sure what the problem is here. @bobholt @jugglinmike

[jugglinmike]

By the current configuration, TravisCI runs two identical builds for each
commit in a pull request. The error here is limited to just one of the two
"Chrome stability" jobs, and it describes a timeout after the instruction to
download information about the Chromedriver binary. In light of this, my
suspicion is that the error was caused by network instability. Do you mind if I
re-run the build to verify that it is not a recurring issue?

[annevk]

Sure go ahead.

[jugglinmike]

The manually-triggered build has passed:

https://travis-ci.org/w3c/web-platform-tests/jobs/210612033

Do you think it is safe to close this issue? I realize this is not a particularly satisfying resolution, but I don't see any indication of an error in the project's code.

[annevk]

I think what we actually need to is to recognize the .any.js convention and run the corresponding .any.html and .any.worker.html tests. Same for the .worker.js convention. Would you mind of we reuse this issue for that?

[annevk]

See http://web-platform-tests.org/writing-tests/testharness.html for the documentation of this feature by the way.

[jugglinmike]

Works for me! Although this calls for a change in title...

[jugglinmike]

Yesterday, @jgraham addressed this with the following patches: w3c/wpt-tools#195 and w3c/wptrunner#242. Because the "stability checker" Python script installs the latest version of the wptrunner utility by invoking git from the command line, no change to this repository is required.