Skip to content

test: fix flaky FusingSpec activeStage assertion #3496

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pjfanning merged 1 commit into from
Aug 31, 2026
+5 −1
Merged

test: fix flaky FusingSpec activeStage assertion #3496

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion stream-tests/src/test/scala/org/apache/pekko/stream/FusingSpec.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -377,7 +377,11 @@ class FusingSpec extends StreamSpec {
Await.result(ready.future, 3.seconds)
Await.result(stageActorFuture, 3.seconds) ! "complete"
Await.result(done, 3.seconds) should ===(Done)
Await.result(interpreterPromise.future, 3.seconds).activeStage should be(null)
val completedInterpreter = Await.result(interpreterPromise.future, 3.seconds)
// `done` completes from within the downstream sink's own processing, so the interpreter
// may still be finalizing that stage (and briefly hold it as `activeStage`) when this
// thread wakes. Poll until it has settled rather than reading once and racing the clear.
awaitAssert(completedInterpreter.activeStage should be(null))
}

"stop a lazy stage actor dispatch after its handler fails" in {
Expand Down