harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <g...@pobox.com>
Subject Re: [buildtest] moving the testing infrastructure forward
Date Tue, 21 Nov 2006 12:07:44 GMT

Tim Ellison wrote:
> Geir Magnusson Jr. wrote:
>> Stefano Mazzocchi wrote:
> <lots of stuff agreed with incl. Geir's clarifications>
>>> 5) config-full.xml currently runs three targets "classlib, drlvm and
>>> drlvm-test" where classlib runs the build and runs the tests. I think
>>> classlib should be split in three: java, native and tests. I also note
>>> that classlib tests need a JVM, so we need to come up with a reasonable
>>> strategy for all that.
>> Yes - each should actually be broken up into sequences :
>> 1)  classlib -> update/build and then unit tests using j9 (IMO) to test
>> classlib in isolation of changes from DRLVM.  It used to be that way IIRC.
> classlib is still buildable and testable right in the working directory
> with the IBM VME in place.  That is what the IBM build machines are
> currently doing and reporting to the commit list.

Of course.  Stefano is talking about the larger-scale sequence run by 
our own build test.

I think that this step using J9 is critical, having that known-good VM 
as the first test of the classlib.


View raw message