> 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 ------------- Changes: - all: https://git.openjdk.org/jdk/pull/32460/files - new: https://git.openjdk.org/jdk/pull/32460/files/dca47bb0..1cbd6018 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=32460&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=32460&range=01-02 Stats: 4 lines in 1 file changed: 0 ins; 1 del; 3 mod Patch: https://git.openjdk.org/jdk/pull/32460.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/32460/head:pull/32460 PR: https://git.openjdk.org/jdk/pull/32460
