1296913 - try server schedules unrequested spidermonkey jobs on my push

Status: RESOLVED WORKSFORME

(Release Engineering :: General, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

I pushed https://treeherder.mozilla.org/#/jobs?repo=try&revision=22da75fc4238&selectedJob=26086861 with the commit message

> Bug 1292628. Make sure our surface is good before locking it. r=mstange try: -b o -p win32 -u reftest[Windows XP] -t none[Windows XP]

There is another line in the commit message:
> This should fix a crash in ssse3_fetch_bilinear_cover.

I expected a Windows XP opt build + R(R) as test.

The Try server also scheduled the Spidermonkey cgc and p builds. There are separate checkboxes for theses under "Platforms" at http://trychooser.pub.build.mozilla.org/ and I didn't check them.

Comment 1

[Phil Ringnalda (:philor)]

Dupe of some really really old bug that talks about something like "infer the qbase of a try push" - you only intended to push Jeff's patch, but because nobody had pushed to try with an m-i base since you had pushed https://hg.mozilla.org/try/rev/c53525b828f7 to m-i, what you actually pushed to try was a bunch of things including csets which touched js/src/, which is what triggers SpiderMonkey builds, because the SpiderMonkey team doesn't care whether or not you want to run them, if you touch their src they want you running them no matter what.

Comment 2

[Aki Sasaki (not active)]

We've moved to ./mach try fuzzy and in-tree configs since this bug was filed.