I've added a new directory to svn, in scripts/digress, which is a bit of a framework to allow for automated testing of d-i installs. It currently only has scripts for testing ia64's, netbooting with serial console, but the framework is flexible and I hope to add scripts later for more usual things, like bochs.
I've also checked in people/joeyh/autoinstall, which has some preseed files I use for the automated install testing (and other things), and some scheme files, which define machines and setups to do automated installs. This is out of the way because it's all specific to my own personal setup here, but I put it in svn because it may be a useful example. With this setup, I have a cronjob that runs a command: 50 4 * * * DI_TESTDIR=$HOME/html/d-i $HOME/src/d-i/scripts/digress/daily-tests elephant d-i d-i-26; DI_TESTDIR=$HOME/html/d-i $HOME/src/d-i/scripts/digress/test-harness elephant devel-system This automatically reboots my ia64, sets up tftp to boot the lastest build of d-i, and does an automated install. It can detect if the boot or base install fails, and it's all logged. After that test install, it does another one, with the 2.6 kernel. Finally it boots the machine back into my normal development system. Currently the test system stops after the first stage of the install, and does not test the base-config and task installation stage, though I hope to add that once newer versions of tasksel and base-config reach sarge. I also plan to add more test schemes besides the current noninteractive install. The logs are available from this web page: http://people.debian.org/~joeyh/d-i/test-logs.html The web page is set up so I can easily add more people's automated tests to it, if someone else manages to set it up. It would be great to get some more architectures covered. (BTW, I need to thank HP for the loan of the ia64 machine that made it possible for me to set this up.) -- see shy jo
signature.asc
Description: Digital signature
