On Aug 28, 2006, at 12:04 PM, mdavis wrote: >> The ongoing work with planning the next-gen test system includes >> a few levels of testing, from fast/developer/minimal to slow/ >> thorough/ automated. I don't think we necessarily need faster >> machines (can you believe ben shine just said that?) if we plan >> our testing system well. Even with our split-coast development, >> nightly builds between midnight and 3 am pacific will be done >> before developers wake up and need to see nightly results. Then >> individual bugs that broke should be testable in isolation during >> the day. >> >> The exception to the "3 hours in the middle of the night is >> enough" rule is developing the build/test systems themselves... >> which seems to be my job, and well, I wouldn't mind if the >> complete tests ran in cup-of-coffee time rather than go-to-the- >> grocery-store-then-cook- dinner time. As far as that goes, the >> current situation is acceptable. > > There should be a subset of the tests that you can use to test the > build system.
Now, that would be clever. It's mostly there; nightly/build.xml lets you get particular about whether to fetch a tag from svn, whether to push the tag to the windows and mac machines, and what targets to run when invoking the build from nightly/build.xml into $LPS_HOME/ build.xml. Some of the tests for the build systems inherently require running a complete build; for instance, does the correct version info string make it into the Debug.versionInfo() on the mac installer? (It does, now, but making it do so was an interaction between the ssh command invoked from nightly/build.xml and the tiger-builder-go.sh script run on the mac build machine.) _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
