From 39d467b676ebaf0447fa065a0abde82631610455 Mon Sep 17 00:00:00 2001 From: maliming Date: Wed, 25 Mar 2026 18:02:09 +0800 Subject: [PATCH] Reduce timeout in deadlock test for CmdHelper to 10 seconds --- .../Volo/Abp/Cli/Utils/CmdHelper_Tests.cs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/framework/test/Volo.Abp.Cli.Core.Tests/Volo/Abp/Cli/Utils/CmdHelper_Tests.cs b/framework/test/Volo.Abp.Cli.Core.Tests/Volo/Abp/Cli/Utils/CmdHelper_Tests.cs index ab0b96d157..1526a18d42 100644 --- a/framework/test/Volo.Abp.Cli.Core.Tests/Volo/Abp/Cli/Utils/CmdHelper_Tests.cs +++ b/framework/test/Volo.Abp.Cli.Core.Tests/Volo/Abp/Cli/Utils/CmdHelper_Tests.cs @@ -32,9 +32,9 @@ public class CmdHelper_Tests : AbpCliTestBase string output = null; var cmdTask = Task.Run(() => output = _cmdHelper.RunCmdAndGetOutput(command)); - var completed = await Task.WhenAny(cmdTask, Task.Delay(TimeSpan.FromSeconds(30))); + var completed = await Task.WhenAny(cmdTask, Task.Delay(TimeSpan.FromSeconds(10))); - // The original sequential code deadlocked here; 30 s is a generous upper bound. + // The original sequential code deadlocked here; 10 s is a generous upper bound. (completed == cmdTask).ShouldBeTrue( "RunCmdAndGetOutput should not deadlock when both stdout and stderr produce large output");