On Fri, 21 Aug 2026 02:38:31 GMT, Shiv Shah <[email protected]> wrote:
>> LingeredApp currently always runs its loop on the main thread, so the jtreg >> virtual thread factory never applies to it. With this change the launcher >> forwards the test.thread.factory property to the child, and the app runs its >> loop on a thread from the factory when one is set. The default path is >> unchanged. >> >> One heap dump test limits the virtual thread scheduler to a single carrier >> on purpose, so it now calls the loop directly on the current thread instead, >> and mainLoop was made public for that. The SA heap dump test is problem >> listed for virtual runs, it trips a separate SA issue with virtual threads. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Shiv Shah has updated the pull request incrementally with one additional > commit since the last revision: > > Check the thread factory property directly so the app runs with a minimal > classpath Marked as reviewed by lmesnik (Reviewer). ------------- PR Review: https://git.openjdk.org/jdk/pull/32460#pullrequestreview-5021868240
