Changes between Version 2 and Version 3 of Ticket #873


Ignore:
Timestamp:
06/28/11 16:38:21 (14 years ago)
Author:
geofft
Comment:

This ticket has nothing to do with OS; in fact, Lucid, being an older OS with an older kernel, is probably more likely to randomly panic on the codepaths we call than Squeeze.

Paths forward include debugging aufs, moving away from unioning file systems to something like unpacking chroots from tarballs, or moving away from using the aufs kernel patch to union mounts or overlayfs or unionfs_fuse or something. (But this ticket is separate from #463; we're interested in a different union solution in the clusters as well, and it may well be that a different solution like tarballs is the right answer for the builder and not for clusters.)

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #873

    • Property Priority changed from high to blocker
    • Property Summary changed from Migrate zulu to not-Debian to Our build infrastructure is not reliable
    • Property Type changed from enhancement to defect
    • Property Milestone changed from Fall 2011 to Natty Beta

  • Ticket #873 – Description

    v2 v3  
    1 Ops would very much prefer it if zulu were not-Debian.  Since we can't make it RHEL unless we want to port all of Debian (what could possibly go wrong?), an Ubuntu LTS is the next best choice, in this case, Lucid.   
     1zulu keeps exploding.   Today, it exploded for the 3rd time in the "Hack binNMU version" stage of the build, though I have no idea why. 
    22 
    3 Ops will give us a Lucid VM, but we'll need to move our build infrastructure over.  We should take this opportunity to fix things and also ensure that the NOTES file is sufficient. 
     3This happened while attempting to do a time-sensitive build, which is very not good.