Skip to content

[Android] System.Collections.Immutable tests timeout on android-arm and android-x86 #112948

Description

@simonrozsival

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=947194
Build error leg or test failing: System.Collections.Immutable.Tests.WorkItemExecution

Last passing build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=946422
First failing build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=947194
Commit range: 02f99e5...91bbb32

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": [
     "Attempting to remove apk",
     "Successfully uninstalled net.dot.System.Collections.Immutable.Tests",
     "XHarness exit code: 70 (TIMED_OUT)"
  ],
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=962825
Error message validated:
Result validation:
Validation performed at:

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0

Activity

  1. dotnet-policy-service commented on Feb 26, 2025

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-android': @vitek-karas, @simonrozsival, @steveisok, @akoeplinger
    See info in area-owners.md if you want to be subscribed.

  2. dotnet-policy-service commented on Feb 26, 2025

    @dotnet-policy-service
    Contributor

    Tagging subscribers to this area: @dotnet/area-system-collections
    See info in area-owners.md if you want to be subscribed.

  3. added
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    and removed
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    on Feb 27, 2025
  4. steveisok commented on Mar 23, 2025

    @steveisok
    Member

    Looking at the logs, this strikes me as a hang. There's no indication the test process terminated and there's quite a distance in time before helix steps in and kills the run.

    Also, the error message is general for the entire suite regardless of architecture. Not sure if there's a better way tbh.

  5. added this to the Future milestone on May 20, 2025
  6. matouskozak commented on Mar 16, 2026

    @matouskozak
    Member

    No longer failing, closing...

  7. locked and limited conversation to collaborators on Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions