Fix tracing when there are multiple self-hosted runners

github · Sep 2, 2020 · 2dbd7e8 · 2dbd7e8
1 parent 68c6069
commit 2dbd7e8
Show file tree

Hide file tree

Showing 3 changed files with 37 additions and 7 deletions.
diff --git a/lib/init.js b/lib/init.js
diff --git a/lib/init.js.map b/lib/init.js.map
diff --git a/src/init.ts b/src/init.ts
@@ -87,9 +87,24 @@ export async function runInit(
           [String]
           $tracer
       )
-      Get-Process -Name Runner.Worker
-      $process=Get-Process -Name Runner.Worker
-      $id=$process.Id
+
+      # Go up the process tree until finding an ancestor called "Runner.Worker.exe"
+      # A new Runner.Worker is spawned for each job. It is spawned by a process
+      # called Runner.Listener that persists for the life of the worker.
+      $id = $PID
+      while ($true) {
+        $p = Get-CimInstance -Class Win32_Process -Filter "ProcessId = $id"
+        Write-Host "Found process: $p"
+        if ($p -eq $null) {
+          throw "Could not determine Runner.Worker.exe process"
+        }
+        if ($p[0].Name -eq "Runner.Worker.exe") {
+          Break
+        } else {
+          $id = $p[0].ParentProcessId
+        }
+      }
+
       Invoke-Expression "&$tracer --inject=$id"`);
 
     await new toolrunnner.ToolRunner(