Rsclub2_2 ec7ea8ea1d test: render every ImageComposeScene on the AWT event thread ...

The rare CI hang is a lock-order deadlock in Compose Multiplatform 1.8.2,
shown by the thread dump of run 40299943329:

- the test thread renders the scene and holds the FlushCoroutineDispatcher
  runLock while LazyListState.scrollToItem measures and wants the
  SnapshotStateObserver's observedScopeMapsLock;
- the AWT event thread sends the global snapshot notifications and holds
  observedScopeMapsLock in drainChanges while a re-read derived state wakes
  the scene's snapshotFlow collector, whose dispatch wants runLock.

The application renders on the event thread, where both monitors are simply
re-entered. The tests now do the same: onEventThread builds, renders and
closes each scene there and rethrows what the block throws.

Claude-Session: https://claude.ai/code/session_01FJBfPYm6rCH4zD6T7bcC7Y

2026-10-26 11:02:17 +01:00

..

src

test: render every ImageComposeScene on the AWT event thread

2026-10-26 11:02:17 +01:00

build.gradle.kts

Keep tests out of the user profile; small socket fixes (#127)

2026-10-16 10:48:33 +02:00