junhyeong9812 bbfe6a0473 Make immediate-cancel task termination test deterministic ...

The taskTerminationTimeoutWithImmediateCancel test submitted a task and
immediately closed the executor, then asserted that the future was
cancelled. The cancellation flag is set by close() on the calling thread,
while it is checked at the start of the task on a separate worker thread.
With no ordering guarantee between the two, a quickly scheduled worker
could pass the cancellation check before close() set the flag, complete
the trivial task normally, and leave the future uncancelled, making the
test fail intermittently under load.

Override doExecute to capture the task-tracking wrapper instead of
running it on a background thread, then run it on the test thread after
close() has set the cancellation flag. This exercises the same
cancellation path deterministically, with no reliance on thread
scheduling.

Signed-off-by: junhyeong9812 <pickjog@gmail.com>

2026-07-10 20:30:19 +02:00

..

src

Make immediate-cancel task termination test deterministic

2026-07-10 20:30:19 +02:00

spring-core.gradle

Consistently ignore non-loadable annotation types with ClassFile/ASM

2026-03-11 13:52:19 +01:00