Draft
Conversation
github-actions
bot
added
the
needs-area-label
- Add $(NetCoreAppCurrent)-maccatalyst to TargetFrameworks - Include Unix interop files for maccatalyst target - Create ProcessTests.MacCatalyst.cs with tests for Process.Start, I/O redirection, process killing, exit codes, and process names modeled on ProcessTests.Android.cs Fixes: tests cannot run on MacCatalyst because RemoteExecutor is not supported Agent-Logs-Url: https://github.com/dotnet/runtime/sessions/6cbdf5a5-19f7-46b1-acab-3a4a9f5a6dde Co-authored-by: adamsitnik <6011991+adamsitnik@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add Process tests for MacCatalyst support
Add Process tests for MacCatalyst
Mar 30, 2026
github-actions
bot
added
area-System.Diagnostics.Process
and removed
needs-area-label
Member
|
/azp list |
Contributor
|
Tagging subscribers to this area: @dotnet/area-system-diagnostics-process |
Member
|
/azp run runtime-maccatalyst |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
|
@rolfbjarne @akoeplinger @vitek-karas I am going to need some help, as this failure does not tell me anything: [08:54:54] info: Preparing run for maccatalyst
[08:54:54] info: Getting app bundle information from '/tmp/helix/working/B5070A06/w/A65C0914/e/System.Diagnostics.Process.Tests.app'..
[08:54:54] dbug: Property UIRequiredDeviceCapabilities not present in Info.plist, assuming 32-bit is not supported. Error: Failed to get bundle information: Print: Entry, "UIRequiredDeviceCapabilities", Does Not Exist
[08:54:54] dbug: *** Executing 'System.Diagnostics.Process.Tests' on MacCatalyst *** |
Member
Why is RemoteExecutor not unsupported on MacCatalyst? If we are able to start child processes on MacCatalyst, RemoteExecutor should work just fine. |
Member
I don't know, but I agree it would be the best long-term solution. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All existing
Processtests rely onRemoteExecutor, which is unsupported on MacCatalyst. This adds MacCatalyst-specific tests using simple Unix tools (ls,sleep) available in the MacCatalyst environment, modeled on the Android test additions from #126099.Changes
ProcessTests.MacCatalyst.cs(new): Six MacCatalyst-specificProcesstests covering:Process.Kill()terminationProcessNameavailability for a running processStandardInputHandle/StandardOutputHandle/StandardErrorHandlevia anonymous pipesSystem.Diagnostics.Process.Tests.csproj:$(NetCoreAppCurrent)-maccatalysttoTargetFrameworksmaccatalystin the Unix compile condition (picks upProcessTests.Unix.cs,ProcessThreadTests.Unix.cs, and related interop)ItemGroupto compileProcessTests.MacCatalyst.csonly for themaccatalysttarget