fix(test): Fix flaky MainEventProcessorTest by checking crashed thread (#5126)

adinauer · claude · web-flow · commit 9dc12d16737e · 2026-02-27T12:46:14.000Z
Assert stacktrace on the crashed thread instead of the first thread in
the list, which may not be the crashed one depending on thread ordering.

Co-authored-by: Claude Opus 4.6 &lt;noreply@anthropic.com&gt;
diff --git a/sentry/src/test/java/io/sentry/MainEventProcessorTest.kt b/sentry/src/test/java/io/sentry/MainEventProcessorTest.kt
@@ -258,7 +258,7 @@ class MainEventProcessorTest {
 
     assertNotNull(event.threads)
     assertEquals(1, event.threads!!.count { it.isCrashed == true })
-    assertNotNull(event.threads!!.first().stacktrace)
+    assertNotNull(event.threads!!.first { it.isCrashed == true }.stacktrace)
   }
 
   @Test

Original file line number	Diff line number	Diff line change
`@@ -258,7 +258,7 @@ class MainEventProcessorTest {`
`258`	`258`
`259`	`259`	`assertNotNull(event.threads)`
`260`	`260`	`assertEquals(1, event.threads!!.count { it.isCrashed == true })`
`261`		`- assertNotNull(event.threads!!.first().stacktrace)`
	`261`	`+ assertNotNull(event.threads!!.first { it.isCrashed == true }.stacktrace)`
`262`	`262`	`}`
`263`	`263`
`264`	`264`	`@Test`