> 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 tests for 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).

Alan Bateman has updated the pull request incrementally with one additional 
commit since the last revision:

  Print stack trace in unparker thread if it fails

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/33907/files
  - new: https://git.openjdk.org/jdk/pull/33907/files/1257a5b6..d1b1415a

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=33907&range=04
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=33907&range=03-04

  Stats: 2 lines in 2 files changed: 2 ins; 0 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/33907.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/33907/head:pull/33907

PR: https://git.openjdk.org/jdk/pull/33907

Reply via email to