[CI][MacCatalyst] DocumentTest.PerformAsynchronousFileAccess_Null hangs in File.Delete on x64

Apple platform

Mac Catalyst, x64, in the mac_14_x64 macOS CI test jobs.

Framework version

The captured app paths target net12.0-maccatalyst. The exact selected build SDK, full dotnet/runtime checkout and exclusive native initiating condition are not established by these native app executions; none is inferred from installed SDK folders or queued merge SHAs.

Affected platform version

Captured mac_14_x64 / mac_sonoma test-job configuration, Mac Catalyst x64. No exact host minor/build or common worker origin is asserted without an own current matching diagnostic.

Description

The same 600-second hang in the file-deletion setup for MonoTouchFixtures.UIKit.DocumentTest.PerformAsynchronousFileAccess_Null is source-qualified in 2 physical runtime-configuration failures across 2 distinct monitored PRs.

PR	Exact own product source head	Pipeline 21922 execution	Own Run tests task bounds (UTC)
#26997	`fcdac3f20cc19faec0f5d5bf8793ae3ba8024d5a`	15856875 / own task	`2026-10-29T08:20:33.1966667Z` to `2026-10-29T08:39:45.4833333Z`
#27122	`033ada9e84d5827dc211b5b8db80ac98ae60cec4`	15856860 / own task	`2026-10-29T08:19:15.58Z` to `2026-10-29T08:38:34.9033333Z`

Both source-qualified task/job generations are 1. The repeated job/task GUIDs occur in different run IDs and are two physical executions, not one execution or two retry requests. The timestamps above are original task bounds, not exact hang onset, retry submission or later monitoring clocks.

Each own console first records DocumentTest.Fields passing, then reaches the 600-second guard. The captured active managed boundary is:

Interop.Sys.Unlink
System.IO.FileSystem.DeleteFile
MonoTouchFixtures.UIKit.DocumentTest.GetFileName
MonoTouchFixtures.UIKit.DocumentTest.PerformAsynchronousFileAccess_Null

The exact fixture source at both failed heads has the same Git blob, be2e2ae6f928ea4c608f05f8805232cd89c3619d. GetFileName checks and deletes an existing mydocument.txt under Environment.SpecialFolder.MyDocuments before constructing the document for this test. The active boundary is therefore before the PerformAsynchronousFileAccess(null) assertion can finish.

Both own logs report Execution timed out after 600 seconds., followed by fatal/SIGABRT text and outer exit code 137. This does not prove OOM, a spontaneous initiating crash, a permission prompt, an exclusive filesystem/TCC cause or a genuine flake. No worker policy, setting or identity is inferred.

Each own TestSummary reports one failed configuration group and four passed groups. The complete corresponding HtmlReport archives contain no original NUnit/XML/TRX result files, so these are configuration/console failures, not two fabricated failed NUnit assertion leaves. Passing console lines and unrelated package/API-scan successes are not proof that this original operation recovered or was permanently fixed.

Seven complete open-and-closed searches covered the stable signature, exact test name, fixture, Sys.Unlink, UIDocument, GetFileName and timeout fragments. The full candidate bodies, structured closures and non-ignored paginated histories were inspected. Closed #24702 concerns DocumentTest.Save and a weak/strong gchandle race after PerformAsynchronousFileAccess_Null passed; it is not this earlier file-deletion hang and is not being reopened. #10883 concerns absent native symbols in old Xamarin.iOS libraries, and #6917 is an unrelated FinderSync extension hang.

Steps to Reproduce

Inspect either linked source-qualified run's own Mac Catalyst x64 monotouch-test execution in HtmlReport-mac_14_x64mac_sonoma-1.
Observe DocumentTest.Fields pass and the subsequent file-deletion setup fail to complete.
Confirm the 600-second guard, active managed boundary and outer exit from that same execution. No new local reproduction or CI retry is claimed.

Did you find any workaround?

No validated workaround or exclusive initiating condition. No monitor retry, source/fixture edit, approval, SDK/cache/feed change, worker probe/reset, privacy/security-policy change or remote deletion was performed. Retry capacity remains uncertified because complete all-actor accepted-request history is unavailable; successes do not refund charges or reset lifetime counters.

Relevant log output

MonoTouchFixtures.UIKit.DocumentTest
    [PASS] Fields
Execution timed out after 600 seconds.
Fatal error.
Got a SIGABRT while executing native code.
   at Interop+Sys.Unlink(System.String)
   at System.IO.FileSystem.DeleteFile(System.String)
   at MonoTouchFixtures.UIKit.DocumentTest.GetFileName()
   at MonoTouchFixtures.UIKit.DocumentTest.PerformAsynchronousFileAccess_Null()
Execution completed with exit code 137

Use the linked own tasks and their exact attempt-1 TestSummary/HtmlReport artifacts; Azure artifact retention is limited. Raw commands, environments, full logs, worker identifiers, addresses, process IDs and diagnostic archives are not published. No issue-specific diagnostic checklist applies to a new issue; related-issue comments do not authorize disclosure or scope expansion.

Note

Generated by GitHub Copilot.

Five new source-qualified Mac Catalyst x64 configuration failures hit the same DocumentTest.PerformAsynchronousFileAccess_Null -> GetFileName -> File.Delete -> Interop.Sys.Unlink 600-second boundary. Including the two occurrences already in the issue body, the confirmed x64 hang population is now 7 physical runtime configurations across 4 distinct monitored PRs.

PR	Exact own product source	Own job	Pipeline 21922 task	Own task bounds (UTC)
#26889	`5efb33a77edccfc49b6db6f56ad2087ef972f4d7`	`mac_15_arm64.tests.__default`	15857313 / own task	`2026-10-29T09:12:10.73Z` to `2026-10-29T09:46:54.0533333Z`
#26997	`fcdac3f20cc19faec0f5d5bf8793ae3ba8024d5a`	`mac_15_arm64.tests.__default`	15856875 / own task	`2026-10-29T08:19:51.9833333Z` to `2026-10-29T08:57:18.29Z`
#27092	`a547025bd302e4bfb573d2d35c54709f86f29217`	`mac_14_x64.tests.__default`	15856871 / own task	`2026-10-29T09:22:35.1133333Z` to `2026-10-29T09:40:38.6366667Z`
#27092	`a547025bd302e4bfb573d2d35c54709f86f29217`	`mac_15_arm64.tests.__default`	15856871 / own task	`2026-10-29T08:21:30.3333333Z` to `2026-10-29T08:53:10.6033333Z`
#27122	`033ada9e84d5827dc211b5b8db80ac98ae60cec4`	`mac_15_arm64.tests.__default`	15856860 / own task	`2026-10-29T08:19:29.9266667Z` to `2026-10-29T08:59:11.06Z`

The Mac15 rows are x64 applications in the mac_15_arm64 host selector, not an inferred ARM64 application result or proof of a shared worker cause. Every own successful source reset and each original console member was checked. All four failed-head fixture sources have the same Git blob, be2e2ae6f928ea4c608f05f8805232cd89c3619d, and the same active managed file-deletion boundary, net12.0-maccatalyst app paths, explicit 600-second guard and outer exit 137.

The original signature's mac14 wording records its initial host observation; it is not substituted for the current host selector, exact OS minor/build, worker origin or native initiator. The extra rows remain scoped to the same x64 operation and failure boundary. No TCC/prompt, OOM, exclusive filesystem cause or genuine flake is asserted.

Separate, bounded externally rerun outcomes were also observed for the two original Mac14 failures:

PR	Exact own source	Own external execution	Observed outcome
#26997	`fcdac3f20cc19faec0f5d5bf8793ae3ba8024d5a`	15856875 / Mac14 stage 2, job 2, task retry-counter 1	`UnauthorizedAccessException` in fixture file deletion; outer exit 1, no original XML
#27122	`033ada9e84d5827dc211b5b8db80ac98ae60cec4`	15856860 / Mac14 stage 2, job 2, task retry-counter 1	`UnauthorizedAccessException` in fixture file deletion; outer exit 1, no original XML

Those attempts report console [FAIL] lines for PerformAsynchronousFileAccess_Null and Save before their document operations, not a confirmed pass or recovery of the original hang. No original NUnit/XML/TRX leaf is fabricated from these console names. Their permission exception does not establish the earlier hangs' exclusive initiating condition.

Both runs now expose product-stage/job generation 2 for Mac14 and Mac15, while the independent task retry counter is 1 and the publisher generation is 3. Durable all-actor accounting records at least one new externally accepted-request epoch per run, not one fee per stage, job, task, publisher or observation. The exact accepted count/grouping, actor, requested payload and service-submission clocks remain unobserved. These were not monitor-submitted retries; the parent runs were still in progress at their own captured metadata clocks. No refund, lifetime reset or certified remaining capacity follows.

Each included x64 hang archive contains zero original XML/TRX files, so the population above is configuration-level, not seven invented NUnit assertions. Task bounds are not exact hang-onset, service-submission or final-monitoring times. Exact host minor/build and full dotnet/runtime checkout remain unavailable for these matched executions; none is borrowed from a sibling job. Related ARM64 and permission-error populations remain separately scoped and are not added to the seven x64 hangs.

The refreshed issue body has no Additional info to collect section. Its complete non-ignored history and structured open state are checked again immediately before posting; comment text is not treated as checklist authority. Artifact retention is limited. Worker identifiers, addresses, process IDs, raw commands, full logs and diagnostic archives are not published. No source/fixture, SDK/cache/feed, worker/privacy/security-policy, approval or remote-CI mutation was performed.

Note

Generated by GitHub Copilot.

The two already-observed external Mac15 reruns also hang at the same x64 file-deletion boundary; neither is a recovery. These add 2 confirmed x64 runtime-configuration failures, bringing this exact signature to 9 configurations across 4 distinct monitored PRs.

Classification: unresolved. Stable signature: DocumentTest.PerformAsynchronousFileAccess_Null -> GetFileName -> File.Delete -> Interop.Sys.Unlink, 600-second guard, outer exit 137.

PR	Exact own product source	Pipeline 21922 execution	Own task bounds (UTC)
#26997	`fcdac3f20cc19faec0f5d5bf8793ae3ba8024d5a`	15856875 / own Run tests	`2026-10-29T10:08:24.0933333Z` to `2026-10-29T10:46:32.24Z`
#27122	`033ada9e84d5827dc211b5b8db80ac98ae60cec4`	15856860 / own Run tests	`2026-10-29T10:05:53.65Z` to `2026-10-29T10:38:57.74Z`

Both are x64 applications in mac_15_arm64.tests.__default: product stage 2, job 2, independent task retry-counter 1. Complete own artifact inventories resolve TestSummary-mac_15_arm64mac_sequoia-2 and HtmlReport-mac_15_arm64mac_sequoia-2; the task counter does not select attempt-1 artifacts. The exact original member is tests/maccatalyst-x64-monotouch-test.txt.

For each linked execution, the own successful source reset matches the head above. The unchanged failed-head fixture is Git blob be2e2ae6f928ea4c608f05f8805232cd89c3619d. Both original consoles show DocumentTest.Fields passing, then the explicit 600-second guard and the same active managed unlink/file-deletion stack before PerformAsynchronousFileAccess_Null can complete.

These are also 2 bounded externally rerun original-case outcomes: the corresponding Mac15 stage-1 x64 configurations already failed at that boundary, and stage 2 fails there again. They are the same two new configurations counted above, not two additional hang occurrences. The previously reported Mac14 permission-error outcomes remain separate and unchanged. Related ARM64 configurations are retained under their separately scoped signature and are not added to these x64 totals.

The two accepted-request lower bounds for these runs were already charged when their shared Mac14-2/Mac15-2 epochs became observable. Finishing the Mac15 tasks or publisher generation 3 creates no additional observed request fee. Exact all-actor accepted count/grouping, requested payload, actor and service-submission clocks remain unobserved, so no remaining retry capacity, exact payload satisfaction, refund or lifetime reset is certified. No monitor rerun was submitted.

For each occurrence, the complete own HtmlReport contains zero XML/TRX files: these are original console/runtime-configuration failures, not fabricated NUnit assertion leaves. No current task-bounded crash record is available. The selected build SDK, full dotnet/runtime checkout, exact host minor/build and exclusive initiating native condition remain unavailable for these matched executions; product TFM net12.0-maccatalyst is not a substitute. Task bounds are not exact hang-onset or retry-submission clocks.

The refreshed issue remains open and its body has no Additional info to collect section; body-only checklist results are empty for both new occurrences and both bounded outcomes. Full non-ignored history and structured closure are refreshed again before submission. No TCC/prompt, OOM, shared worker cause or genuine flake is asserted, and no validated workaround is established. No source/fixture, SDK/cache/feed, worker/privacy/security-policy, approval or remote deletion action was performed. Artifact retention is limited; worker identifiers, addresses, process IDs, raw commands, full logs and diagnostic archives are withheld.

Note

Generated by GitHub Copilot.

We recently updated the agent version on some bots, I wonder if some (manually applied) permissions were lost (full-disk access).

One new source-qualified x64 configuration hits the same DocumentTest file-deletion hang on #27122's 8fd2b02960 head. The exact x64 signature now has 10 confirmed runtime configurations across 4 distinct monitored PRs.

PR	Exact own product source	Pipeline 21922 execution	Own Run tests task bounds (UTC)
#27122	`8fd2b02960ef096f1b8a7b62b51075c3cc0f55a0`	15862570 / own task	`2026-10-29T19:12:23.1133333Z` to `2026-10-29T19:49:04.9933333Z`

This is an initial stage-1/job-1 execution, with independent task retry-counter 1, not a newly submitted or externally rerun request. The application is Mac Catalyst x64 under mac_15_arm64.tests.__default; the host selector is not an ARM64 application result or proof of a shared worker origin.

The exact own source reset matches 8fd2b02960, and the fixture remains Git blob be2e2ae6f928ea4c608f05f8805232cd89c3619d. The original tests/maccatalyst-x64-monotouch-test.txt member in HtmlReport-mac_15_arm64mac_sequoia-1 records DocumentTest.Fields passing, then:

Execution timed out after 600 seconds.
Interop.Sys.Unlink
System.IO.FileSystem.DeleteFile
MonoTouchFixtures.UIKit.DocumentTest.GetFileName
MonoTouchFixtures.UIKit.DocumentTest.PerformAsynchronousFileAccess_Null
Execution completed with exit code 137

The complete own archive has zero original XML/TRX result files and no current task-bounded crash record. This is one runtime-configuration failure, not a fabricated NUnit assertion, OOM diagnosis or exact hang-onset timestamp. The selected native-app build SDK, full runtime checkout and exact host minor/build remain unavailable for this execution; net12.0-maccatalyst is not a substitute.

The separately observed ARM64 configuration and earlier Mac14 UnauthorizedAccessException vector remain separately scoped and are not added to these 10 x64 hangs. No exclusive filesystem/TCC cause, permission prompt, worker origin, genuine flake or validated repair is established.

The simulator parent was still in progress at its own captured metadata time. This new failure adds no accepted retry fee, payload-satisfaction claim, refund or lifetime reset; complete all-actor accepted-request history and remaining retry capacity remain uncertified. No monitor CI retry, source/fixture edit, approval, SDK/feed/cache/worker repair, privacy/security-policy change or remote deletion was performed.

The refreshed issue remains open and its body has no Additional info to collect section: the body-only checklist for this occurrence is empty. Full structured closure and non-ignored paginated history are refreshed again before submission. Comment suggestions remain context, not checklist authority or authorization to change worker permissions. Artifact retention is limited; worker identifiers, addresses, process IDs, raw commands, full logs and diagnostic archives are withheld.

Note

Generated by GitHub Copilot.

One new source-qualified x64 configuration hits the same DocumentTest file-deletion hang on #27092's 59c1988239 head. The exact x64 signature now has 11 confirmed runtime configurations across 4 distinct monitored PRs.

PR	Exact own product source	Pipeline 21922 execution	Own Run tests task bounds (UTC)
#27092	`59c1988239d35489082a1ba647da2a3792d9e366`	15869466 / own task	`2026-10-30T02:56:34.2666667Z` to `2026-10-30T03:37:05.8066667Z`

This is the original observed stage-1/job-1 execution, independent task retry-counter 1. The parent queued source is 15cda0cce544d4b51d61e59433590e857c5e2a95, but this exact job's successful source reset proves the product checkout above. That queued-versus-actual mismatch remains unqualified for the initial queue's billing exemption: neither a speculative positive retry fee nor certified free capacity is inferred.

The application is Mac Catalyst x64 under mac_15_arm64.tests.__default; the host selector is not an ARM64 application result or proof of a shared worker origin. The unchanged fixture is Git blob be2e2ae6f928ea4c608f05f8805232cd89c3619d. The original tests/maccatalyst-x64-monotouch-test.txt in HtmlReport-mac_15_arm64mac_sequoia-1 records DocumentTest.Fields passing, followed by:

Execution timed out after 600 seconds.
Interop.Sys.Unlink
System.IO.FileSystem.DeleteFile
MonoTouchFixtures.UIKit.DocumentTest.GetFileName
MonoTouchFixtures.UIKit.DocumentTest.PerformAsynchronousFileAccess_Null
Execution completed with exit code 137

The complete own archive contains zero original XML/TRX result files and no current task-bounded crash record. Its four older or unattributable incidents are not used as this execution's crashes. This is one runtime-configuration failure, not a fabricated NUnit assertion, OOM diagnosis or exact hang-onset timestamp. The native app's selected build SDK, full runtime checkout and exact host minor/build remain unavailable; the separately observed dotnet-test SDK is not transferred to this configuration.

The separately observed ARM64 counterpart and earlier immediate Mac14 permission-error vector remain separately scoped and are not added to these 11 x64 hangs. No exclusive filesystem/TCC cause, permission prompt, worker origin, genuine flake or validated repair is established.

The parent is now independently observed failed. Its completion and the successful API children do not prove this original case passed, a permanent fix, exact retry-payload satisfaction, a refund or lifetime reset. No new accepted-request epoch was observed; complete all-actor accepted-request history and remaining retry capacity remain uncertified. No monitor CI retry, source/fixture edit, approval, SDK/feed/cache/worker repair, privacy/security-policy change or remote deletion was performed.

The refreshed issue remains open; a closing-PR reference is not treated as actual closure or a validated repair. Its body has no Additional info to collect section, so this occurrence's body-only checklist is empty. Full structured state and complete non-ignored history are checked again before submission. Comment suggestions remain context, not checklist authority or authorization to change worker permissions. Artifact retention is limited; worker identifiers, addresses, process IDs, raw commands, full logs and diagnostic archives are withheld.

Note

Generated by GitHub Copilot.

Two new original Mac Catalyst x64 configurations reproduce the same DocumentTest unlink watchdog boundary. The monitor's retained ledger now contains 13 x64 configurations across 6 distinct monitored PRs.

Exact PR/source	Pipeline 21922 execution	Own product TFM	Own Run tests task bounds (UTC)
#27182 / `bc5699001b0e4aa98d57eab7bb9c2a57648debc5`	15870549 / original macOS 15 matrix task	`net11.0-maccatalyst`	`2026-10-30T05:22:39.15Z` to `2026-10-30T06:00:19.57Z`
#27183 / `601067480214b5af6d842daade0402e6b38e00bc`	15870730 / original macOS 15 matrix task	`net12.0-maccatalyst`	`2026-10-30T05:50:08.9433333Z` to `2026-10-30T06:32:52.27Z`

Each is stage 1 / job 1 / independent task counter 1, tests/maccatalyst-x64-monotouch-test.txt; its own job's successful source reset matches the head above. Application x64 is not inferred from the host matrix's ARM64 selector. Both pinned tests/monotouch-test/UIKit/UIDocumentTest.cs files are the same blob be2e2ae6f928ea4c608f05f8805232cd89c3619d.

Both own configuration logs show:

Interop.Sys.Unlink
System.IO.FileSystem.DeleteFile
DocumentTest.GetFileName
DocumentTest.PerformAsynchronousFileAccess_Null
600-second watchdog -> outer exit 137

These are two configuration failures, not fabricated NUnit assertion leaves. Neither archive has original XML/TRX for this configuration or a matching current task-bounded native incident. Selected SDK and full runtime checkout for these native applications remain unavailable; the net11/net12 TFMs above do not transfer the separate dotnet-unit-test SDKs into them.

Classification: unresolved initiating cause, matching this exact x64 boundary. Watchdog abort text does not establish a spontaneous initiating crash, OOM, TCC/prompt issue, exclusive worker cause, or safe repair. The contemporaneous ARM64 unlink configurations and separate immediate UnauthorizedAccess/Save-related signatures are not added to this x64 issue. The issue's closing-PR reference is not a structured closure or validated fix.

Both original parents now ended failed. No exact named-case recovery, permanent fix, accepted-payload satisfaction, refund or budget reset is inferred. No monitor retry was submitted: unresolved failures are not trial-rerun, and complete all-actor accepted-request history/capacity remain uncertified. No source, approval, SDK/cache/feed/worker/privacy-policy change or remote deletion occurred.

The refreshed issue remains open and its body has no Additional info to collect section; both body-only checklists are empty. Own attempt-1 TestSummary/HtmlReport, configuration output and source-reset/pinned-fixture records were inspected; artifact retention is limited. Direct Azure jobs; no Helix work-item link is present. Worker identifiers, addresses, process IDs, raw commands and archives are withheld.

Note

Generated by GitHub Copilot.

One new original Mac Catalyst x64 configuration reproduces the same DocumentTest unlink watchdog boundary on #27182. The exact x64 signature now has 14 confirmed runtime configurations across 6 distinct monitored PRs.

Exact own product source	Pipeline 21922 execution	Own Run tests task bounds (UTC)
`2ed26a6a23cf845e92170e0ddd06c2ac9d5c3157`	15873030 / original macOS 15 matrix task	`2026-10-30T10:48:34.71Z` to `2026-10-30T11:25:04.89Z`

This is stage 1 / job 1 / independent task counter 1, original member tests/maccatalyst-x64-monotouch-test.txt, product TFM net11.0-maccatalyst. The exact job's successful source reset matches this head. The host matrix's ARM64 selector is not an ARM64 application result or proof of a shared worker cause.

The pinned UIDocumentTest.cs is unchanged Git blob be2e2ae6f928ea4c608f05f8805232cd89c3619d. The own console passes DocumentTest.Fields, then reaches the explicit 600-second guard, outer exit 137, with the same active managed boundary:

Interop.Sys.Unlink
System.IO.FileSystem.DeleteFile
DocumentTest.GetFileName
DocumentTest.PerformAsynchronousFileAccess_Null

The complete own HtmlReport contains zero original XML/TRX result files and no current task-bounded native incident. This is one configuration failure, not a fabricated NUnit assertion, spontaneous initiating crash or OOM diagnosis. Native-app selected SDK, full runtime checkout and exact host minor/build remain unavailable; the separate Xtro job's SDK is not transferred here.

The contemporaneous ARM64 unlink configuration and separate Mac14 immediate UnauthorizedAccessException before Perform/Save remain under distinct diagnostic signatures, not added to these 14 x64 hangs. The initiating filesystem/TCC/prompt/worker condition remains unresolved. A closing-PR reference is not structured closure or a validated repair.

The original parent was still in progress at its own captured metadata time. This observation adds no proven accepted-request epoch or retry fee; complete all-actor history and remaining capacity stay uncertified. No monitor retry, source/fixture edit, approval, SDK/cache/feed/worker/privacy-policy change, probe or remote deletion occurred. No named-case recovery, exact retry-payload satisfaction, refund or lifetime reset is claimed.

The refreshed issue remains open and its body has no Additional info to collect section: this occurrence's body-only checklist is empty. Full structured state and complete non-ignored history are checked again before submission. Permission suggestions in comments remain inert context, not repair authority. Own attempt-1 TestSummary/HtmlReport, configuration output, reset and pinned fixture were inspected; artifact retention is limited. Direct Azure job; no Helix work-item link was found. Worker identifiers, addresses, process IDs, raw commands, full logs and archives are withheld.

Note

Generated by GitHub Copilot.

[release/11.0.1xx] [tests] Use temporary directory in DocumentTest/Fi…

One new source-qualified Mac Catalyst x64 configuration hits the same DocumentTest unlink watchdog on #27183's newer head. The exact retained x64 population is now 15 configurations across 6 distinct monitored PRs; this is a new head/run, not a new distinct PR.

Exact source ed8668244bdbfa7c4edccf8e7d173999021db3f1, pipeline 21922, own run 15873899 / task, stage1-job1-task1. Original task bounds: 2026-10-30T13:26:13.76Z to 2026-10-30T14:02:48.6133333Z UTC. These are task bounds, not inferred hang onset or retry-submission clocks.

Own HtmlReport-mac_15_arm64mac_sequoia-1, member tests/maccatalyst-x64-monotouch-test.txt, explicitly targets net12.0-maccatalyst. Its own completed source reset matches this head; application x64 is not inferred from the host's ARM64 matrix selector. Pinned UIDocumentTest.cs remains Git blob be2e2ae6f928ea4c608f05f8805232cd89c3619d.

The original console reaches the 600-second guard, outer exit 137, with the same active boundary:

DocumentTest.PerformAsynchronousFileAccess_Null
DocumentTest.GetFileName
System.IO.FileSystem.DeleteFile
Interop.Sys.Unlink

The complete own native archive has zero original XML/TRX files and no matching current task-bounded application incident. This is one configuration failure, not a fabricated NUnit assertion, OOM or spontaneous initiating crash. Native-app selected SDK, full runtime checkout and exact host minor/build remain unavailable. Related ARM64 unlink, immediate permission failures and silent Contacts headings remain separate signatures; none is added to this x64 count.

Classification: unresolved initiating cause. The run belongs to a duplicated same-head/same-merge callback cohort. No speculative fee or certified initial/free capacity follows from that duplication. It was still in progress at its own metadata capture; unrelated API-child successes do not prove this case recovered. Complete all-actor accepted-request history and remaining capacity are uncertified.

The refreshed issue remains open; its closing-PR reference is not structured closure or a validated repair. Its body has no Additional info to collect section, so this occurrence's body-only checklist is empty. Source reset, pinned fixture, exact attempt-1 TestSummary/HtmlReport and full non-ignored history were inspected. No monitor retry, source/fixture edit, approval, worker/privacy/SDK/cache/feed repair, probe or remote deletion occurred. Direct Azure job; no own Helix work-item link. Artifact retention is limited; worker identifiers, addresses, process IDs, raw commands and archives are withheld.

Note

Generated by GitHub Copilot.

[release/10.0.1xx] [tests] Use temporary directory in DocumentTest/Fi…

[tests] Use temporary directory in DocumentTest/FileCoordinatorTest a…

One new source-qualified x64 configuration hits the same DocumentTest unlink watchdog. Keeping this issue closed: this tested source does not incorporate the merged fixture fix. The retained exact x64 population is 16 configurations across 6 distinct monitored PRs.

Exact owning PR #27122, source identity 3c5516b102ffd6f93c2585cdc46b4adb02f19e8a, pipeline 21922, run 15876062 / own job and task, stage1-job1-task1. Own task bounds are 2026-10-30T18:41:43.3366667Z to 2026-10-30T19:16:45.6033333Z UTC; they are not exact hang onset, retry-submission or final-monitoring clocks.

This is a Mac Catalyst x64 application under mac_15_arm64.tests.__default, original member tests/maccatalyst-x64-monotouch-test.txt, product net12.0-maccatalyst. The host selector is not an ARM64 application result or proof of a shared worker.

The own completed reset matches the head above. Its pinned UIDocumentTest.cs still deletes an existing mydocument.txt under Environment.SpecialFolder.MyDocuments before constructing the document. The original console passes DocumentTest.Fields, then reaches the 600-second guard with outer exit 137 at:

Interop.Sys.Unlink
System.IO.FileSystem.DeleteFile
DocumentTest.GetFileName
DocumentTest.PerformAsynchronousFileAccess_Null

#27145's own PR state independently proves its merge at 2026-10-30T17:17:07Z, not merely the closing reference. Its exact source 03722df4e10d4301af97e721d8a8370f4c43d19c uses NSFileManager.TemporaryDirectory and a process-specific filename. The tested 3c5516... fixture does not contain that change. A later failing-task clock therefore does not demonstrate a regression of the incorporated fix or invalidate this closure.

The complete own native archive has no original XML/TRX or matching task-bounded application incident. This is one configuration failure, not a fabricated NUnit assertion, spontaneous crash or OOM verdict. Native-app selected SDK/full runtime checkout and exact host minor/build remain unavailable. Related ARM64 unlink and immediate Mac14 permission-error configurations remain separately scoped and are not added to this x64 count. Their canonical ambiguity is not resolved by sharing a fixture/method.

The original parent independently ended failed. No exact original-case recovery, permanent repair, requested-payload satisfaction, retry fee, refund or lifetime reset follows; this is its independently qualified first current-source execution, not a monitor retry.

The full body, structured closure and complete non-ignored history were reconciled; there is no Additional info to collect section, so the body-only checklist is empty. Direct Azure evidence; no own Helix work-item applies. Artifact retention is limited. Complete all-actor accepted-request history and safe remaining capacity are uncertified. No source/suppression edit, approval/bypass, shared SDK/cache/feed/auth/privacy/worker repair, endpoint probe or remote deletion occurred. Worker identities, addresses/ports, process IDs, raw commands/environments and archives are withheld.

Note

Generated by GitHub Copilot.

One new source-qualified Mac Catalyst x64 DocumentTest unlink watchdog on #27092: 17 configurations across 6 distinct monitored PRs. This PR was already in the historical population. Keeping this issue closed: the tested source does not incorporate the recent fixture fix.

Head acbadf1c45330161a1b84d4e53d0cdc53dbea1a5, pipeline 21922, run 15882619 / own job and task, stage 1 / phase 1 / job 1 / task 1. Own task bounds: 2026-10-31T02:56:30.9133333Z–2026-10-31T03:41:05.3333333Z UTC; these are not inferred hang-onset or retry-request clocks.

Own HtmlReport-mac_15_arm64mac_sequoia-1, member tests/maccatalyst-x64-monotouch-test.txt, identifies the net12.0-maccatalyst x64 application. After DocumentTest.Fields passes, it reaches the 600-second guard, outer exit 137, with the active stack Interop.Sys.Unlink → FileSystem.DeleteFile → DocumentTest.GetFileName → DocumentTest.PerformAsynchronousFileAccess_Null. Classification: unresolved initiating cause. This is one configuration failure, not a fabricated NUnit assertion, spontaneous crash or OOM verdict.

The launcher's own reset, package producer reset and this job's own same-run package download are independently verified. Pinned fixture blob be2e2ae6f928ea4c608f05f8805232cd89c3619d still deletes a shared Documents filename. #27145 merged at 2026-10-30T17:17:07Z, but its merge commit is not an ancestor of this head. A later task clock alone does not invalidate the fix or closure. Related ARM64 watchdog and immediate permission-error records remain separate and are excluded from this total.

The full native archive has no original XML/TRX or matching task-bounded application incident; its six retained incidents are from October 29, outside this October 31 task. Native-app selected SDK/full runtime checkout, exact host minor/build and an own Helix work-item link are unavailable from this direct-Azure evidence. Worker identities, addresses and process IDs are restricted and withheld. Artifact retention is limited.

Full body, structured closure and complete non-ignored history reconcile 16 earlier configurations/6 PRs plus this new configuration. The body has no Additional info to collect section, so its body-only checklist is empty. Latest parent disposition is inProgress / no final result; no exact-case recovery is established. No monitor retry or source edit occurred; all-actor lifetime/head retry capacity remains uncertified.

Note

Generated by GitHub Copilot.

One new Mac Catalyst x64 DocumentTest unlink watchdog on #27092: 18 configurations across 6 distinct monitored PRs. This PR was already counted. Keeping this issue closed: the tested source still lacks the recent fixture fix.

Head 5534b4acbe8eba132ddd55ec4c552d49619f1345, pipeline 21922, run 15887110 / own job and task, stage 1 / phase 1 / job 1 / task 1. Own task bounds: 2026-11-01T02:52:58.3966667Z–2026-11-01T03:30:47.3233333Z UTC; these are not inferred hang-onset or retry-request clocks.

Own HtmlReport-mac_15_arm64mac_sequoia-1, member tests/maccatalyst-x64-monotouch-test.txt, identifies the net12.0-maccatalyst x64 application. After DocumentTest.Fields passes, it reaches the 600-second guard, outer exit 137, with active Interop.Sys.Unlink → FileSystem.DeleteFile → DocumentTest.GetFileName → DocumentTest.PerformAsynchronousFileAccess_Null. Initiating cause remains unresolved; this is one configuration failure, not an original failed NUnit assertion, spontaneous-crash or OOM finding.

Own launcher/producer resets and this job's same-run package consumption are independently verified. Fixture blob be2e2ae6f928ea4c608f05f8805232cd89c3619d still deletes the shared Documents filename. #27145 merged 2026-10-30T17:17:07Z; its merge is not an ancestor of this head. A later task clock does not invalidate the fix or closure. ARM64 watchdogs and immediate permission errors remain separate and excluded from this census.

The archive has no original XML/TRX or established task-bounded application incident; its retained October 29 incidents predate this task. Native selected SDK/full runtime checkout, exact host minor/build and an own Helix work-item link are unavailable. Worker identities, addresses/home paths and process IDs are withheld; artifacts are retention-limited.

Full body, structured closure and complete non-ignored history reconcile 17 earlier configurations/6 PRs plus this one. The body has no Additional info to collect checklist. Parent remains inProgress / no final result; no exact-case recovery is established. No monitor retry or source edit; all-actor lifetime/head request budgets remain uncertified.

Note

Generated by GitHub Copilot.

Navigation Menu

Repository navigation

[CI][MacCatalyst] DocumentTest.PerformAsynchronousFileAccess_Null hangs in File.Delete on x64 #27138

Apple platform

Framework version

Affected platform version

Description

Steps to Reproduce

Did you find any workaround?

Relevant log output

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[CI][MacCatalyst] DocumentTest.PerformAsynchronousFileAccess_Null hangs in File.Delete on x64 #27138

Description

Apple platform

Framework version

Affected platform version

Description

Steps to Reproduce

Did you find any workaround?

Relevant log output

Activity

dalexsoto commented on Oct 29, 2026

dalexsoto commented on Oct 29, 2026

rolfbjarne commented on Oct 29, 2026

dalexsoto commented on Oct 29, 2026

dalexsoto commented on Oct 30, 2026

dalexsoto commented on Oct 30, 2026

dalexsoto commented on Oct 30, 2026

dalexsoto commented on Oct 30, 2026

dalexsoto commented on Oct 30, 2026

dalexsoto commented on Oct 31, 2026

dalexsoto commented on Nov 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions