[release/10.0.1xx-sr2] [iOS, macOS] Fixed CollectionView group header size changes with ItemSizingStrategy - #33166
.NET Result Analysis
Details
Tip
To unconditionally bypass the build analysis check (turn it green), you can use the escape mechanism feature. The completion time may vary, potentially taking several minutes, depending on the build analysis workload at the moment.
Build Failures
maui-pr-devicetests / net10.0 iOS Helix Tests / Run DeviceTests iOS / DeviceTestsIOS (Unix)
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌Bash exited with code '1'.
maui-pr-uitests / Android UITests / Controls (API 30) / Controls (API 30) Layout / Controls (API 30) Layout
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌PowerShell exited with code '1'.
maui-pr-uitests / Android UITests / Controls (API 30) / Controls (API 30) Layout / Publish the android_ui_tests_controls_30 test results
[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]-
❌There are one or more test failures detected in result files. Detailed summary of published test results can be viewed in the Tests tab.
2 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [maui-pr-devicetests] [maui-pr-uitests]
Test Failures (4 tests failed)
🔹 [All failing tests from maui-pr-devicetests]
❌ Microsoft.Maui.Controls.DeviceTests.WorkItemExecution [Console] [Details] [Artifacts] [50.53% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
This is a helix work item crash with status: BadExit. To investigate look the [Console log] / navigate to [Helix Artifacts]
Failing Configuration
🔹 [All failing tests from maui-pr-uitests]
- Exception Message
The app was expected to be running still, investigate as possible crash TearDown : The app was expected to be running still, investigate as possible crash
- CallStack
at UITest.Appium.NUnit.UITestBase.UITestBaseTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 87 at UITest.Appium.NUnit.UITestBase.TestTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 38 at InvokeStub_UITestBase.TestTearDown(Object, Object, IntPtr*)
--TearDown
at UITest.Appium.NUnit.UITestBase.UITestBaseTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 87
at UITest.Appium.NUnit.UITestBase.TestTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 38
at InvokeStub_UITestBase.TestTearDown(Object, Object, IntPtr*)1) at UITest.Appium.NUnit.UITestBase.UITestBaseTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 87
at UITest.Appium.NUnit.UITestBase.TestTearDown() in /_/src/TestUtils/src/UITest.NUnit/UITestBase.cs:line 38
at InvokeStub_UITestBase.TestTearDown(Object, Object, IntPtr*)- Exception Message
VisualTestUtils.VisualTestFailedException : Snapshot different than baseline: ModalPageMarginCorrectAfterKeyboardOpens.png (1.34% difference) If the correct baseline has changed (this isn't a a bug), then update the baseline image. See test attachment or download the build artifacts to get the new snapshot file.
More info: https://aka.ms/visual-test-workflow
- CallStack
at VisualTestUtils.VisualRegressionTester.Fail(String message) in /_/src/TestUtils/src/VisualTestUtils/VisualRegressionTester.cs:line 162 at VisualTestUtils.VisualRegressionTester.VerifyMatchesSnapshot(String name, ImageSnapshot actualImage, String environmentName, ITestContext testContext) in /_/src/TestUtils/src/VisualTestUtils/VisualRegressionTester.cs:line 123 at Microsoft.Maui.TestCases.Tests.UITest.<VerifyScreenshot>g__Verify|9_0(String name, <>c__DisplayClass9_0&) in /_/src/Controls/tests/TestCases.Shared.Tests/UITest.cs:line 367 at Microsoft.Maui.TestCases.Tests.UITest.VerifyScreenshot(String name, Nullable`1 retryDelay, Int32 cropLeft, Int32 cropRight, Int32 cropTop, Int32 cropBottom, Double tolerance) in /_/src/Controls/tests/TestCases.Shared.Tests/UITest.cs:line 209 at Microsoft.Maui.TestCases.Tests.Issues.Issue18961.ModalPageMarginCorrectAfterKeyboardOpens() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue18961.cs:line 40 at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted() at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter) at NUnit.Framework.Internal.AsyncToSyncAdapter.Await[TResult](Func`1 invoke) at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context) at NUnit.Framework.Internal.Commands.DelegatingTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)
- Exception Message
System.TimeoutException : Timed out waiting for element...
- CallStack
at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2575 at UITest.Appium.HelperExtensions.WaitForElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 745 at Microsoft.Maui.TestCases.Tests.Issues.Issue24574.TapThenDoubleTap() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue24574.cs:line 41 at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result) at System.RuntimeMethodHandle.InvokeMethod(ObjectHandleOnStack target, Void** arguments, ObjectHandleOnStack sig, BOOL isConstructor, ObjectHandleOnStack result) at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
❌ Microsoft.Maui.TestCases.Tests.DragAndDropUITests(iOS).DragStartEventCoordinates [Details] [3.26% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
❌ Microsoft.Maui.TestCases.Tests.Issues.Issue18961(Android).ModalPageMarginCorrectAfterKeyboardOpens [Details] [46.67% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]
Failing Configuration
❌ Microsoft.Maui.TestCases.Tests.Issues.Issue24574(iOS).TapThenDoubleTap [Details] [18.40% failure rate]
-
[ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]