Skip to content

[mono][android] Investigate failures on Linux Bionic [x64/arm64] jobs #100281

Open

Description

@matouskozak

Description

Linux bionic jobs have been lately unreliable and unusable due to extensive number of failures. These failures must be triaged and eliminated to gain reliable coverage on this platform. This is a part of improving the reliability and coverage of Mobile testing infrastructure (#99949).

Error types

Overall, x64 Linux bionic is slightly more reliable than arm64 version. There are 3 main error patterns occuring on linux_bionic-[x64/arm64] Release AllSubsets_Mono jobs across many test suits.

  1. Segmentation faults - (exit code 139)
dbug: Exit code: 139
Std out:
Std err:   Segmentation fault 
  1. Device not found - (exit code 81)
XHarness exit code: 81 (DEVICE_NOT_FOUND)
  1. Operation got canceled (time out) - (exit code -4)
    • Test finishes without failures but the entire job gets cancelled (happening mostly on x64)
##[error]The Operation will be canceled. The next steps may not contain expected logs.
##[error]The operation was canceled.
  • there are other types of errors happening but these 3 account for the majority of failures.

Investigation areas

  • Usage of simulator instead of devices
  • Runtime vs Library tests

Goals

  • understand what is triggering the above-mentioned errors
  • eliminate these errors from the testing infrastructure
  • make Linux bionic jobs green

FYI: @kotlarmilos @vitek-karas

Known Issue Error Message

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

{
  "ErrorMessage": "",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Report

Summary

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

Activity

  1. added this to the 9.0.0 milestone on Mar 26, 2024
  2. simonrozsival commented on Apr 16, 2024

    @simonrozsival
    Member

    /cc @rzikm

  3. removed
    blocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
    on Jul 23, 2024
  4. vitek-karas commented on Aug 7, 2024

    @vitek-karas
    Member

    Moving this to 10 as we don't really need this to hit RC1 for 9.

  5. modified the milestones: 9.0.0, 10.0.0 on Aug 7, 2024
  6. modified the milestones: 10.0.0, Future on Jul 9, 2025
  7. matouskozak commented on Jul 9, 2025

    @matouskozak
    MemberAuthor

    Not a priority for .NET 10, moving to Future

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