New Early Access builds

[Christian Stein]

After loading the new Early Access build [0] and
updating the syntax [1], the 1.000.000 virtual tests
... erm ... virtual threads are running like a charm.

Looks like the overhead also decreased, when
looking at the numbers produced on GitHub
Actions (that is Microsoft Azure's containers).
See the updated timings table at [2].

Cheer,
Christian

[0]:
https://github.com/sormuras/junit5-looming/commit/27d59a3fbf5af60bfe19e491134e90b46373615e
[1]:
https://github.com/sormuras/junit5-looming/commit/f3640952e475ca0a2bb8fa58dc9629f23062fef8
[2]: https://github.com/sormuras/junit5-looming#timings


On Mon, Jun 29, 2020 at 8:53 AM Alan Bateman <Alan.Bateman at oracle.com>
wrote:

>
> The builds at the Project Loom Early Access page [1] have been
> refreshed. The latest builds are based on jdk-16+3 (JDK 16 build 3).
>
> There are several stability issues fixed in the latest builds. Several
> people have reported crashes and other issues in recent weeks and it
> would be good to re-run those tests to see if any of these issues persist.
>
> There are a couple of API tweaks and renames. The "Getting started" [2]
> has been updated so it is aligned with the current APIs.
>
> -Alan
>
> [1] http://jdk.java.net/loom/
> [2] https://wiki.openjdk.java.net/display/loom/Getting+started
>