Greg Stein wrote:
> I run "make check" on pretty much *all* of my commits. The WC is very
...
> What is your 30 minutes compare to N developers each trying to track
> down a failure?
...
Greg, you're right. Using a ramdisk and an entropy generator, the tests
*really* are pretty quick. Before, I would start make check, watch some TV
and see that an hour later it was apparently working in slow motion.
Since, I've found a way to generate enough entropy (re-compiling apr with
/dev/urandom didn't help, maybe I did something wrong. Instead, I currently
use):
/usr/local/bin/entropy
[[[
#!/bin/sh
echo "*** WARNING!"
echo "*** DON'T USE THIS ON MACHINES THAT NEED QUALITY ENTROPY"
echo "*** FOR GOOD ENCRYPTION!"
sudo rngd -r /dev/urandom -o /dev/random -f -t 1
]]]
and I know how to setup a ramdisk:
/usr/local/bin/svnmount
[[[
#!/bin/sh
target="`pwd`/subversion/tests/cmdline/svn-test-work"
if [ -d "$target" ]; then
rm -rf "$target"
fi
mkdir "$target" && sudo mount -t tmpfs tmpfs "$target" \
-o uid=$USER,mode=770,size=64m
]]]
If I then avoid clobbering the ramdisk by using
make check CLEANUP=true
it completes within a very reasonable time frame.
(quoted all of it so it might help other newbies like me.)
~Neels
>
> Invariably, there is always some time to run that test. I typically
> start the "make check" and then start producing my commit message
> while I review my "diff" for my commit. I always produce a diff,
> review that, and build a commit message. Lots of times, when reviewing
> that diff, I might find some stray debug message, or something a
> little better that I could do, or maybe something that I forgot. But
> it does take a bit to produce that, and in the background, my test run
> is proceeding.
>
> Pause and watch some TV. Surf some web pages. Take a dump. Grab a
> beer. Whatever... there is always something to do while waiting for
> that test to complete, and it will help your fellow developers
> immensely.
>
> Cheers,
> -g
Received on 2008-11-29 02:09:47 CET