When xpcshell moves to mozlog.structured, we'll need mozlog on any machine running xpcshell tests. I can see from try that it's missing at least for Android 2.2 Armv6 Opt.

This should probably be installed into the virtualenv the tests run with. jgriffin, do you have a preferred place to add this requirement ?

fwiw this [android 2.2 .*] is not-mozharness xpcshell tests, and possibly should be addressed with the Mobile Testing meeting kim is attending tomorrow, to find out relative priority and if this issue can be solved on the harness side rather than the releng side. n-i to kim to bring up at tomorrow's meeting

For non-mozharness tests, we can probably use our old hack of copying files around to make them appear in the right places in tests.zip. I'd love to get all the tests in mozharness, though...we'll need that to make use of structured logs.

We are planning to disable Tegras soon on 32 and ride the trains so I don't know how relevant this is. See bug 1033507

(In reply to Jonathan Griffin (:jgriffin) from comment #3) > For non-mozharness tests, we can probably use our old hack of copying files > around to make them appear in the right places in tests.zip. > > I'd love to get all the tests in mozharness, though...we'll need that to > make use of structured logs. I've been working on this by copying files into tests.zip, but it looks like the situation has changed a bit (the android tests run by try appear to use mozharness). Should I keep copying over mozlog and resolve this bug?

(In reply to Chris Manchester [:chmanchester] from comment #5) > (In reply to Jonathan Griffin (:jgriffin) from comment #3) > > For non-mozharness tests, we can probably use our old hack of copying files > > around to make them appear in the right places in tests.zip. > > > > I'd love to get all the tests in mozharness, though...we'll need that to > > make use of structured logs. > > I've been working on this by copying files into tests.zip, but it looks like > the situation has changed a bit (the android tests run by try appear to use > mozharness). Should I keep copying over mozlog and resolve this bug? If nothing else Thunderbird is not using mozharness for xpcshell at the moment.

Yes, as Called says, I believe we need to use the 'copy files' approach to avoid breaking xpcshell tests for Thunderbird. :(

Will do!