Skip to content

[Android] Fix VerifyFlowDirectionRTLCanReorderItemsTrueWithCanMixGroups test failure regression #35000

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kubaflo merged 1 commit into from
Apr 17, 2026
+16 −2

Update ReorderableItemsViewAdapter.cs

f62f980
Select commit
Loading
Failed to load commit list.
Merged

[Android] Fix VerifyFlowDirectionRTLCanReorderItemsTrueWithCanMixGroups test failure regression #35000

Update ReorderableItemsViewAdapter.cs
f62f980
Select commit
Loading
Failed to load commit list.
Build Analysis / Build Analysis failed Apr 17, 2026 in 0s

.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.

Known Repository Errors

Known Infrastructure Errors

Build Failures

maui-pr-uitests / WinUI UITests / Controls / Controls WebView

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌The job running on agent NetCore-Public 179 ran longer than the maximum time of 180 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

maui-pr-uitests / Build UITests Sample App / Build Sample App / Build the samples

[ 🚧 Report infrastructure issue] [ 📄 Report repository issue]
    ❌.dotnet/packs/Microsoft.Android.Sdk.Darwin/36.1.2/tools/Microsoft.Android.Sdk.Bindings.Gradle.targets(83,5): Error MSB6006: "gradlew" exited with code 1.
    ❌expand to see the full error
      .dotnet/packs/Microsoft.Android.Sdk.Darwin/36.1.2/tools/Microsoft.Android.Sdk.Bindings.Gradle.targets(83,5): Error XAGRDL0000: Downloading https://services.gradle.org/distributions/gradle-8.13-all.zip ......................10%......................20%......................30%......................40%......................50%......................60%......................70%.......................80%......................90%......................100%

      Welcome to Gradle 8.13!

      Here are the highlights of this release:

      • Daemon JVM auto-provisioning
      • Enhancements for Scala plugin and JUnit testing
      • Improvements for build authors and plugin developers

      For more details see https://docs.gradle.org/8.13/release-notes.html

      To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.13/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
      Daemon will be stopped at the end of

      the build
      w: file:///Us

maui-pr-uitests / Android UITests CoreClr / Controls (API 30) / Controls (API 30) Border,BoxView,Brush,Button / 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.

20 other jobs are failing and were not displayed due to space limitations.
Builds with failures: [maui-pr] [maui-pr-uitests]

Known test errors

 ⚠️ 43 Known test errors not displayed due to space limitations

Test Failures (57 tests failed)

🔹 [All failing tests from maui-pr]

🔹 [All failing tests from maui-pr-uitests]

    ⚠️ 46 failing tests not displayed for this pipeline due to space limitations

    ❌ Microsoft.Maui.TestCases.Tests.BorderFeatureTests(Android).Border_PolygonShapeWithStrokeLineCap_Round [Details] [22.78% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configuration
    Exception Message
    VisualTestUtils.VisualTestFailedException : 
Snapshot different than baseline: Border_PolygonShapeWithStrokeLineCap_Round.png (0.86% 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
    
[Full log]

    CallStack
       at Microsoft.Maui.TestCases.Tests.UITest.VerifyScreenshot(String name, Nullable`1 retryDelay, Nullable`1 retryTimeout, Int32 cropLeft, Int32 cropRight, Int32 cropTop, Int32 cropBottom, Double tolerance) in /_/src/Controls/tests/TestCases.Shared.Tests/UITest.cs:line 296
   at Microsoft.Maui.TestCases.Tests.BorderFeatureTests.Border_PolygonShapeWithStrokeLineCap_Round() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/BorderFeatureTests.cs:line 629
   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, Obj... [Full call stack]
    ❌ Microsoft.Maui.TestCases.Tests.BorderFeatureTests(Android).Border_PolygonShapeWithStrokeLineJoin_Bevel [Details] [22.79% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configuration
    Exception Message
    VisualTestUtils.VisualTestFailedException : 
Snapshot different than baseline: Border_PolygonShapeWithStrokeLineJoin_Bevel.png (0.83% 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
    
[Full log]

    CallStack
       at Microsoft.Maui.TestCases.Tests.UITest.VerifyScreenshot(String name, Nullable`1 retryDelay, Nullable`1 retryTimeout, Int32 cropLeft, Int32 cropRight, Int32 cropTop, Int32 cropBottom, Double tolerance) in /_/src/Controls/tests/TestCases.Shared.Tests/UITest.cs:line 296
   at Microsoft.Maui.TestCases.Tests.BorderFeatureTests.Border_PolygonShapeWithStrokeLineJoin_Bevel() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/BorderFeatureTests.cs:line 288
   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)
... [Full call stack]
    ❌ Microsoft.Maui.TestCases.Tests.BorderFeatureTests(Android).Border_StrokeShape_Path [Details] [22.78% failure rate]
    [ 🚧 Report test infrastructure issue] [ 📄 Report test repository issue]

    Failing Configuration
    Exception Message
    VisualTestUtils.VisualTestFailedException : 
Snapshot different than baseline: Border_StrokeShape_Path.png (0.90% 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
    
[Full log]

    CallStack
       at Microsoft.Maui.TestCases.Tests.UITest.VerifyScreenshot(String name, Nullable`1 retryDelay, Nullable`1 retryTimeout, Int32 cropLeft, Int32 cropRight, Int32 cropTop, Int32 cropBottom, Double tolerance) in /_/src/Controls/tests/TestCases.Shared.Tests/UITest.cs:line 296
   at Microsoft.Maui.TestCases.Tests.BorderFeatureTests.Border_StrokeShape_Path() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/FeatureMatrix/BorderFeatureTests.cs:line 169
   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)
... [Full call stack]

Was this helpful? Yes No

View more details on Build Analysis