On Saturday 2013-05-11 20:46 -0400, Ehsan Akhgari wrote: > I tried backing out everything that looked suspicious on the birch side of > the merge but the leaks continued to persist. Not sure what to do next, > and I won't be around for further investigation today. The trees remain > closed for now.
I bisected the birch/mozilla-central side of the merge by merging various points along the birch/mozilla-central side of the bad merge with the merge's parent on the mozilla-inbound side of the bad merge. Based on this, I backed out https://bugzilla.mozilla.org/show_bug.cgi?id=863732 in https://hg.mozilla.org/integration/mozilla-inbound/rev/9ec0ad6f7e09 , though I don't know the bad changeset on the other half. I've reopened the trees. -David > On Sat, May 11, 2013 at 6:03 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com>wrote: > > > The latest merge from m-c to inbound resulted in all debug unit tests > > going orange. This is caused by bad interaction of things that are landed > > on birch and inbound. I've closed birch/inbound/central until this issue > > is resolved in order to prevent further damage. > > > > I've tried backing out bug 868312 from inbound, but that did not help. > > The next suspect on the list is bug 861903 landed on birch, which I'm > > trying to backout: <https://tbpl.mozilla.org/?tree=Try&rev=ccc66ba18f23>. > > If that fixes the bustage, then I will back it out from inbound and merge > > to birch. Otherwise, I'm not sure what to do. -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla http://www.mozilla.org/ 𝄂 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
