The listed classes that are failing look familiar to me. I've made a sequence of pairs of commits to the assembly message properties files and the asm test runner's expected error messages file, If your build environment is anything like mine, you may have two file system hierarchies to update from svn and two maven builds to run to keep these tests running properly.
If the test errors you are seeing are of the type "expected message not equal to actual" due to an inserted conformance statement either being absent when expected, or present when not, then I would say that it's just a question of being up to date in both the otests and sca assembly modules extractions and builds. Kelvin. On Wed, Mar 3, 2010 at 1:27 PM, Simon Laws <[email protected]> wrote: > The feels like the sort of thing we need. A couple of points. > > - we need the project(s) you used to package the resources as we will > have to republish the artifacts relatively regularly (maybe they > should be in a more generally accessible area than your p.a.o site) > - we should talk with the OASIS folks to see what they have in mind > re. packaging. We can probably help them along the way and get them > publishing these artifacts sooner rather than later > - Mine ran faster than yours did (but got different results compared > to running the tests from "otest" > > Failed tests: > testDummy(client.ASM_6015_TestCase) > testDummy(client.ASM_5037_TestCase) > testDummy(client.ASM_6002_TestCase) > testDummy(client.ASM_5028_TestCase) > testDummy(client.ASM_5005_TestCase) > testDummy(client.ASM_6021_TestCase) > testDummy(client.ASM_6003_TestCase) > testDummy(client.ASM_5029_TestCase) > testDummy(client.ASM_5024_TestCase) > testDummy(client.ASM_4002_TestCase) > > Tests run: 122, Failures: 10, Errors: 0, Skipped: 0 > > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] There are test failures. > > Please refer to > D:\sca-java-2.x\compliance-tests\assembly-tests\target\surefire- > reports for the individual test results. > [INFO] > ------------------------------------------------------------------------ > [INFO] For more information, run Maven with the -e switch > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 3 minutes 28 seconds > [INFO] Finished at: Wed Mar 03 13:20:34 GMT 2010 > [INFO] Final Memory: 39M/1016M > [INFO] > ------------------------------------------------------------------------ > > Maybe failures to do with the version you packages? > > Speed will be a problem with Assembly/CAA/CII/Policy hooked up. An > extra 16 mins on the build. Then we'll have the otests starting to > come in from the extensions. > > I think we need to get back to this idea about having profiles. I'e a > core profile that does include these compliance tests. Never got round > to doing anything about it as other improvements go my build down to > the 15 minute mark. Creeping back up again now though even without the > otests. > > Simon >
