So if you've looked at the list of jobs on Jenkins lately you'll notice it's drastically shorter.
I've folded all the deleted jobs into one job, ExternalPackage, that * bootstraps a Smalltalk environment (Cog VM, Interpreter VM, etc.) * preps an image for running tests (updates an image, loads HudsonBuildTools, and saves the image as a base state) * for each Squeak version (currently only 4.4 and 4.5; 4.3 needs to have an Installer fix first) ** for each external package *** loads the package through package-load-test/MyPackage.st *** runs the test
Which means drastically less disk space, but at the cost of quick-glance how're-all-packages-doing. Now you'll have to drill down a bit to see failing tests: http://build.squeak.org/job/ExternalPackages/24/testReport/
Ken's found one problem with the new world order, which is that you sometimes get processes launched by the build that don't get killed. I _hope_ I've fixed this by extending the timeout period for a test sufficiently.
frank
On 22 March 2013 14:56, Frank Shearar frank.shearar@gmail.com wrote:
So if you've looked at the list of jobs on Jenkins lately you'll notice it's drastically shorter.
I've folded all the deleted jobs into one job, ExternalPackage, that
- bootstraps a Smalltalk environment (Cog VM, Interpreter VM, etc.)
- preps an image for running tests (updates an image, loads
HudsonBuildTools, and saves the image as a base state)
- for each Squeak version (currently only 4.4 and 4.5; 4.3 needs to
have an Installer fix first) ** for each external package *** loads the package through package-load-test/MyPackage.st *** runs the test
Which means drastically less disk space, but at the cost of quick-glance how're-all-packages-doing. Now you'll have to drill down a bit to see failing tests: http://build.squeak.org/job/ExternalPackages/24/testReport/
Another cost: you see the test report per Monticello package; it's not necessarily obvious how a Monticello package relates to an application: EitherTests form part of Nutcracker, for instance.
Another benefit: the time to run all these tests is drastically less than the old regime.
frank
Ken's found one problem with the new world order, which is that you sometimes get processes launched by the build that don't get killed. I _hope_ I've fixed this by extending the timeout period for a test sufficiently.
frank
box-admins@lists.squeakfoundation.org