[8964] in athena10

home help back first fref pref prev next nref lref last post

Re: [Debathena] #873: Our build infrastructure is not reliable

daemon@ATHENA.MIT.EDU (Debathena Trac)
Sun Apr 29 01:22:18 2012

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: jdreed@MIT.EDU, andersk@MIT.EDU, geofft@MIT.EDU
Date: Sun, 29 Apr 2012 05:22:13 -0000
Reply-To: 
Message-ID: <057.c63bb9be8802b7f36777d11a7b316b18@mit.edu>
In-Reply-To: <042.2f67124897dae0d66702ce5546cf9fac@mit.edu>
Content-Transfer-Encoding: 8bit

#873: Our build infrastructure is not reliable
---------------------+------------------------------
 Reporter:  jdreed   |         Owner:
     Type:  defect   |        Status:  new
 Priority:  blocker  |     Milestone:  Precise Alpha
Component:  --       |    Resolution:
 Keywords:           |  Upstream bug:
---------------------+------------------------------

Comment (by geofft):

 r25470 switches `make-chroot` to using tar-based chroots. This takes a bit
 of time to unpack (anywhere from 15 seconds to over a minute depending on
 how warm the cache is and how contended the operation is), but is
 otherwise perfectly reliable because it's entirely in userspace, and also
 uses a bunch less disk space as a side benefit. I've converted the precise
 chroot to one of these, and it's worked smoothly for the precise build.

 We should convert the remaining chroots on zulu, and figure out what to do
 with the dink volume group. (I think we can empty it of everything but
 schroot-scratch, so it's possible that vg should move onto the zulu volume
 group.) Alternatively, we could wipe and reinstall the build server as
 proposed in #940.

-- 
Ticket URL: <https://athena10.mit.edu/trac/ticket/873#comment:4>
Debathena <http://debathena.mit.edu>
MIT Debathena Project


home help back first fref pref prev next nref lref last post