1014912 - Add "emulator" option under "Restrict tests to platform(s)" on TryChooser

Status: RESOLVED DUPLICATE of bug 1039771

(Release Engineering :: General, defect)

Description

[Botond Ballo [:botond]]

TryChooser (http://trychooser.pub.build.mozilla.org/) has a "Restrict tests to platform(s)" section, but it does not list all platforms - for example it does not list "emulator".

The absence of "emulator" from that lists is unfortunate because a common test configuration for APZ development is to build on all platforms and test on B2G emulator only. Currently I need to do two separate try pushes to accomplish this (build + tests for emulator, and build only for everything else).

Comment 1

[Ed Morley [:emorley]]

If you manually set [b2g_emulator_vm] (or [b2g_emulator]) in a similar manner to how the other test platform names are formed, does it work? If so, I can easily add an entry to trychooser, if not, it will presumably require changes to https://hg.mozilla.org/build/buildbotcustom/file/tip/try_parser.py - which I'm less familiar with.

Comment 2

[Botond Ballo [:botond]]

(In reply to Ed Morley [:edmorley UTC+0] from comment #1)
> If you manually set [b2g_emulator_vm] (or [b2g_emulator]) in a similar
> manner to how the other test platform names are formed, does it work? If so,
> I can easily add an entry to trychooser, if not, it will presumably require
> changes to
> https://hg.mozilla.org/build/buildbotcustom/file/tip/try_parser.py - which
> I'm less familiar with.

I will try this next time I Try.

Out of curiosity, where did you get the strings "b2g_emulator_vm" and "b2g_emulator" from?

Comment 3

[Botond Ballo [:botond]]

(In reply to Botond Ballo [:botond] from comment #2)
> (In reply to Ed Morley [:edmorley UTC+0] from comment #1)
> > If you manually set [b2g_emulator_vm] (or [b2g_emulator]) in a similar
> > manner to how the other test platform names are formed, does it work? If so,
> > I can easily add an entry to trychooser, if not, it will presumably require
> > changes to
> > https://hg.mozilla.org/build/buildbotcustom/file/tip/try_parser.py - which
> > I'm less familiar with.
> 
> I will try this next time I Try.

I did a try push with the syntax "try: -b o -p all -u all[b2g_emulator] -t none": https://tbpl.mozilla.org/?tree=Try&rev=4ec7d365b86c

It seems to be running Linux tests, so I guess it doesn't work?

Comment 4

[Botond Ballo [:botond]]

(In reply to Botond Ballo [:botond] from comment #3)
> (In reply to Botond Ballo [:botond] from comment #2)
> > (In reply to Ed Morley [:edmorley UTC+0] from comment #1)
> > > If you manually set [b2g_emulator_vm] (or [b2g_emulator]) in a similar
> > > manner to how the other test platform names are formed, does it work? If so,
> > > I can easily add an entry to trychooser, if not, it will presumably require
> > > changes to
> > > https://hg.mozilla.org/build/buildbotcustom/file/tip/try_parser.py - which
> > > I'm less familiar with.
> > 
> > I will try this next time I Try.
> 
> I did a try push with the syntax "try: -b o -p all -u all[b2g_emulator] -t
> none": https://tbpl.mozilla.org/?tree=Try&rev=4ec7d365b86c
> 
> It seems to be running Linux tests, so I guess it doesn't work?

Oh, that's not actually Linux tests, it's just the Valgrind and Static Rooting Hazard Analysis that come with a Linux build.

I don't see any B2G tests queued up either, though, so it's still not doing what we want.

Comment 5

[Botond Ballo [:botond]]

(In reply to Botond Ballo [:botond] from comment #4)
> I don't see any B2G tests queued up either, though, so it's still not doing
> what we want.

Never mind, I see them now. Guess it's working after all!

Comment 6

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)]

I also need "android". When I want to try all mochitests on all platforms but it's enough to run on one environment per OS, I need to run all tests without restriction now.

Comment 7

[Botond Ballo [:botond]]

(In reply to Masayuki Nakano (:masayuki) (Mozilla Japan) from comment #6)
> I also need "android". When I want to try all mochitests on all platforms
> but it's enough to run on one environment per OS, I need to run all tests
> without restriction now.

"Android" with a capital "A" seems to work. ("android" does not.)

Comment 8

[Ed Morley [:emorley]]

Bug 1039771 will fix this and the Android case :-)