.any.js results in wasm/ don't show any results

[foolip]

In WPT, .any.js tests generate a number of other tests, like .any.html and .any.worker.html.

In wasm/, for reasons I don't understand yet, the .any.js files are also included in the results:
https://wpt.fyi/results/wasm/jsapi?label=master&label=experimental&aligned&q=any.js

Drilling into one of the tests, it doesn't load any results table or anything:
https://wpt.fyi/results/wasm/jsapi/constructor/compile.any.js

Screenshot:

@nairnandu and I were looking at this in preparation for Interop 2025.

cc @ajklein @past @DanielRyanSmith

[past]

This seems to be limited to wasm/jsapi tests only, and not the automatically imported ones in wasm/core.

[DanielRyanSmith]

Some initial thoughts after a quick look at this:

• The fact that there is no view when looking at a single test, but they are visible on the results list implies there is something incorrect with the summary file that populates the results page (example file), since the single test view and the results page are populated from different data.
• In the summary file above, the wasm "any.js" results exist, but are marked with an "S" status, which is short for "SKIP".

I still don't know why this would be the case only for wasm/jsapi tests, however.

[DanielRyanSmith]

One more interesting note: this seems to be a longstanding issue, as these same "any.js" results are visible on runs from over a year ago:

https://wpt.fyi/results/wasm/jsapi?q=any.js&run_id=5160056105992192

[foolip]

Hmm, a SKIP seems unlikely to spontaneously appear, I wonder if it's from the original results in wptreport.json files?

[gsnedders]

Hmm, a SKIP seems unlikely to spontaneously appear, I wonder if it's from the original results in wptreport.json files?

Yes:

{
  "test": "/wasm/jsapi/js-string/basic.any.js",
  "subsuite": "",
  "subtests": [],
  "status": "SKIP",
  "message": "Executor does not support jsshell",
  "duration": 0
}

See: https://github.com/web-platform-tests/wpt/blob/bc4e61c278fcb26c5ccc074669aff8bf421ec823/tools/wptrunner/wptrunner/wptrunner.py#L269-L270

Specifically, this test is a jsshell test, see: https://github.com/web-platform-tests/wpt/blob/3bab3d2f7bc07e368cd69cef8a7a0b5196590458/wasm/jsapi/js-string/basic.any.js#L1

And given none of Chrome, Edge, Firefox, or Safari support jsshell tests, this test gets skipped. The other global scopes that this test includes are run against these browsers, as they do support them.