All work was completed on Monday and services fully restored. If you are
experiencing any issues, please contact #vcs.
NOTE: if you use the remote git.mozilla.org/integration/gecko-dev.git
please keep reading.
If you use this particular remote, and pulled during the problem window
(roughly J
7.30 PST update:
Work is largely complete (with two exceptions, and no force pushes
required) and we are currently re-enabling automation.
We have left gecko-projects and integration/gecko-dev for now and will pick
these up in the morning.
Thank you for your patience while the team worked through
GitHub syncing has been restored. Replication on git.mozilla.org is still
recovering. But we're over the big hump (getting the two systems to agree
on SHA-1s).
On Fri, Jan 30, 2015 at 5:01 PM, Gregory Szorc wrote:
> I figured people would like an update.
>
> There were multiple, independent fai
5pm PST update:
Work is progressing smoothly. We are currently at step 8 in the detailed
plan posted earlier. That is, all commits have been manually processed and
the head of both systems matches.
We'll send an update when work is complete, or at 9am PST, whichever is
sooner.
Best,
Laura
On S
Here is an update on our plans and status.
= Overview =
gps and hwine will implement the plan, which is, in summary, manually
playing back the problematic merges one by one to ensure both systems are
in agreement.
gps has point and hwine is online for peer review of the work.
No further tree clo
I figured people would like an update.
There were multiple, independent failures in the replication systems (there
are 2 systems that replicate Mercurial to Git).
At least one system wasn't DAG aware. It was effectively using the "tip"
commit of the Mercurial repositories (the most recently commi
On Fri, Jan 30, 2015 at 2:24 PM, Gregory Szorc wrote:
> On Fri, Jan 30, 2015 at 3:38 AM, Wander Lairson Costa
> wrote:
>>
>> On Thu, Jan 29, 2015 at 8:48 PM, Mike Hommey wrote:
>> > On Thu, Jan 29, 2015 at 12:31:35PM -0800, Gregory Szorc wrote:
>> >> The steps within my control to potentially fi
On Fri, Jan 30, 2015 at 2:08 AM, Tim Guan-tin Chien
wrote:
> Any support for Level 1 people for creating a patch-to-commit for
> attaching on Bugzilla?
> I tried :jlebar's moz-git-tools once but the exported patch was broken for
> hg.
>
The easiest way to attach a git patch to bugzilla is with
On Fri, Jan 30, 2015 at 3:38 AM, Wander Lairson Costa
wrote:
> On Thu, Jan 29, 2015 at 8:48 PM, Mike Hommey wrote:
> > On Thu, Jan 29, 2015 at 12:31:35PM -0800, Gregory Szorc wrote:
> >> The steps within my control to potentially fix this issue have been
> >> postponed until at least tomorrow du
On Friday, January 30, 2015 at 5:30:52 AM UTC-5, 陳侃如 Kan-Ru Chen wrote:
>
> I use this alias in ~/.gitconfig
>
> [alias]
> hg-format-patch = !sh -c 'git format-patch -kp -U8 "$@"|tee
> /dev/stderr|xargs git-patch-to-hg-patch' git
>
> Get git-patch-to-hg-patch from https://github.com/mozil
On Thu, Jan 29, 2015 at 01:28:48PM -0800, Eric Rescorla wrote:
> Thanks. Hopefully all will be back to normal soon.
Alternatively you can use the git-remote-hg glandium wrote and let
Alternatively you can take the excuse and switch to using the
git-remote-hg glandium wrote for everything and let m
On Thu, Jan 29, 2015 at 8:48 PM, Mike Hommey wrote:
> On Thu, Jan 29, 2015 at 12:31:35PM -0800, Gregory Szorc wrote:
>> The steps within my control to potentially fix this issue have been
>> postponed until at least tomorrow due to the Firefox Beta build today.
>> tl;dr is people don't want to tak
Tim Guan-tin Chien writes:
> On Fri, Jan 30, 2015 at 6:48 AM, Mike Hommey wrote:
>>
>> People using Git for Gecko development can also try a new workflow that
>> doesn't involve gecko-dev at all.
>>
>> http://glandium.org/blog/?page_id=3438
>>
>> Mike
>
> This sure look promising!
>
> Any suppor
On Fri, Jan 30, 2015 at 6:48 AM, Mike Hommey wrote:
>
> People using Git for Gecko development can also try a new workflow that
> doesn't involve gecko-dev at all.
>
> http://glandium.org/blog/?page_id=3438
>
> Mike
This sure look promising!
Any support for Level 1 people for creating a patch-to
On Thu, Jan 29, 2015 at 12:31:35PM -0800, Gregory Szorc wrote:
> The steps within my control to potentially fix this issue have been
> postponed until at least tomorrow due to the Firefox Beta build today.
> tl;dr is people don't want to take on additional risk changing repositories.
>
> I hate to
Thanks. Hopefully all will be back to normal soon.
Best,
-Ekr
On Thu, Jan 29, 2015 at 1:27 PM, Gregory Szorc wrote:
> On Thu, Jan 29, 2015 at 1:07 PM, Eric Rescorla wrote:
>
>> On Thu, Jan 29, 2015 at 12:31 PM, Gregory Szorc wrote:
>>
>>> The steps within my control to potentially fix this i
On Thu, Jan 29, 2015 at 1:07 PM, Eric Rescorla wrote:
> On Thu, Jan 29, 2015 at 12:31 PM, Gregory Szorc wrote:
>
>> The steps within my control to potentially fix this issue have been
>> postponed until at least tomorrow due to the Firefox Beta build today.
>> tl;dr is people don't want to take
On Thu, Jan 29, 2015 at 12:31 PM, Gregory Szorc wrote:
> The steps within my control to potentially fix this issue have been
> postponed until at least tomorrow due to the Firefox Beta build today.
> tl;dr is people don't want to take on additional risk changing
> repositories.
>
> I hate to say
The steps within my control to potentially fix this issue have been
postponed until at least tomorrow due to the Firefox Beta build today.
tl;dr is people don't want to take on additional risk changing repositories.
I hate to say this, but people using Git for Gecko development will have to
wait a
19 matches
Mail list logo
