On Sat, 14 Nov 2026 16:20:11 GMT, Alan Bateman <[email protected]> wrote:
> The "blocked in write" tests in BlockingSocketOps and BlockingChannelOps are > problematic as the underlying non-blocking socket may be polled as writable > several times before the virtual thread writer blocks indefinitely. The tests > were updated recently to additionally test the blocked thread's parkBlocker, > which makes it harder to test when it wakes up several times. > > The tests are simplified to avoid special casing the writing case. The > runAfterParkedAsync method in both tests now polls the thread until it parks > and the parkBlocker is set. BlockingChannelOps tests the expected parkBlocker > whereas BlockingSocketOps just observed a non-null parkBlocker. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). [sendaoYan](https://github.com/sendaoYan) Can you confirm that your comment was not AI generated? > One thing I'd like to see addressed is that awaitParked has no bound. If the > expected park never happens then the test hangs until the jtreg timeout with > no diagnostic, If such a bug were to arise then the thread dump, invoked by the timeout/failure handler, will show the unparker thread. ------------- PR Comment: https://git.openjdk.org/jdk/pull/33907#issuecomment-6891062449
