adjust timeouts to resolve Windows test failures (#1856)

Author: matthewbastien

test/integration-tests/tasks/SwiftTaskProvider.test.ts

@@ -112,7 +112,7 @@ suite("SwiftTaskProvider Test Suite", () => {
                 expect(task?.detail).to.include("swift build --build-tests");
             });
 
-            tag("large").test("executes", async () => {
+            tag("medium").test("executes", async () => {
                 const task = await getBuildAllTask();
                 assert(task);
                 const exitPromise = waitForEndTaskProcess(task);
@@ -138,7 +138,7 @@ suite("SwiftTaskProvider Test Suite", () => {
                 expect(task?.detail).to.include("swift build --show-bin-path");
             });
 
-            test("executes", async () => {
+            tag("medium").test("executes", async () => {
                 const task = await getBuildAllTask();
                 assert(task);
                 const exitPromise = waitForEndTaskProcess(task);

test/integration-tests/utilities/testutilities.ts

@@ -68,7 +68,7 @@ const extensionBootstrapper = (() => {
         let restoreSettings: (() => Promise<void>) | undefined;
         before("Activate Swift Extension", async function () {
             // Allow enough time for the extension to activate
-            this.timeout(120_000);
+            this.timeout(180_000);
 
             // Make sure that CodeLLDB is installed for debugging related tests
             if (!vscode.extensions.getExtension("vadimcn.vscode-lldb")) {