This bug tracks migration of mozmill-tests branches for releasing Firefox 23.

mozilla-beta -> mozilla-release ------------------------------- https://hg.mozilla.org/qa/mozmill-tests/rev/4823dfb30abd RELEASE_BASE_20130730 https://hg.mozilla.org/qa/mozmill-tests/rev/cb11da114e7e Merge mozilla-beta -> mozilla-release https://hg.mozilla.org/qa/mozmill-tests/rev/6093fd4abac6 FIREFOX_RELEASE_23.0

Looks like I might have missed something: http://mozmill-release.blargon7.com/#/functional/report/b3aefd29a5c41bda1cc43616d3b7e54d Strange how this passed locally. Can someone on the AutoDev team look into this for me?

Dave, can you please look into comment 2? I'm not sure what went wrong and I don't want to make it more broken trying to fix it myself.

Andreea, maybe you can help out since Dave's on PTO?

The test has been removed in bug 861520 due to the changes in the UI there. I'll prepare a patch for it and delete it in release also. We've removed it in nightly only and it merged fine until now, not sure why it failed this time.

mozilla-aurora -> mozilla-beta ------------------------------ https://hg.mozilla.org/qa/mozmill-tests/rev/54579340ad3d BETA_BASE_20130805 https://hg.mozilla.org/qa/mozmill-tests/rev/eed4d1de6f98 Merge mozilla-aurora to mozilla-beta for Firefox 24.0 https://hg.mozilla.org/qa/mozmill-tests/rev/eaee8a5ea36e FIREFOX_BETA_24.0

default -> mozilla-aurora ------------------------- https://hg.mozilla.org/qa/mozmill-tests/rev/1a29e244154f AURORA_BASE_20130805 https://hg.mozilla.org/qa/mozmill-tests/rev/393c4491bb95 Merge default to mozilla-aurora for Firefox 25.0 https://hg.mozilla.org/qa/mozmill-tests/rev/93b0d42ca50f FIREFOX_AURORA_25.0

(In reply to Anthony Hughes, Mozilla QA (:ashughes) from comment #2) > Looks like I might have missed something: > http://mozmill-release.blargon7.com/#/functional/report/ > b3aefd29a5c41bda1cc43616d3b7e54d > > Strange how this passed locally. Can someone on the AutoDev team look into > this for me? It's not the first time that happened. We had it at least twice in the past. For both of the occurrences I mentioned to add the step to the release documentation for QA. So as what you all have figured out was that the get_mozmill-tests job in mozmill-ci has to be triggered manually.