On Tuesday, June 3, 2014 1:57:14 PM UTC+2, Dale Harvey wrote: > +1 @ root cause analysis > > > I assumed this was the cause of the error, I started seeing it at the same > time, but does anyone know what is up with > https://bugzilla.mozilla.org/show_bug.cgi?id=1019552 ? I flashed master today > and the homescreen is fixed for me, but this still shows up > > > > > > On 3 June 2014 04:30, Faramarz Rashed <[email protected]> wrote: > > Hi Clint, > > Is this something you can help us with? How can we help make sure we have > solid CI tests around this? > > > > Faramarz > > > > > > On Jun 2, 2014, at 6:57 PM, Kyle Huey <[email protected]> wrote: > > > > > On Mon, Jun 2, 2014 at 6:47 PM, Faramarz Rashed <[email protected]> wrote: > > >> ehsan, > > >> how was this tested before landing and why did this break the trunk? > > >> > > >> faramarz > > >> > > >> On Jun 2, 2014, at 7:24 AM, Ehsan Akhgari <[email protected]> wrote: > > >> > > >> I just backed out bug 957086. Andrea has verified that bug was the cause. > > >> > > >> -- > > >> Ehsan > > >> <http://ehsanakhgari.org/> > > >> > > >> > > >> On Mon, Jun 2, 2014 at 9:46 AM, Ben Hearsum <[email protected]> wrote: > > >>> > > >>> I locked our mozilla-central/master nightlies at one of the May 30th > > >>> builds until this is resolved. > > >>> > > >>> On 14-06-02 09:22 AM, Dale Harvey wrote: > > >>>> Is that the correct bug? its resolved for 3 days now > > >>>> > > >>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1018956 has also been filed > > >>>> and duped against https://bugzilla.mozilla.org/show_bug.cgi?id=1018909, > > >>>> anyone know what the root cause is for this and fill us in? > > >>>> > > >>>> Thanks > > >>>> Dale > > >>>> > > >>>> > > >>>> On 2 June 2014 02:27, Kevin Grandon <[email protected]> wrote: > > >>>> > > >>>>> Just wanted to send a note to let you know that current trunk is > > >>>>> broken, > > >>>>> so maybe avoid updating gecko for a little bit. I've been pinged a few > > >>>>> times offline and didn't see an update, so thought it'd make sense to > > >>>>> notify everyone. > > >>>>> > > >>>>> A fix is in the works and is being tracked in bug 957086. > > >>>>> > > >>>>> Best, > > >>>>> Kevin > > >>>>> _______________________________________________ > > >>>>> dev-gaia mailing list > > >>>>> [email protected] > > >>>>> https://lists.mozilla.org/listinfo/dev-gaia > > >>>>> > > >>>> > > >>> > > >>> _______________________________________________ > > >>> dev-b2g mailing list > > >>> [email protected] > > >>> https://lists.mozilla.org/listinfo/dev-b2g > > >> > > >> > > >> _______________________________________________ > > >> dev-b2g mailing list > > >> [email protected] > > >> https://lists.mozilla.org/listinfo/dev-b2g > > >> > > >> > > >> > > >> _______________________________________________ > > >> dev-b2g mailing list > > >> [email protected] > > >> https://lists.mozilla.org/listinfo/dev-b2g > > > > > > It was tested on our CI infrastructure for three full days. It's > > > pretty alarming that we don't have any testing that can catch > > > something as bad as "the device is completely unusable". > > > > > > - Kyle > > > > _______________________________________________ > > dev-b2g mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-b2g
I used to get those with --disable-ril option in gecko-defaultconfig. But I think that was fixed around V1.4. Perhaps this is a similar problem? _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
