Skip TCP launch timeout if result files are copied directly

[kotlarmilos]

Description

On iOS 18 and later (devices and simulators), result files are copied directly from the app container instead of being transmitted over TCP. In these cases, the TCP launch timeout logic is skipped to avoid terminating tests when no TCP connection is established.

Changes

• Skip TCP launch timeout logic for Apple mobile platforms on iOS 18+
• Extend resultFileHandler with an IsVersionSupported method
• Update resultFileHandler to throw an exception if the version format is invalid

Contributes to dotnet/runtime#117714

[kotlarmilos]

@rolfbjarne We're encountering the following issue again:

[14:40:31] dbug: Running /private/tmp/helix/working/B1AE0973/p/microsoft.dotnet.xharness.cli/10.0.0-ci/tools/net8.0/any/../../../runtimes/any/native/mlaunch/bin/mlaunch --sdkroot /Applications/Xcode_16.1.app --disable-memory-limits --devname 00008030-00114C222185402E --launchdevbundleid net.dot.iOS.Simulator.PInvoke.Test --wait-for-exit -v -v -v -v -v
[14:40:39] dbug: Process mlaunch exited with 42
[14:40:39] fail: App run has failed. mlaunch exited with 42

Do you know what might be causing this? Is the mlaunch invocation incorrect?

Note this happens when using scouting queues (18.x) only.

[akoeplinger]

Process mlaunch exited with 42

That test is supposed to be exiting with 42 so it looks like mlaunch is somehow using that as its own exit code

[rolfbjarne]

Process mlaunch exited with 42

That test is supposed to be exiting with 42 so it looks like mlaunch is somehow using that as its own exit code

Yes, that's correct, mlaunch will forward the exit code if it can.