這已經困擾了我幾個小時了。如果我安排一個任務在5秒內執行，然后立即取消該任務，我會期望“awaitTermination”方法立即返回，但它會在整個7秒（而不是5秒）內保持阻塞。下面是一個 JUnit 5 測試用例，它在 Java 11 上重現了這個問題。package dummy;import org.junit.jupiter.api.DisplayName;import org.junit.jupiter.api.Test;import java.util.concurrent.Executors;import java.util.concurrent.ScheduledExecutorService;import java.util.concurrent.ScheduledFuture;import java.util.concurrent.TimeUnit;import java.util.concurrent.atomic.AtomicBoolean;import static org.junit.jupiter.api.Assertions.assertFalse;import static org.junit.jupiter.api.Assertions.fail;class DummyTest {  @Test  @DisplayName("Cancelling task should work...")  void cancel_task() throws InterruptedException {    ScheduledExecutorService executorService = Executors.newSingleThreadScheduledExecutor();    AtomicBoolean isExecuted = new AtomicBoolean(false);    ScheduledFuture<?> scheduled = executorService.schedule(() -> isExecuted.set(true), 5, TimeUnit.SECONDS);    scheduled.cancel(false);    if (!executorService.awaitTermination(7, TimeUnit.SECONDS)) {      fail("Didn't shut down within timeout"); // <-- Fails here    }    assertFalse(isExecuted.get(), "Task should be cancelled before executed");  }}有什么想法嗎？