runtime: Some iOS tests are failing to launch test app

I just saw a couple of failures on a PR on iOS, with:

[16:59:08] dbug: 16:59:08.5015570 Xamarin.Hosting: Simulator watchdogs are already disabled for 'iOS 13.5 (17F61) - iPhone X'.
[16:59:08] dbug: 16:59:08.5075460 Xamarin.Hosting: Device 'iOS 13.5 (17F61) - iPhone X' is already booted and the simulator is running.
[16:59:08] dbug: 16:59:08.5182020 Xamarin.Hosting: No need to boot (already booted): iPhone X (iOS 13.5) - created by XHarness
[16:59:08] dbug: 16:59:08.5218370 Xamarin.Hosting: Installing /tmp/helix/working/9F630914/w/A3C008F7/e/Microsoft.Extensions.Configuration.Functional.Tests.app with Bundle Identifier net.dot.Microsoft.Extensions.Configuration.Functional.Tests on 'iOS 13.5 (17F61) - iPhone X'...
[17:28:44] dbug: 17:28:44.9031320 Killing process 14971 as it was cancelled
[17:28:44] dbug: 17:28:44.9088890 Process exited with 137
[17:28:44] dbug: 17:28:44.9095210 Test run failed
[17:28:44] dbug: 17:28:44.9175530 Could not find pid in mtouch output.
[17:28:44] dbug: 17:28:44.9224100 Test run started
[17:28:46] dbug: 17:28:46.0798530 Test run failed to launch
[17:28:46] dbug: 17:28:46.0844090 No crash reports, waiting a second to see if the crash report service just didn't complete in time (4)
[17:28:47] dbug: 17:28:47.2295520 No crash reports, waiting a second to see if the crash report service just didn't complete in time (3)
[17:28:48] dbug: 17:28:48.3149390 No crash reports, waiting a second to see if the crash report service just didn't complete in time (2)
[17:28:49] dbug: 17:28:49.4627860 No crash reports, waiting a second to see if the crash report service just didn't complete in time (1)
[17:28:50] dbug: 17:28:50.5966390 No crash reports, waiting a second to see if the crash report service just didn't complete in time (0)
[17:28:51] fail: Failed to launch the application:
                 Launch failure
                 
                 Check logs for more information.
XHarness exit code: 83
+ exit_code=83

https://github.com/dotnet/runtime/pull/45172 https://dev.azure.com/dnceng/public/_build/results?buildId=898906&view=results https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-45172-merge-f3086f428107446aa7/Microsoft.Extensions.Configuration.Functional.Tests/console.c96502f5.log?sv=2019-07-07&se=2020-12-15T00%3A55%3A49Z&sr=c&sp=rl&sig=i1uWKdwS6iGhcUW0XoWG5uWfxxQF%2FwXqK6V6beKh6YM%3D

cc: @premun @dotnet/runtime-infrastructure

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 46 (45 by maintainers)

Commits related to this issue

Forward PYTHONPATH to XHarness iOS script (#6675) When iOS simulators slow down / freeze up, we detect this, retry the work item and reboot the machine. Since the iOS payload script is run through `... — committed to dotnet/arcade by premun 4 years ago

Most upvoted comments

@steveisok would it make sense to open new issues to track the platforms that should run as part of the main runtime pipeline instead of in runtime-staging?

Yes, however, they are on hold to move to the main runtime until we have more resiliency options.

steveisok on Feb 23, 2021

I’d keep this open until we can confirm it helped, if it’s closed we’ll forget to check 😃

akoeplinger on Dec 19, 2020

So I did some investigations and the problem is that we are using launchctl asuser to start XHarness in a user session with GUI rendering capabilities in order to be able to run the Simulator. However, this process doesn’t run in a subshell so we lose all the env variables and that’s why we cannot request an infra retry. I will need to take care of this outside of launchctl so will need more time on this.

premun on Dec 15, 2020

Yes, Monday is fine. That’s why it made sense to move it over to the staging pipeline. Gives us a bit of flex.

steveisok on Dec 11, 2020