Android 'mach mochitest' times out when run on a subsuite with no active tests

RESOLVED INVALID

Status

()

Firefox for Android
Testing
P1
normal
RESOLVED INVALID
a year ago
a year ago

People

(Reporter: gbrown, Assigned: gbrown)

Tracking

49 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

a year ago
For example, testing/mochitest/tests/Harness_sanity/mochitest.ini has one test belonging to the "clipboard" sub-suite, but that test is skipped on Android.

'mach mochitest testing/mochitest/tests/Harness_sanity', when it runs clipboard tests, starts the servers, starts the browser, and then times out waiting for something to happen. (All is well if run with '--subsuite default'.)
(Assignee)

Updated

a year ago
Priority: -- → P1
(Assignee)

Comment 1

a year ago
The mochitest runtests.py has code to count the number of tests and abandon the run if there are zero tests, but those counts include disabled tests -- getActiveTests(..., disabled=True) -- which seems odd.

:ahal -- Do you know why the harness is counting disabled tests? How should we handle the case where all tests have been disabled -- start the browser and let the js side sort it out, or abandon the run earlier?

https://hg.mozilla.org/mozilla-central/file/tip/testing/mochitest/runtests.py#l779
https://hg.mozilla.org/mozilla-central/file/tip/testing/mochitest/runtests.py#l2358
Flags: needinfo?(ahalberstadt)
I think it's so we can log that those tests are skipped/disabled:
https://hg.mozilla.org/mozilla-central/file/tip/testing/mochitest/runtests.py#l1019

I think just letting the JS parts run their course make the most sense there, but I don't think it should be timing out...
Flags: needinfo?(ahalberstadt)
(Assignee)

Comment 3

a year ago
I didn't understand the problem well when I wrote the description here: It has nothing to do with the subsuite being empty.

Let's start a new bug...bug 1286697.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.