1840538 - ./mach try fuzzy [path/to/reftest] fails on Android, with "Could not find manifest [full/path/to/reftest]"

Status: NEW

(Developer Infrastructure :: Try, defect)

Description

[Daniel Holbert [:dholbert]]

STR:

1. Run ./mach try fuzzy <path-to-some-reftest>
   (in my case the path was layout/reftests/bugs/1840511-1.html which was a test I was adding locally in a commit; I suspect this repro's for any arbitrary reftest, though)
2. Accept all the suggested tasks. (Ctrl+A, and then Enter)
3. Look at your Android reftest results.

ACTUAL RESULTS:
The Android reftest tasks immediately die with the following error:

INFO -  Could not find manifest /builds/worker/workspace/build/tests/reftest/layout/reftests/bugs/1840511-1.html
[taskcluster:error] Task timeout after 3600 seconds. Force killing container.

Here's my Try run where I ran into this:
https://treeherder.mozilla.org/jobs?repo=try&revision=6f426ea236f244dc9dff9edecd73d478a37abfbf

Sample Android log showing this issue:
https://treeherder.mozilla.org/logviewer?job_id=420732081&repo=try&lineNumber=1840

EXPECTED RESULTS:
Successful test run. We shouldn't be treating the test name as a reftest manifest.

Comment 1

[Daniel Holbert [:dholbert]]

I hit this when I run ./mach try fuzzy with a reftest directory, too (instead of a single reftest). Like so:
./mach try fuzzy layout/reftests/bugs

This hit the same issue where the test runner seems to be expecting the provided path to be a manifest file:

INFO -  Could not find manifest /builds/worker/workspace/build/tests/reftest/layout/reftests/bugs
[taskcluster:error] Task timeout after 3600 seconds. Force killing container.

https://treeherder.mozilla.org/logviewer?job_id=420996678&repo=try&lineNumber=1838-1840

Comment 2

[Marco Castelluccio [:marco]]

Was this working before?