From 565f35b54a06807fcee3f763dd64ae8342cd3e40 Mon Sep 17 00:00:00 2001 From: Iain Nicol Date: Mon, 23 May 2016 13:25:26 +0100 Subject: [PATCH] NUnit3: don't set a timeout on the nunit3-console process A process level timeout is unhelpful, because the timeout is meant to be per test. --- src/app/FakeLib/UnitTest/NUnit/NUnit3.fs | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/app/FakeLib/UnitTest/NUnit/NUnit3.fs b/src/app/FakeLib/UnitTest/NUnit/NUnit3.fs index e7988f8c5a5..5ef1a94ecf7 100644 --- a/src/app/FakeLib/UnitTest/NUnit/NUnit3.fs +++ b/src/app/FakeLib/UnitTest/NUnit/NUnit3.fs @@ -276,11 +276,12 @@ let NUnit3 (setParams : NUnit3Params -> NUnit3Params) (assemblies : string seq) let tool = parameters.ToolPath let args = buildNUnit3Args parameters assemblies trace (tool + " " + args) + let processTimeout = TimeSpan.MaxValue // Don't set a process timeout. The timeout is per test. let result = ExecProcess (fun info -> info.FileName <- tool info.WorkingDirectory <- getWorkingDir parameters - info.Arguments <- args) parameters.TimeOut + info.Arguments <- args) processTimeout let errorDescription error = match error with | OK -> "OK"