If anyone is looking for tasks to contribute to Shenandoah
Jiri Vanek
jvanek at redhat.com
Tue Sep 20 12:52:05 UTC 2016
On 09/20/2016 02:48 PM, Christine Flood wrote:
>
> There's always the list from the team meeting:
>
> Shenandoah productization
>
> Whitebox finalization by team
>
> Blackbox testing/input by those who don't know the codebase as well
>
> Catching supported memory ranges, exiting gracefully
>
> Document options properly
>
> Remove unsupported options
>
> Compressed oops error message should be printed only if user specified it
>
> Implement compressed oops
>
> JBoss stress tests for stability
>
> Kitchen Sink tests
>
> Graduated GC stress tests (speak to adinn about this)
>
> Graceful exit on unsupported platforms
>
Maybe its hidden in above, but I recall after need of proper logging via hotspot api.
J.
More information about the shenandoah-dev
mailing list