Add workflow timeouts and stop pre-existing tracing

Set timeout-minutes on CI steps to avoid long-running/hung jobs (10m for integration test, 5m for report generation). In the sample test, call Context.Tracing.StopAsync() before starting tracing to ensure any leftover tracing from previous runs doesn't interfere with the new trace run. Modified .github/workflows/motus-ci.yml and samples/Motus.Samples/Tests/TraceCaptureSampleTest.cs.

Author: TorreyBetts

.github/workflows/motus-ci.yml

@@ -108,6 +108,7 @@ jobs:
         run: dotnet build Motus.sln --configuration Release
 
       - name: Test (integration - Chrome)
+        timeout-minutes: 10
         run: >-
           dotnet test Motus.sln
           --configuration Release
@@ -126,6 +127,7 @@ jobs:
 
       - name: Generate Motus reports
         if: always()
+        timeout-minutes: 5
         run: >-
           dotnet run --project src/Motus.Cli/Motus.Cli.csproj --configuration Release --framework net10.0 --no-build --
           run samples/Motus.Samples/bin/Release/net8.0/Motus.Samples.dll

samples/Motus.Samples/Tests/TraceCaptureSampleTest.cs

@@ -16,6 +16,9 @@ public async Task CaptureFullWorkflowTrace()
             AppContext.BaseDirectory, "..", "..", "..", ".."));
         var tracePath = Path.Combine(projectDir, "sample-trace.zip");
 
+        // Stop any pre-existing tracing (e.g. from failure-tracing) before starting fresh
+        await Context.Tracing.StopAsync();
+
         await Context.Tracing.StartAsync(new TracingStartOptions
         {
             Screenshots = true,