+++ This bug was initially created as a clone of Bug #1480479 +++ Filing this in advance to start chaining deps for release-ing 63.0

* Bug 1489405 should be done before second day mergeduty on the 22nd October. * Unclear to me if bug 1415233 is still a problem during mergeduty.

* Adding bug 1480476 as direct dep just to make sure we no longer have anything BB during this cycle

bug 1415233 is still an issue

With regard to bug 1415233, we have deployed a fix that appears to have remedied the issue. I'd like to attempt the next push without disabling replication. As a safety net, please NI/ping me in #vcs beforehand so I can be around to turn it off if the problem persists.

(In reply to Connor Sheehan [:sheehan] from comment #4) > With regard to bug 1415233, we have deployed a fix that appears to have > remedied the issue. I'd like to attempt the next push without disabling > replication. As a safety net, please NI/ping me in #vcs beforehand so I can > be around to turn it off if the problem persists. Thanks for taking care of this, will ping beforehand if needed.

I brought up the merge day instance [1][2] and did the fx63 dry run [3]. This is the diff. [1] https://github.com/mozilla-releng/releasewarrior-2.0/blob/master/docs/mergeduty/howto.md#merge-remote-instance [2] https://github.com/mozilla-releng/releasewarrior-2.0/blob/master/docs/mergeduty/howto.md#connect-to-remote-instance-and-get-a-copy-of-mozharness [3] https://github.com/mozilla-releng/releasewarrior-2.0/blob/master/docs/mergeduty/howto.md#mozilla-beta-mozilla-release-migration-no-op-trial-run

:sheehan, merge day will be this coming Monday, starting in European hours. It currently looks like things should Just Work. If we hit issues, the merge push may be delayed until North American hours if we need time to debug.

:aki, I will be on PTO for all of next week. gps says he can be online in EU hours in case something comes up.

we think beta to release worked fine. Issues: 1. push hanged for ~50mins until Simon killed the script. The pushes seemed to have worked though so we don't know what the issue is exactly logs say: 03:19:07 INFO - Running command: ['hg', 'push', '--new-branch', '-r', '.'] in /home/buildduty/merge_day_63/build/mozilla-release 03:19:07 INFO - Copy/paste: hg push --new-branch -r . 2. These two commits weren't exactly expected on mozilla-release https://hg.mozilla.org/releases/mozilla-release/rev/32928de80b1b https://hg.mozilla.org/releases/mozilla-release/rev/bb69fd13467d 3. Decision task[1] of resulting mozilla-release failed in the first place. Rerunning seems to have worked, still waiting for results. [1]: https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&selectedJob=205512697&revision=18d4c09e9378f1fca26c074a10195589248c88c0

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #9) > 3. Decision task[1] of resulting mozilla-release failed in the first place. > Rerunning seems to have worked, still waiting for results. > > [1]: > https://treeherder.mozilla.org/#/jobs?repo=mozilla- > release&selectedJob=205512697&revision=18d4c09e9378f1fca26c074a10195589248c88 > c0 https://bugzilla.mozilla.org/show_bug.cgi?id=1490119#c19 anticipated this but we forgot to uplift sooner. We grafted the patch to mozilla-release, let's see how this goes.

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #10) > (In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #9) > > 3. Decision task[1] of resulting mozilla-release failed in the first place. > > Rerunning seems to have worked, still waiting for results. > > > > [1]: > > https://treeherder.mozilla.org/#/jobs?repo=mozilla- > > release&selectedJob=205512697&revision=18d4c09e9378f1fca26c074a10195589248c88 > > c0 > > https://bugzilla.mozilla.org/show_bug.cgi?id=1490119#c19 anticipated this > but we forgot to uplift sooner. We grafted the patch to mozilla-release, > let's see how this goes. https://hg.mozilla.org/releases/mozilla-release/rev/5ccec2d040a6