On 28/04/16 01:33, Dale wrote: > Michael Mol wrote: >> I have my system automatically update nightly, and check the build results >> in >> the morning. If there's a persistent build error for a couple days, I file a >> bug report. That's my threshold, anyway. >> > > > This started on Sunday. So it has met that part anyway. Since I run a > mix of stable and unstable, it has been known to cause issues that are > weird. I just don't want to file a bug report and take up a devs time > if it is some weird one off thing that affects no one else. It's not > like they don't have enough stuff to deal with already. Then again, > they do want info on failures so that it doesn't affect others. Where's > my coin to flip? lol > > I plan to sync again and if it persists, Raid comes out. :/ > > Thanks. > > Dale > > :-) :-) >
I have a couple of background "things" happening at the moment: prelink and glibc: odd failures that make no sense - unprelink the system and everything works fine (at some point you get a failure to fork.) I hit it when trying to build multiple lxc instances ... it builds two and then the server becomes "toast" :( There is a bug on bgo ... btrfs and kernels 4.4.6 and 4.4.7: fails to convert/balance a raid 10 (system hard lock, no errors) and maybe some file system related build errors (which might also be glibc related, though it might not ...) 4.4.8 works fine (includes a number of btrfs fixes) Either of those fit? BillK
