• Type: Icon: Epic Epic
    • Resolution: Unresolved
    • Priority: Icon: Unknown Unknown
    • None
    • Component/s: Astrolabe
    • None
    • Sunset Astrolabe
    • To Do
    • 0
    • 0
    • 0
    • 100
    • Needed - No Spec Changes
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-5910 Blocked
      CXX-3230 Blocked
      CSHARP-5509 Blocked
      GODRIVER-3490 Blocked
      JAVA-5798 Blocked
      NODE-6783 Blocked
      MOTOR-1436 Duplicate
      PYTHON-5152 Blocked
      PHPLIB-1633 Blocked
      RUBY-3627 Blocked
      RUST-2163 Blocked
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } #scriptField td.willNotDo { background-color: #FF0000; /* Red color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion CDRIVER-5910 Blocked CXX-3230 Blocked CSHARP-5509 Blocked GODRIVER-3490 Blocked JAVA-5798 Blocked NODE-6783 Blocked MOTOR-1436 Duplicate PYTHON-5152 Blocked PHPLIB-1633 Blocked RUBY-3627 Blocked RUST-2163 Blocked
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      The client libraries team proposes to sunset the Astrolabe testing framework.

      Motivation

      Who is the affected end user?

      Client libraries engineering is primarily affected, as that team is responsible for troubleshooting frequent failures of the Astrolabe test suite.

      However, we should write a scope document to get input from server and Atlas teams, to ensure that they are not relying on this test suite for their own correctness guarantees.

      The client libraries team is confident that drivers have sufficient correctness guarantees from other tests, which is why we are comfortable proposing this change.

      How does this affect the end user?

      N/A

      color: Color value is invalid

      How likely is it that this problem or use case will occur?

      N/A

      color: Color value is invalid

      If the problem does occur, what are the consequences and how severe are they?

      N/A

      color: Color value is invalid

      Is this issue urgent?

      No required timeline.  It's not urgent, but investigation of Astrolabe failures are low yield (the issue is never an actual bug), but often tricky to investigate to prove that failures are environment, and to fix those failures in order to get the suite green again.

      Is this ticket required by a downstream team?

      No

      color: Color value is invalid

      Is this ticket only for tests?

      It is test removal

      Acceptance Criteria

            Assignee:
            andreas.braun@mongodb.com Andreas Braun
            Reporter:
            jeff.yemin@mongodb.com Jeffrey Yemin
            None
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None
              None
              None
              None
              None