Skip to content

Reproduce #1911 with failing tests only (no fix, not for merge) - #1930

Closed
jasperblues wants to merge 1 commit into
mainfrom
test/1911-failing-tests
Closed

Reproduce #1911 with failing tests only (no fix, not for merge)#1930
jasperblues wants to merge 1 commit into
mainfrom
test/1911-failing-tests

Conversation

@jasperblues

@jasperblues jasperblues commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Reproduces #1911. Tests only, no fix. Not for merge.

The tests from #1912, applied to main. Nothing else changed.

1. Tests alone on main — 13 of 21 fail

git checkout test/1911-failing-tests
mvn -q test -pl embabel-agent-api -am \
  -Dtest='ExecutorAsyncerCallerThreadTest,SharedExecutorCallerRunsWiringIT' \
  -Dsurefire.failIfNoSpecifiedTests=false

2. #1912 on top — 31 of 31 pass

git merge origin/fix/agentprocess-restore-on-caller-thread
mvn -q test -pl embabel-agent-api -am \
  -Dtest='ExecutorAsyncerCallerThreadTest,SharedExecutorCallerRunsWiringIT,AgentProcessAccessorTest' \
  -Dsurefire.failIfNoSpecifiedTests=false

31 rather than 21 because the merge brings AgentProcessAccessorTest.With, which needs with() to compile.

The 8 that pass in step 1 matter too. OwnedExecutorsNeverRunOnTheCaller green both ways is the evidence for "virtual threads cannot hit this"; PooledThreadIsolation green both ways is the evidence this is not "just stop cleaning up". All 21 red would prove too much.

AgentProcessAccessorTest.With is excluded here on purpose — it calls with(), which #1912 adds, so on main it fails to compile. A compile error proves nothing about behaviour.

Read counts from the surefire XML; rerunFailingTestsCount makes the console summary double-count.

Tests only, on top of main. 13 of 21 fail, which is the point: the defect is
reproducible from configuration a deployment can reach, without reading any of the
argument for it.

Not for merge. #1912 carries the same tests plus the fix.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@jasperblues

Copy link
Copy Markdown
Contributor Author

#1911 was merged. Closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant