648918 - Please retrigger a Maemo build (and the tests it should trigger) on http://hg.mozilla.org/mozilla-central/rev/352ebc13e546

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Phil Ringnalda (:philor)]

Because we can't tell whether or not the way all tests on the Mobile tree are broken is the result of a code change or broken infrastructure, we need a retriggered Maemo build (because Android was broken on that rev) and tests for http://hg.mozilla.org/mozilla-central/rev/352ebc13e546, the last cset that had non-orange tests. Self-serve, if it was working (bug 648783) wouldn't do the trick, since it's (bug 648916) retriggering on the tip rev instead of the intended rev, so I'm hoping whatever script you use to manually retrigger is able to be persuasive about which mozilla-central rev to use in the new mobile-merged-in world.

Comment 1

[Nick Thomas [:nthomas] (UTC+12)]

Triggered a build of Maemo 5 GTK mozilla-central build on m-c rev 352ebc13e546.

Comment 2

[Nick Thomas [:nthomas] (UTC+12)]

Bah, it did 'hg up -C' and completely ignore the revision I set on the request.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

Aki, the only way I can see to do this is to hardcode mozilla_revision somewhere in config.py, so as to pass it in to mozRevision on the MaemoBuildFactory. Hoping you can thing of something nicer than that.

Comment 4

[Aki Sasaki (not active)]

Sadly, that's all there is atm.
Now that we're on a single repo, we should probably look at the Mercurial build step and/or check if there's a revision property.

Comment 5

[John Ford [:jhford] CET/CEST Berlin Time]

(In reply to comment #4)
> Sadly, that's all there is atm.
> Now that we're on a single repo, we should probably look at the Mercurial build
> step and/or check if there's a revision property.

I also have a patch somewhere to allow us to use MercurialBuildFactory to do our mobile builds.  In a merged repo world, that might be advantageous to use.

Comment 6

[Phil Ringnalda (:philor)]

The problem for which I wanted this particular retrigger is solved, so feel free to either morph this into a "can't retrigger on a rev" or dupe it to an existing one.

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

(In reply to comment #6)
> The problem for which I wanted this particular retrigger is solved, so feel
> free to either morph this into a "can't retrigger on a rev" or dupe it to an
> existing one.

Maybe bug 648916?

Comment 8

[Phil Ringnalda (:philor)]

Nice, 22 hours to completely forget that I had filed something. DIDNTFIX for this, then.