RFR: 8323515: Create test alias "all" for all test roots [v3]

Jan Lahoda jlahoda at openjdk.org
Tue Jan 23 11:45:28 UTC 2024


On Tue, 16 Jan 2024 09:01:35 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:

>> Since recent work to improve `tier4` performance, we actually test `tier{1,2,3,4}` often, which includes all the tests in current tree. It would be more convenient to just have the `all` test group/alias, so that we can do `make test TEST=all`. This also gives a parallelism / run time benefit, as we do not wait for tests in each tier to complete before moving to next tier. 
>> 
>> Sample run on out-of-the-box Linux x86_64 fastdebug is below. For some environments one also needs to supply a few keywords like `!printer` to skip tests that cannot complete without failure due to misconfiguration. I left the keywords as is to show how would a failing run look. There is also an existing shortcut in build system that allows to run this with `make test-all`.
>> 
>> 
>> % make test TEST=all
>> 
>> Test selection 'all', will run:
>> * jtreg:test/hotspot/jtreg:all
>> * jtreg:test/jdk:all
>> * jtreg:test/langtools:all
>> * jtreg:test/jaxp:all
>> * jtreg:test/lib-test:all
>> 
>> (...about 6 hours later...)
>> 
>> ==============================
>> Test summary
>> ==============================
>>    TEST                                              TOTAL  PASS  FAIL ERROR   
>>>> jtreg:test/hotspot/jtreg:all                       6731  6702    29     0 <<
>>>> jtreg:test/jdk:all                                 9962  9951    11     0 <<
>>    jtreg:test/langtools:all                           4469  4469     0     0   
>>    jtreg:test/jaxp:all                                 513   513     0     0   
>>    jtreg:test/lib-test:all                              32    32     0     0   
>> ==============================
>> TEST FAILURE
>
> Aleksey Shipilev has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Catch-all -> All tests

I have nothing against it, but I don't think I know enough about details of jtreg configuration to provide approval. OTOH, I personally don't see a strong need for it.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/17422#issuecomment-1905864727


More information about the core-libs-dev mailing list