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: [drlvm][testing] Automated Eclipse scenario
Date Sun, 28 Jan 2007 19:34:36 GMT

On Jan 28, 2007, at 10:04 AM, Alexey Varlamov wrote:

> 2007/1/26, Geir Magnusson Jr. <geir@pobox.com>:
>> Why are we bundling this into DRLVM?
>>
>> I think it would be very useful to also run this w/ J9 too....
> No problem :), just run
> $>sh build.sh ehwa.test -Dtest.jvm exe=<path2j9> -Dehwa.test.mode=jit

Cool.

>
> OK, I generally agree, this is true for most or all tests currently
> bundled in drlvm. However we have no federated infrastructure for
> integrational testing (yet?), so I did the first step basing on main
> target audience. E.g. EHWA is particularly good for catching JIT/VM
> regressions, so it should be used as often as possible by VM
> developers; OTOH it is far less critical for everyday classlib tasks.
>

Don't get me wrong - I think this is great!

> Can you suggest better place?

Can we get it into CC? :)


>
>>
>> geir
>>
>>
>> On Jan 26, 2007, at 8:11 AM, Alexey Varlamov wrote:
>>
>> > Folks,
>> >
>> > I'd like to announce 2 new features available now in drlvm build:
>> >
>> > 1) Automated Eclipse HelloWorld Application (aka EHWA) scenario.
>> > Based on Eclipse plugin API, it runs really fast - single iteration
>> > takes much less than 1 minute. Very easy to invoke:
>> >> sh build.sh ehwa.test
>> >
>> > By default, it is run in 3 modes (the same as kernel tests):
>> > jitrino.JET, jitrino.OPT and interpreter. BTW, early runs  
>> allowed to
>> > discover 2 bugs, see HARMONY-3061 and HARMONY-3062.
>> > So this target is highly recommended for pre-integration testing.
>> >
>> > Well, the very first run may be not that fast, as full Eclipse SDK
>> > needs to be downloaded; one may avoid this by setting ECLIPSE_HOME
>> > environment variable pointing to available Eclipse installation.
>> > Though I tested with 3.2 version only, 3.1 may be ok too.
>> >
>> > 2) Shortcut target for efficient running of main pre-commit tests,
>> > including HUT, EHWA, and "build-test". The tests are started in
>> > parallel if enough CPUs available, and run sequentially on  
>> single-core
>> > machines.
>> > All tests are run by the single target:
>> >> sh build.sh test2
>> >
>> > Time to run:
>> > Laptop (T42) Win32 : ~45 min on release DRLVM
>> > Multicore Xeon servers, 32 bit and 64 bit SUSE9: ~20 min  
>> release, ~33
>> > min debug DRLVM
>> >
>> > The limiting time is to finish classlib tests, the time could be  
>> twice
>> > shorter if split HUT to run some modules in parallel.
>> >
>> > --
>> > Alexey
>>
>>


Mime
View raw message