Date: Sun, 8 Jan 1995 08:23:44 -0500 (EST) From: Peter Dufault <dufault@hda.com> To: gibbs@estienne.CS.Berkeley.EDU (Justin T. Gibbs) Cc: freebsd-hackers@freefall.cdrom.com Subject: Re: Commit testing Message-ID: <199501081323.IAA00420@hda.com> In-Reply-To: <199501072100.NAA20491@estienne.cs.berkeley.edu> from "Justin T. Gibbs" at Jan 7, 95 01:00:17 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Justin T. Gibbs writes: > > Well, I usually thoroughly test my code, and when I'm ready to commit > it, SUP current and rebuild, do about an hour or so of testing again, > and commit. Then I re-sup, merge conflicts, and retest to see if I've > left anything out or botched the commit. For future commits, I plan > on checking out a brand new copy of the kernel sources (I sup CVS) in > this phase since otherwise its hard to tell if you left anything out > of the commit. Does this mean you don't test it compile Freefall? It doesn't seem like compiling on freefall is easy unless you check out most of sys. Or am I missing something? I wanted to 1. sup current 2. Test locally 3. Log in; check out, change, compile, check in 4. sup again 5. test locally Is this overkill? Is there an easy way to compile on freefall during step 3? Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 -- Formerly hd@world.std.com. E-mail problems? Tell hdslip@iii.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199501081323.IAA00420>