From 56ab34865207a1bb4c35e0d480052a08eb0806ff Mon Sep 17 00:00:00 2001 From: Gabor Garancsi Date: Thu, 31 May 2018 10:12:20 +0200 Subject: [PATCH] Fix environment variable setting in RunawayProcessKiller test This way the check can be reenabled as well. --- src/Test/winswTests/Extensions/RunawayProcessKillerTest.cs | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/Test/winswTests/Extensions/RunawayProcessKillerTest.cs b/src/Test/winswTests/Extensions/RunawayProcessKillerTest.cs index 31f950a..db11f44 100644 --- a/src/Test/winswTests/Extensions/RunawayProcessKillerTest.cs +++ b/src/Test/winswTests/Extensions/RunawayProcessKillerTest.cs @@ -75,7 +75,7 @@ namespace winswTests.Extensions // Prepare the env var String varName = WinSWSystem.ENVVAR_NAME_SERVICE_ID; var env = new Dictionary(); - env.Add("varName", winswId); + env.Add(varName, winswId); // Spawn the test process var scriptFile = Path.Combine(tmpDir, "dosleep.bat"); @@ -89,10 +89,9 @@ namespace winswTests.Extensions try { // Generate extension and ensure that the roundtrip is correct - //TODO: checkWinSWEnvironmentVariable should be true, but it does not work due to proc.StartInfo.EnvironmentVariables var pidfile = Path.Combine(tmpDir, "process.pid"); var sd = ConfigXmlBuilder.create(id: winswId) - .WithRunawayProcessKiller(new RunawayProcessKillerExtension(pidfile, checkWinSWEnvironmentVariable: false), extensionId) + .WithRunawayProcessKiller(new RunawayProcessKillerExtension(pidfile), extensionId) .ToServiceDescriptor(); WinSWExtensionManager manager = new WinSWExtensionManager(sd); manager.LoadExtensions();