dotnet / dotnet/xharness

Apple mobile runtime test finish is not detected

Open
#1,552 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

apple bug device
Dominant language
C#
Stars
189
Forks
67
Avg merge
1d 12h
Merged PRs (30d)
29

Description

The runtime tests (not libraries) run successfully but the execution gets killed causing final error exit code:

Test log

[23:46:18.0680850] 	2026-03-08 20:46:18.179 Regression_1[18131:12618610] 20:46:18.178 Passed test: JIT/Regression/CLR-x86-JIT/V2.0-Beta2/b426654/b426654/b426654.cmd
[23:46:18.0902690] 	2026-03-08 20:46:18.201 Regression_1[18131:12618610] Xml file was written to the provided writer.
[23:46:18.0921010] 	2026-03-08 20:46:18.203 Regression_1[18131:12618610] 
[23:46:18.0921510] 	=== TEST EXECUTION SUMMARY ===
[23:46:18.0921650] 	Tests run: 36 Passed: 36 Inconclusive: 0 Failed: 0 Ignored: 0 Skipped: 0
[23:46:18.0932100] Killing process 16152 as it was cancelled
[23:46:18.0937720] 	2026-03-08 20:46:18.203 Regression_1[18131:12618610] 802c8349-e4b7-40eb-8c1d-193612c0e3a6
[23:46:18.0938060] 	2026-03-08 20:46:18.203 Regression_1[18131:12618610] [TerminateWithSuccess]
[23:46:18.0938960] 	2026-03-08 20:46:18.205 Regression_1[18131:12618610] Test results saved to: /var/mobile/Containers/Data/Application/1E4F522D-35AE-44BC-A30D-38561C1637DC/Library/Caches/Documents/test-results.xml

Console log

[23:46:18] dbug: Detected test end tag in application's output
[23:46:18] dbug: Process mlaunch exited with 137
[23:46:18] dbug: Test run completed
[02:44:54] dbug: Process 16137 already exited or busy: No process is associated with this object.
[02:44:54] dbug: Killing process 16137 as it was cancelled
[02:44:54] dbug: Process 16128 already exited or busy: No process is associated with this object.
[02:44:54] dbug: Killing process 16128 as it was cancelled
[02:44:54] fail: Run timed out after 10800 seconds
ERROR: WORKLOAD TIMED OUT - Killing user command..

Additionally, the test log is not included in the main console log.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Apple mobile runtime run using the test log and console log details, focusing on the detected test-end tag, mlaunch exit 137, cancellation, and timeout handling. Trace how successful runtime completion is propagated and how the test log is forwarded to the main console log. Done means a fully passed run exits successfully without a timeout and includes the test log in the main console output.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, ios
Domain
mobile-dev, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.