On Mon, 10 Oct 2022 23:16:20 GMT, Mandy Chung wrote:
> This separates `@run` into its own `@test` that they can be run concurrently.
Ok, thanks for the input. Instead of breaking into separate `@test` blocks, we
should look at how these tests can be broken up and which cases really need to
On Tue, 11 Oct 2022 11:31:51 GMT, Alan Bateman wrote:
> I wouldn't expect it to change the execution time of tier1_part1
I have *seen* the change in total CPU time when I tried to do the same thing
this PR does. This is why I bailed on doing the same thing PR proposes. Cutting
out the tests
On Mon, 10 Oct 2022 23:16:20 GMT, Mandy Chung wrote:
> This separates `@run` into its own `@test` that they can be run concurrently.
I wouldn't expect it to change the execution time of tier1_part1 but it may
help with test selection, maybe combined with putting understandable ids or
jtreg
On Mon, 10 Oct 2022 23:16:20 GMT, Mandy Chung wrote:
> This separates `@run` into its own `@test` that they can be run concurrently.
I did consider when working on `VarHandle` tests recently, but figured this
split penalizes the total CPU time quite significantly. Given that these tests
run
This separates `@run` into its own `@test` that they can be run concurrently.
-
Commit messages:
- 8295104: Break VarHandle tests into separate @test to reduce test execution
time
Changes: https://git.openjdk.org/jdk/pull/10641/files
Webrev:
