Skip to content

Fix iOS infinite layout invalidation loop from bit-exact Frame equality (#35142)#35144

Closed
Qythyx wants to merge 1 commit into
dotnet:mainfrom
Qythyx:fix/ios-layout-loop-frame-equality-35142
Closed

Fix iOS infinite layout invalidation loop from bit-exact Frame equality (#35142)#35144
Qythyx wants to merge 1 commit into
dotnet:mainfrom
Qythyx:fix/ios-layout-loop-frame-equality-35142

Fix iOS infinite layout invalidation loop from bit-exact Frame equality

cd1ec75
Select commit
Loading
Failed to load commit list.
Azure Pipelines / maui-pr-devicetests failed Apr 27, 2026 in 1h 6m 19s

Build #10.0.70-ci+pr.35144.azdo.1398460 had test failures

Details

Tests

  • Failed: 2 (0.04%)
  • Passed: 5,008 (95.98%)
  • Other: 208 (3.99%)
  • Total: 5,218

Annotations

Check failure on line 495 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

Build log #L495

Cmd.exe exited with code '1'.

Check failure on line 935 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

Build log #L935

Cmd.exe exited with code '1'.

Check failure on line 51 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

Build log #L51

PowerShell exited with code '1'.

Check failure on line 1 in RequestsCanBeInterceptedAndCustomDataReturnedForDifferentHosts(uriBase: \"https://echo.free.beeceptor.com/sample-request\")

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

RequestsCanBeInterceptedAndCustomDataReturnedForDifferentHosts(uriBase: \"https://echo.free.beeceptor.com/sample-request\")

Assert.Equal() Failure: Strings differ
           ↓ (pos 0)
Expected: "Hello Matthew (param1=value1, param2=valu"···
Actual:   "Failed to fetch"
           ↑ (pos 0)
Raw output
   at Microsoft.Maui.MauiBlazorWebView.DeviceTests.Elements.BlazorWebViewTests.<>c__DisplayClass22_0.<<RequestsCanBeInterceptedAndCustomDataReturnedForDifferentHosts>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.MauiBlazorWebView.DeviceTests.Elements.BlazorWebViewTests.<>c__DisplayClass26_0.<<RunTest>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.DeviceTests.HandlerTestBasement.<>c__DisplayClass20_0.<<AttachAndRun>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.DeviceTests.AssertionExtensions.<<AttachAndRun>g__Run|21_0>d`1[[System.Boolean, System.Private.CoreLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
   at Microsoft.Maui.DeviceTests.AssertionExtensions.<AttachAndRun>d__21`1[[System.Boolean, System.Private.CoreLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
   at Microsoft.Maui.DeviceTests.AssertionExtensions.<>c__DisplayClass72_0`2.<<AttachAndRun>g__Run|0>d[[System.Boolean, System.Private.CoreLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[Microsoft.Maui.IPlatformViewHandler, Microsoft.Maui, Version=10.0.0.0, Culture=neutral, PublicKeyToken=null]].MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.Dispatching.DispatcherExtensions.<>c__DisplayClass2_0`1.<<DispatchAsync>b__0>d[[System.Boolean, System.Private.CoreLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Maui.MauiBlazorWebView.DeviceTests.Elements.BlazorWebViewTests.RunTest(Func`3 test)
--- End of stack trace from previous location ---

Check failure on line 1 in com.microsoft.maui.mauiblazorwebview.devicetests-Signed.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / maui-pr-devicetests

com.microsoft.maui.mauiblazorwebview.devicetests-Signed.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.