1147586 - B2G mochitest-chrome not available on try with -u mochitest-chrome, but available with -u all

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Jonathan Griffin (:jgriffin)]

For some reason, B2G emulator mochitest-chrome tests do not get run on a try job with -u mochitest-chrome (e.g., https://treeherder.mozilla.org/#/jobs?repo=try&revision=96f10b54ba5e) but do get run when -u all is specified (e.g., https://treeherder.mozilla.org/#/jobs?repo=try&revision=bf62d64d58ff)

I haven't been able to discover why this is.

Comment 1

[Jonathan Griffin (:jgriffin)]

Jordan, any ideas here?

Comment 2

[Jordan Lund (:jlund)]

hmm, I'm not too familiar with trychooser and the syntax interpretation. however, I dug around and found this:

http://mxr.mozilla.org/build/source/buildbotcustom/try_parser.py?rev=df52461b1501#22

which led me to: https://bugzil.la/1011700

my best guess is that we once had synonyms for everything under mochitest-other and this is getting swallowed in the commit message, rewriting it to mochitest-o, and I bet emulator (b2g) builds don't have a mochitest-o (other) job to run so no tests are run.

If I'm right, I'd say it's pretty safe to just remove the synonyms and ask devs to rely on explicitly saying mochitest-o if they want other. Especially now that we are taking parts out of other.

Comment 3

[Jonathan Griffin (:jgriffin)]

Great spelunking, thanks.  I'll do what you suggest.

Comment 4

[Jonathan Griffin (:jgriffin)]

Attachment: Remove mochitest-chrome alias,

Thanks.  It looks like this is literally the only line that needs to change.

I looked at the last 2 weeks of try pushes, and no one has used this alias.  I'll make a post to dev.platform when this lands, as well.

Comment 5

[Jonathan Griffin (:jgriffin)]

https://hg.mozilla.org/build/buildbotcustom/rev/17e4004c89fd

I'll follow up with a post to dev.platform.

Comment 6

[Release Engineering SlaveAPI Service]

In production: https://hg.mozilla.org/build/buildbotcustom/rev/17e4004c89fd