On Wed, 19 Aug 2026 23:22:01 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). This pull request has now been integrated. Changeset: f40a2c36 Author: Shiv Shah <[email protected]> Committer: Leonid Mesnik <[email protected]> URL: https://git.openjdk.org/jdk/commit/f40a2c3625484087cfdb41d34b360414ccf0ebd0 Stats: 27 lines in 3 files changed: 24 ins; 0 del; 3 mod 8241634: Support execution of threads as virtual in LingeredApp Reviewed-by: cjplummer, lmesnik ------------- PR: https://git.openjdk.org/jdk/pull/32460
