On 29/06/16 14:05, Vladimir Ivanov wrote: > Most likely, it's JDK-8154239 [1], which is specific to exploded build. > Have you tried to run the tests using complete jdk images? Oh, that again. I remember now that jtreg testing broke in the same way last year. Yes, that seems to fix it. Thanks, Andrew.