You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ecf1dd8
Browse filesBrowse the repository at this point in the historyBrowse files
test(ios): pin the query-sweep tier timeout and the tap routing identity to main
Two regressions #2781 still leaves open, both red on this head:
A query sweep that stops at its own slice deadline is a tier timeout, but
the plan classified its payload by node count, so a partial sweep that beat
the sparse threshold armed no XCTest-channel penalty and no later capture
of the same screen was deferred.
The coordinate tap's system-modal routing probe armed its penalty with
currentBundleId read on the command queue, while main owned that state and
could still be clearing or rebinding it.
Copy file name to clipboardExpand all lines: apple/runner/AgentDeviceRunner/AgentDeviceRunnerUITests/UnitTests/RunnerTests+SnapshotCapturePlanOccupancyTests.swift
+108Lines changed: 108 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -258,5 +258,113 @@ extension RunnerTests {
258
258
XCTAssertLessThan(starts.count,sweepQueryCount,"the slice must cut the sweep short")
259
259
XCTAssertFalse(hasAbandonedMainThreadWork())
260
260
}
261
+
262
+
/// A query sweep that stops at its own slice deadline collected a partial tree, not an answer, so
263
+
/// it is a tier timeout: the plan must arm the XCTest-channel penalty and let private AX answer,
264
+
/// keeping the partial sweep only as the fallback. Accepting it because it carries more nodes than
265
+
/// the sparse threshold ships a hierarchy-free capture and leaves every later capture of the same
266
+
/// screen to pay for the full sweep again (#2781).
0 commit comments