[squeak-dev] Hudson build server (was: testrun results)
David T. Lewis
lewis at mail.msen.com
Thu Apr 8 12:53:39 UTC 2010
On Thu, Apr 08, 2010 at 11:53:56AM +0200, Bert Freudenberg wrote:
> On 08.04.2010, at 09:12, Yanni Chiu wrote:
> > Alexander Lazarevi?? wrote:
> >> Thanks! Once a day this just updates a trunk image, runs all tests and compares the results with the previous ones. Only if there are any differences it will send out a report.
> > Check out:
> > http://hudson.jooshr.org/job/Squeak4.1/
> > It's currently set up to run:
> > [Utilities updateFromServer] valueSuppressingAllMessages.
> > once a day, starting with a Squeak4.1-9850-beta image. Then it runs the tests using:
> > HDTestReport runClasses: TestCase withAllSubclasses named: 'AllTestCases'.
> > HDTestReport is available from:
> > http://www.squeaksource.com/HudsonBuild.html
> > The shell scripts and .st scripts are available from:
> > http://github.com/renggli/builder
> > There's also a job to load and test Seaside3.0 into the updated Squeak image, using a Metacello configuration. And, there are some Pharo & Seaside build jobs too.
> > I keep up with image releases, and try to make sure the build keeps running, but not much else. There are some test running incompatibilities between Squeak and Pharo that need to be fixed, but the current workaround is to use some older package versions and customized scripts for Squeak vs. Pharo.
> > --
> > Yanni
> Very nice!
> Which VM version are you using for this? At least the BitBltTest failures need a new VM.
> Or can we change the test to be an expected failure on an older VMs only?
The updated unix VM will be published within a few days, so I don't think
the tests should change (after all they are real failures).
Hmm, I think we need a better way to identify VM version at runtime ...
More information about the Squeak-dev