kst4contest

Rsclub2_2/kst4contest

0 Fork 0

mirror of https://github.com/praktimarc/kst4contest.git synced 2026-11-08 22:38:36 +01:00

Author	SHA1	Message	Date
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
Rsclub2_2	05874d6ddb	test: print all threads when a test times out The rare CI hang in SelectedStationMessageUiVisualRenderingTest blocks on a monitor in SnapshotStateObserver.observeReads (line 643 is the monitorenter of observedScopeMapsLock in Compose 1.8.2). The timed-out thread's stack shows where it waits but not which thread holds the lock. With the thread dump enabled, JUnit prints every thread to the test's standard output, which ends up in the XML report of the test-results artifact. Claude-Session: https://claude.ai/code/session_01FJBfPYm6rCH4zD6T7bcC7Y	2026-10-26 10:29:18 +01:00

Author

SHA1

Message

Date

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

Rsclub2_2

05874d6ddb

test: print all threads when a test times out

The rare CI hang in SelectedStationMessageUiVisualRenderingTest blocks on a
monitor in SnapshotStateObserver.observeReads (line 643 is the monitorenter
of observedScopeMapsLock in Compose 1.8.2). The timed-out thread's stack
shows where it waits but not which thread holds the lock. With the thread
dump enabled, JUnit prints every thread to the test's standard output, which
ends up in the XML report of the test-results artifact.

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

2026-10-26 10:29:18 +01:00

2 changed files with 2 additions and 2 deletions

No files matched your search

									
										gradle/libs.versions.toml
									
		+1
		-1
	
												View File
												
				@@ -1,5 +1,5 @@

				[versions]

				sqliteJdbc = "3.54.1.0"

				sqliteJdbc = "3.53.4.0"

				jlayer = "1.0.1"

				junit = "6.1.3"

				mockito = "5.24.0"

									
										gradle/wrapper/gradle-wrapper.properties
									
Vendored

		+1
		-1
	
												View File
												
				@@ -1,6 +1,6 @@

				distributionBase=GRADLE_USER_HOME

				distributionPath=wrapper/dists

				distributionUrl=https\://services.gradle.org/distributions/gradle-9.8.2-bin.zip

				distributionUrl=https\://services.gradle.org/distributions/gradle-9.8.1-bin.zip

				networkTimeout=10000

				retries=0

				retryBackOffMs=500

Compare commits

No files matched your search