On Wed, 28 Oct 2026 23:39:26 GMT, Shiv Shah <[email protected]> wrote:
> With the virtual test thread factory main runs on a virtual thread. > AsyncGetCallTrace walks on into the carrier frames there. GetStackTrace stops > at the continuation entry. The test expects the same frames from both and > fails. > > Test only change. The test is now two cases, platform and virtual, each > starts its own thread. A longer AsyncGetCallTrace trace is accepted only when > the frame right after the GetStackTrace ones is Continuation.enterSpecial. > The virtual case requires vm.continuations. Neither case runs with a test > thread factory, the ProblemList-Virtual entry is removed. ProblemList-Xcomp > lists both ids. > > --- > Testing: > - [x] Both cases 5 times on linux-x64 and linux-aarch64 debug, the same with > -XX:-VMContinuations (only the platform case runs), serviceability with the > virtual thread factory, and tier1-3 on those two platforms. > > > --------- > - [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: a9867b35 Author: Shiv Shah <[email protected]> Committer: Serguei Spitsyn <[email protected]> URL: https://git.openjdk.org/jdk/commit/a9867b35f202547c9578420b2ca0f9670ad07398 Stats: 59 lines in 4 files changed: 49 ins; 2 del; 8 mod 8308026: AsyncGetCallTraceTest fails with virtual threads Reviewed-by: sspitsyn, lmesnik ------------- PR: https://git.openjdk.org/jdk/pull/33617
