crit: System.Exception: Failed to list devices. preventing text from executing on TvOS in 7.0

[ericstj]

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=229239

Build leg reported

System.Runtime.Tests.WorkItemExecution

Pull Request

dotnet/runtime#84355

Action required for the engineering services team

To triage this issue (First Responder / @dotnet/dnceng):

• Open the failing build above and investigate
• Add a comment explaining your findings

If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:

1. Add the label "Known Build Error"
2. Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation

{
   "ErrorMessage" : "crit: System.Exception: Failed to list devices.",
   "BuildRetry": false,
   "ErrorPattern": "",
   "ExcludeConsoleLog": false
}

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

No response

Report

Build	Definition	Test	Pull Request
274350	dotnet/runtime	System.Memory.Tests.WorkItemExecution
274345	dotnet/runtime	System.Runtime.Tests.WorkItemExecution
271126	dotnet/runtime	System.Runtime.Tests.WorkItemExecution	dotnet/runtime#86127
266742	dotnet/runtime	System.Runtime.Handles.Tests.WorkItemExecution

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	4

[ilyas1974]

We deployed XCode 14.3 to all the tvOS systems earlier today. Will continue to monitor this issue, but this update should resolve the issues we are seeing.

[ilyas1974]

@premun could you take a look at this issue when you get a chance? XCode has been updated and the new version is in the logs, but the workloads still are not able to communicate with the AppleTVs
/cc: @steveisok

[premun]

This is a problem with mlaunch being too old. We have an update coming into the branch here: dotnet/runtime#85726

I believe this should help.

[missymessa]

@steveisok it looks like we haven't been seeing any more hits on this issue. Have things been looking okay on your end? Should we close this as resolved?

[steveisok]

I haven't seen it lately either. I think it can be closed.