841803 - Mozmill tests branch migration for Firefox 19

Status: RESOLVED FIXED

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Description

[u279076]

This is a tracking bug to migrate the mozmill-tests branches in preparation for the release of Firefox 19.

Comment 1

[u279076]

Merge mozilla-beta to mozilla-release for Firefox 19.0
------------------------------------------------------
http://hg.mozilla.org/qa/mozmill-tests/rev/eb67de286956 RELEASE_BASE_20130215
http://hg.mozilla.org/qa/mozmill-tests/rev/9862e805ef65 Merge beta->release
http://hg.mozilla.org/qa/mozmill-tests/rev/744854b1b90f FIREFOX_RELEASE_19.0

Comment 2

[u279076]

Next up, aurora->beta and default->aurora will occur on Tuesday after release. Note that this normally happens on Monday before release but it is being delayed by one day since this coincides with a holiday Monday in the US.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

This merge for beta->release happened too late! We already got builds for testing before those changes have been landed in our mozmill-tests repository. 

So please make sure to do the merge before the 'go to build' email goes out to release drivers. If you can't make that time please inform Dave or myself so we can cover that. Thanks.

Comment 4

[u279076]

(In reply to Henrik Skupin (:whimboo) from comment #3)
> This merge for beta->release happened too late! 

I don't see how that's possible. 

Here is the timeline of events (times GMT-5):
> February 14, 2013 06:43 AM: Lukas Blakk tagged RELEASE_BASE_20130214
> February 15, 2013 10:17 AM: I did the Mozmill Tests beta->release merge 
> February 15, 2013 10:54 AM: Alex Keybl tagged FIREFOX_19_0_BUILD1
> February 15, 2013 11:53 AM: Alex Keybl sent the go-to-build
> February 15, 2013 02:37 PM: Mac OSX builds available
> February 15, 2013 02:55 PM: Linux builds available
> February 15, 2013 04:52 PM: Windows builds available
As you can see I did the merge 4h20m before the first builds became available.

Henrik, please verify all the facts and raise your concerns privately before making public accusations in the future.

Thank you.

Comment 5

[u279076]

Merge mozilla-aurora to mozilla-beta for Firefox 20.0
-----------------------------------------------------
http://hg.mozilla.org/qa/mozmill-tests/rev/327eaf742a61 BETA_BASE_20130219
http://hg.mozilla.org/qa/mozmill-tests/rev/b48b674e53f6 Merge aurora->beta
http://hg.mozilla.org/qa/mozmill-tests/rev/d6b7357d1c13 FIREFOX_BETA_20.0

Comment 6

[u279076]

Merge default to mozilla-aurora for Firefox 21.0
------------------------------------------------
http://hg.mozilla.org/qa/mozmill-tests/rev/2078facc8d93 AURORA_BASE_20130219
http://hg.mozilla.org/qa/mozmill-tests/rev/8b4c71a0d87c Merge default->aurora
http://hg.mozilla.org/qa/mozmill-tests/rev/2f34eda4c5fa FIREFOX_AURORA_21.0

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #4)
> Here is the timeline of events (times GMT-5):

Those times should be GMT-8 given your merge at 'Fri Feb 15 10:13:53 2013 -0800'

> > February 14, 2013 06:43 AM: Lukas Blakk tagged RELEASE_BASE_20130214
> > February 15, 2013 10:17 AM: I did the Mozmill Tests beta->release merge 
> > February 15, 2013 10:54 AM: Alex Keybl tagged FIREFOX_19_0_BUILD1
> > February 15, 2013 11:53 AM: Alex Keybl sent the go-to-build
> > February 15, 2013 02:37 PM: Mac OSX builds available
> > February 15, 2013 02:55 PM: Linux builds available
> > February 15, 2013 04:52 PM: Windows builds available
> As you can see I did the merge 4h20m before the first builds became
> available.

So sorry that I haven't seen the discrepancy in the time earlier. But looking at those times and comparing updates for mozmill-tests in our CI system shows me that there hasn't been triggered a mozmill-tests job manually. The jobs running on Feb 15th didn't include the merge push. The next update is from today.

As we have discussed in one of the last similar merge bugs you will have to trigger those jobs manually until the bug in a dependent Jenkins plugin has been fixed. Only updates to the default branch will trigger the job to automatically run. :/