On Mon, 16 Nov 2026 18:13:14 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). > > Shiv Shah has updated the pull request incrementally with one additional > commit since the last revision: > > Drop the second summary and the compile lines Updates look okay. ------------- Marked as reviewed by sspitsyn (Reviewer). PR Review: https://git.openjdk.org/jdk/pull/33617#pullrequestreview-5928355436
