Skip to content

Ensure .NET harness workers stop after each feature - #937

Merged
yuandrew merged 1 commit into
mainfrom
yuandrew/fix-dotnet-worker-cleanup
Nov 3, 2026
Merged

yuandrew merged 1 commit into
mainfrom
yuandrew/fix-dotnet-worker-cleanup

Conversation

@yuandrew

@yuandrew yuandrew commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

What was changed

Always call StopWorker() when a feature finishes, including when it returns null or throws. Preserve the original feature failure if cleanup also throws.

Why?

Features like #934 should be able to stop their worker automatically without having to return a workflow handle.

Checklist

  1. Closes Ensure .NET harness stops workers when features return null or throw #936

  2. How was this tested:
    Added nine regression cases covering null returns, execution and check failures, explicit worker stop/restart, and cleanup failures. Updated CI to run them.

  3. Any docs updates needed?

Stop workers when features return no workflow handle or fail during
execution or checks. Preserve the original feature failure when worker
cleanup also fails.

Add nine regression cases and run the harness test project in CI.
@yuandrew
yuandrew requested review from a team as code owners November 3, 2026 15:55
@yuandrew
yuandrew merged commit a065126 into main Nov 3, 2026
29 checks passed
@yuandrew
yuandrew deleted the yuandrew/fix-dotnet-worker-cleanup branch November 3, 2026 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ensure .NET harness stops workers when features return null or throw

2 participants