Filed by: apavel [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=283379529&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/cMUMUSl5RROxsj815MVzGg/runs/0/artifacts/public/logs/live_backing.log

[task 2020-01-03T19:56:33.226Z] 19:56:33 INFO - Calling ['C:\tasks\task_1578067056\build\venv\Scripts\python', '-u', 'C:\tasks\task_1578067056\build\tests\mochitest\runtests.py', u'remote/test/browser/browser.ini', u'remote/test/browser/emulation/browser.ini', u'remote/test/browser/input/browser.ini', u'remote/test/browser/io/browser.ini', u'remote/test/browser/network/browser.ini', u'remote/test/browser/page/browser.ini', u'remote/test/browser/runtime/browser.ini', u'remote/test/browser/security/browser.ini', u'remote/test/browser/target/browser.ini', '--setpref=media.peerconnection.mtransport_process=false', '--setpref=network.process.enabled=false', '--appname=C:\tasks\task_1578067056\build\application\firefox\firefox.exe', '--utility-path=tests/bin', '--extra-profile-file=tests/bin/plugins', u'--symbols-path=https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/QVUWL7r9To6srktufDBqDg/artifacts/public/build/target.crashreporter-symbols.zip', '--certificate-path=tests/certs', '--quiet', '--log-raw=C:\tasks\task_1578067056\build\blobber_upload_dir\mochitest-remote_raw.log', '--log-errorsummary=C:\tasks\task_1578067056\build\blobber_upload_dir\mochitest-remote_errorsummary.log', '--screenshot-on-fail', '--cleanup-crashes', '--marionette-startup-timeout=180', '--log-raw=-', '--flavor=browser', '--subsuite=remote'] with output_timeout 1000
[task 2020-01-03T19:56:34.352Z] 19:56:34 INFO - Checking for ssltunnel processes...
[task 2020-01-03T19:56:35.176Z] 19:56:35 INFO - Checking for xpcshell processes...
[task 2020-01-03T19:56:35.563Z] 19:56:35 INFO - mozcrash Removed pending crash reports at 'C:\Users\testdroid.YOGA-001.000\AppData\Roaming\Mozilla\Firefox\Crash Reports'
[task 2020-01-03T19:56:36.317Z] 19:56:36 ERROR - No tests were found for flavor 'browser' and the following manifest filters:
[task 2020-01-03T19:56:36.318Z] 19:56:36 ERROR - skip_if, run_if, fail_if, subsuite(name=remote), pathprefix(['remote/test/browser/browser.ini', 'remote/test/browser/emulation/browser.ini', 'remote/test/browser/input/browser.ini', 'remote/test/browser/io/browser.ini', 'remote/test/browser/network/browser.ini', 'remote/test/browser/page/browser.ini', 'remote/test/browser/runtime/browser.ini', 'remote/test/browser/security/browser.ini', 'remote/test/browser/target/browser.ini'])
[task 2020-01-03T19:56:36.318Z] 19:56:36 ERROR -
[task 2020-01-03T19:56:36.318Z] 19:56:36 ERROR - Make sure the test paths (if any) are spelt correctly and the corresponding
[task 2020-01-03T19:56:36.318Z] 19:56:36 ERROR - --flavor and --subsuite are being used. See mach mochitest --help for a
[task 2020-01-03T19:56:36.318Z] 19:56:36 ERROR - list of valid flavors.
[task 2020-01-03T19:56:36.319Z] 19:56:36 ERROR -
[task 2020-01-03T19:56:36.321Z] 19:56:36 INFO - SUITE-START | Running 0 tests
[task 2020-01-03T19:56:36.323Z] 19:56:36 INFO - TEST-INFO | checking window state
[task 2020-01-03T19:56:36.324Z] 19:56:36 INFO - Browser Chrome Test Summary
[task 2020-01-03T19:56:36.326Z] 19:56:36 INFO - Passed: 0
[task 2020-01-03T19:56:36.326Z] 19:56:36 INFO - Failed: 0
[task 2020-01-03T19:56:36.326Z] 19:56:36 INFO - Todo: 0
[task 2020-01-03T19:56:36.327Z] 19:56:36 INFO - Mode: e10s
[task 2020-01-03T19:56:36.327Z] 19:56:36 INFO - *** End BrowserChrome Test Results ***
[task 2020-01-03T19:56:36.327Z] 19:56:36 INFO - Buffered messages finished
[task 2020-01-03T19:56:36.327Z] 19:56:36 INFO - SUITE-END | took 0s
[task 2020-01-03T19:56:36.403Z] 19:56:36 ERROR - Return code: 1
[task 2020-01-03T19:56:36.405Z] 19:56:36 ERROR - No checks run.
[task 2020-01-03T19:56:36.406Z] 19:56:36 INFO - TinderboxPrint: mochitest-mochitest-remote<br/><em class="testfail">T-FAIL</em>
[task 2020-01-03T19:56:36.406Z] 19:56:36 ERROR - # TBPL FAILURE #
[task 2020-01-03T19:56:36.406Z] 19:56:36 WARNING - setting return code to 2
[task 2020-01-03T19:56:36.406Z] 19:56:36 ERROR - The mochitest suite: mochitest-remote ran with return status: FAILURE

Yoshi can you take a look?

Regression bug got backed out: https://hg.mozilla.org/integration/autoland/rev/c46a34b79b5dad2ca11e7d089a5c4c7a8788aaf0

This is in fact a regression from https://bugzilla.mozilla.org/show_bug.cgi?id=1603930 and it's still permafailing.
Andreas, could you please take a look at this?

It's not a crash or freeze, and as such normal severity.

With bug 1603930 we fixed a logic error where ENABLE_REMOTE_AGENT was inappropriately set on non-trunk branches and we stopped running the M(remote) job on release and beta branches.

This means that the remote agent is now correctly disabled on Windows AArch64 (due to an unrelated Rust compilation issue) and this causes the M(remote) bc test manifest to be empty on this platform on trunk.

The browser-chrome harness doesn’t like empty test manifests, so I suspect we will have to change M(remote) to not run explicitly on Windows AArch64. It would be lovely if bc either didn’t complain about empty manifests or that the TaskCluster job itself observed ENABLE_REMOTE_AGENT, but I can’t think of any way to make that work…

Andrew can you take a look at the previous comment? is this something you can help with?

I think we may be able to fix two bugs in one go here by first fixing bug 1598286. If we enable building of the remote agent on Windows AArch64 this should populate the bc test manifest and the harness should stop complaining about no tests.

If that theory doesn’t work I will resort to the fix I mentioned in comment #6 about disabling the M(remote) TaskCluster job on Windows AArch64.

There are no more failures since bug 1598286 has been fixed. No actual work has been done on this bug, and so I will remove our whiteboard tag.