Closed Bug 1162355 Opened 9 years ago Closed 6 years ago

--tag for mochitest-chrome turns test job red due to other suites with no tests

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

Product:
Release Engineering
Component:
Applications: MozharnessCore
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: robert.strong.bugs, Unassigned)

Details

See
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/rstrong@mozilla.com-204fba6e3139/try-win32/try_xp-ix_test-mochitest-other-bm109-tests1-windows-build956.txt.gz

The --tag arg worked for me locally when running these same tests
./mach mochitest-chrome --tag appupdate

Perhaps this is due to the infra problem occurring at this time though the xpcshell tests didn't have any problems.
The mochitest-oth job runs three suites of mochitests: chrome, plugin, and a11y. Some chrome tests in toolkit/mozapps/update/tests/chrome/ did run and pass in that log, but all of the tests were filtered out of the other two suites, so mozharness turned the job red on behalf of the empty suites. I'm not sure who mochitest-oth are grouped like this in automation.
Summary: --tag for mochitest-chrome tests failed to run tests → --tag for mochitest-chrome turns test job red due to other suites with no tests
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.