Closed Bug 611092 Opened 9 years ago Closed 9 years ago

Trigger working mobile unit tests jobs on the Talos pool of slaves

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set

Tracking

(fennec2.0next+)

RESOLVED FIXED
Tracking Status
fennec 2.0next+ ---

People

(Reporter: jhford, Assigned: jhford)

References

Details

(Whiteboard: [needstaging])

Attachments

(3 files, 2 obsolete files)

Attached patch [wip] buildbotcustom v1 (obsolete) — Splinter Review
Now that we have infrastructure set up from 511282, we should start triggering these tests.

Things that need to happen in this bug include:
-sendchanges
-ensuring results end up on the correct tinderbox tree

The attached patch includes the buildbot factory changes required to get this going.
Running reliable tests on desktop will be crucial for the next Fennec release.
The current device based tests are far to unreliable. Until we get more
reliable testing infra (from hardware issues to flakey tests themselves) we'll
need the desktop-based tests. They can, and do, go green and will help catch
real issues.
tracking-fennec: --- → 2.0next+
Attachment #489583 - Attachment is obsolete: true
Attachment #489584 - Attachment is obsolete: true
Attachment #527570 - Flags: review?(aki)
Attachment #527571 - Flags: review?(aki)
Attached patch dump.diffSplinter Review
I slightly changed the logic of the sendchange stuff, this patch shows that there are no regressions
Attachment #527573 - Flags: feedback?(aki)
Comment on attachment 527570 [details] [diff] [review]
buildbot-configs v1

>diff --git a/mozilla-tests/config.py b/mozilla-tests/config.py
>--- a/mozilla-tests/config.py
>+++ b/mozilla-tests/config.py
>@@ -198,9 +198,9 @@ UNITTEST_SUITES = {
>         #                     'mochitest-ipcplugins']),
>         ('mobile-mochitest-browser-chrome', ['mobile-mochitest-browser-chrome']),
>         #('reftest', ['reftest']),
>-        ('crashtest', ['crashtest']),
>+        #('crashtest', ['crashtest']),
>         #('xpcshell', ['xpcshell']),
>-        ('jsreftest', ['jsreftest']),
>+        #('jsreftest', ['jsreftest']),
>     ],
> 
> }

I'm going to guess this is cruft?
r=me with this backed out (only r+ the mozilla/config.py changes).
Attachment #527570 - Flags: review?(aki) → review+
> I'm going to guess this is cruft?
> r=me with this backed out (only r+ the mozilla/config.py changes).

Actually, that is needed to make sure that crashtest and jsreftest don't get run.
Comment on attachment 527571 [details] [diff] [review]
buildbotcustom v1

This will get cleaner once John Ford fixes bug 557260.
Attachment #527571 - Flags: review?(aki) → review+
Comment on attachment 527570 [details] [diff] [review]
buildbot-configs v1

n/m, r+ for the whole patch.
Comment on attachment 527573 [details] [diff] [review]
dump.diff

I don't know we need these on all these branches, and talos-staging-master02 has gone away, but other than that I think this looks good.
Attachment #527573 - Flags: feedback?(aki) → feedback+
This landed last week.

http://hg.mozilla.org/build/buildbot-configs/rev/4324165089ee
http://hg.mozilla.org/build/buildbotcustom/rev/aafb13808c01
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Does anyone remember what the issues was the last time we tried this?
(In reply to comment #12)
> Does anyone remember what the issues was the last time we tried this?

sorry, wrong bug.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.