650881 - port tegra unit tests to mozharness

Status: RESOLVED WONTFIX

(Release Engineering :: Applications: MozharnessCore, defect, P4)

Description

[Aki Sasaki (not active)]

This should get complexity out of buildbotcustom and allow the a-team,
developers, and releng to all use the same scripts.

The dependency on bug 650880 isn't a hard dependency.

Comment 1

[Aki Sasaki (not active)]

wesj just pinged me about how to run Tegra browser-chrome tests on his phone.
Answer: it's tricky.

I'd love to be able to say, clone mozharness, possibly edit a config file, and run this commandline.  There would also need to be steps to install SUT and friends, but that would hopefully be a known and limited scope list of items in a document.

This is opposed to the known and limited scope list of items, plus a bunch of fiddly steps that you may or may not be able to intuit from the buildbot logs and sut_tools scripts which aren't designed to be run outside of a controlled foopy environment.

Comment 2

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Found in triage.

Comment 3

[Justin Wood (:Callek)]

This is done for pandas, todo is for tegras.

Comment 4

[(not currently active) Ted Mielczarek]

Tegras are EOL, right? Is this WORKSFORME or FIXED now?

Comment 5

[Justin Wood (:Callek)]

more likely wontfix --- pandas were ported to mozharness in a different bug.

That said the tegras are not EOL yet, but they are on an EOL track. to the extent that we want to avoid divesting effort into them.

Comment 6

[Kim Moir [:kmoir] ET]

I think this should be closed wontfix. This was discussed even before we had an eol date for Tegras and we decided that we didn't want to invest the effort in it.