-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Open
Description
Description
There are several types of failures encountered on extra-platforms since dotnet/xharness#1416 was integrated into runtime. That change upgraded the mlaunch version and introduced result copying from device/simulator to the host machine to mitigate TCP tunnel limitations on iOS 18.x.
Example build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1095577&view=results
iOS/tvOS failures
A subset of machines has been upgraded to iOS 18.5, and tests running on these machines are failing with the following error:
Error: If you are targeting a data container, you must specify a username.
[18:27:04] dbug: Usage: devicectl device copy from --device <uuid|ecid|udid|name> --source <source> [--destination <destination>] [--user <user>] --domain-type <domain-type> [--domain-identifier <domain-identifier>] [--verbose] [--quiet] [--timeout <seconds>] [--json-output <path>] [--log-output <path>]
Action points:
- Fix the issue in XHarness and flow the fix into runtime
- Reduce logging from XHarness/mlaunch
- The 18.1 version passed in previous PRs; ensure the same machine queue is used in XHarness tests
- AppleTV queue includes machines with higher OS version #117807
- AppleTV queue fails to locate
devicectl
in PATH #117805 - tvOS and iOS scouting queues can't find device xharness#1441
iOS/tvOS simulator failures
Some tests are failing due to launch-timeout issues. These machines are already on 18.x.
Action points:
- Determine if the failures are test-specific or machine-specific
- Check if mlaunch has changed timeout behavior for simulators
MacCataylst failures
After tests complete successfully, Helix reports the following error:
symbol not found in flat namespace '_PyType_GetName'
Action points:
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
No status