[release/9.0-staging][wbt] Prevent InvalidOperationException on TestOutputHelper logging.

[ilonatommy]

Tell mode, it updates only the tests.

Contributes to #105315.

Fix race condition causing "There is no currently active test" exceptions:

• Wrap TestOutputHelper.WriteLine calls in try-catch blocks
• Continue capturing output even when test context expires
• Add disposal flags to prevent late handler execution

It also fixes the CI after #116747 merge. The PR disabling MT tests did not remove runtime job dependency on the disabled jobs. That caused runtime jobs not to get triggered as the dependency was not satisfied. This PR reverts disabling WBT MT jobs and runtime-official, keeping library MT commented out.

[Copilot]

Pull Request Overview

This PR addresses race conditions that cause InvalidOperationException when logging via TestOutputHelper by adding exception handling, disposal guards, and consolidating logging logic.

• Wraps all TestOutputHelper.WriteLine calls in try-catch blocks with a warning marker on failure
• Introduces an isDisposed flag to prevent handlers from writing after disposal
• Attempts to consolidate duplicate handler logic in ToolCommand

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/mono/wasm/Wasm.Build.Tests/Common/ToolCommand.cs	Wrapped both error/output data handlers’ WriteLine calls in try-catch blocks
src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs	Added isDisposed flag and guards around logging; updated exception and log methods

Comments suppressed due to low confidence (3)

src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:601

• Add unit tests that simulate TestOutputHelper context expiration to verify both the exception-catching path and the buffered output fallback are exercised.

            void LogData(string label, string? message)

src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:490

• [nitpick] The flag isDisposed is used to guard logging after handlers detach. Consider renaming it to something more descriptive (e.g., handlersDisposed or loggingDisabled) to clarify its purpose.

            bool isDisposed = false;

src/mono/wasm/Wasm.Build.Tests/BuildTestBase.cs:620

• Currently outputBuilder.AppendLine runs unconditionally, which may produce lines with null when message is null. Guard this call with if (message != null) to avoid logging an empty or 'null' message.

                    outputBuilder.AppendLine($"{label} {message}");

[ilonatommy]

/azp run runtime

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[ilonatommy]

/azp list

[dotnet-policy-service]

Tagging subscribers to this area: @akoeplinger, @matouskozak, @simonrozsival
See info in area-owners.md if you want to be subscribed.

[jeffschwMSFT]

approved. please get a code review. we will treat this as tell mode