> -----Original Message----- > From: Lucas Meneghel Rodrigues [mailto:[email protected]] > Sent: Tuesday, May 29, 2012 5:30 PM > To: DeFolo, Daniel > Cc: [email protected] > Subject: Re: [Autotest] kernel install issues > > This version has a bug, which I fixed two commits later: > > commit a998776171dcb2591d20ced4db17d29f37f1add4 > Author: Lucas Meneghel Rodrigues <[email protected]> > Date: Mon May 21 19:09:07 2012 -0300 > > > > I think we also saw the same issue with the following version of autotest > installed, but I need to test 1 more time to confirm: > > > https://github.com/autotest/autotest/commit/ed05905987207e30b8ebfeb4 > d6 > > e1dcf9e63d8979 > > I've fixed these issues and even released 0.14.1 with all the fixes.
FYI, We installed 0.14.1 and confirmed the failure goes away. It looks like I was 1 commit short in thinking ed059... had the fix > > I recognize I likely don't have enough information in this message to debug > the actual gruby fatal error, and I'm still trying to triage this failure a > little bit > more (to see if I can tell exactly which grubby command is failing during that > fatal error); however, I think in general the practice should be that if > autotest > sees an error when adding the kernel to the bootloader that it should NOT > proceed to reboot the system. That just makes it harder to debug the > problem and produces a system that no longer boots. > > Fair enough, we might just throw an exception rather than being silent about > the failures. > I've filed issue 369 for this: https://github.com/autotest/autotest/issues/369 _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
