On Wed, 19 Feb 2025 06:54:50 GMT, Jaikiran Pai <j...@openjdk.org> wrote:
> On a more general note, is it a goal to have the static JDK build run against > all these tests that are part of the JDK repo? Would that mean that a lot of > these will have to start using `@requires` to accomodate this? Running static JDK against all (most of) jtreg tests looks practical, based on what we have learned so far about static support for JDK. I think running against tier1 tests is a good initial minimum goal for now to help building a more solid base for us to work on hermetic support on top of static JDK. Following are the tier1 results that I ran a couple of weeks back on static JDK. Overall most tests are passing on static JDK. The `116` failures in hotspot tier1 include gtest failure due to missing `--with-gtest` (I need to fix my test setup to get cleaner results). So overall I think the number of affect tests requiring `@requires` is small. (linked from https://bugs.openjdk.org/browse/JDK-8348905?focusedId=14745728&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14745728) ============================== Test summary ============================== TEST TOTAL PASS FAIL ERROR >> jtreg:test/hotspot/jtreg:tier1 2709 2592 116 1 << >> jtreg:test/jdk:tier1 2454 2368 86 0 << >> jtreg:test/langtools:tier1 4602 4577 25 0 << jtreg:test/jaxp:tier1 0 0 0 0 >> jtreg:test/lib-test:tier1 35 33 2 0 << ============================== TEST FAILURE ------------- PR Comment: https://git.openjdk.org/jdk/pull/23528#issuecomment-2669547916
