Failed Test: mongosh-ReplicaSet_integration__standard_setup_._after_all__hook_in__integration__standard_setup__/test_shell_api/tests_win32-mlatest_n20

XMLWordPrintableJSON

    • 3
    • None
    • Mongosh

      task test_shell_api from variant tests_win32-mlatest_n20 of version mongosh_ab06bafdf52f942592e13423096ec42555f361e6 with status failed

      View Current Status

      The failing test file is ReplicaSet_integration_standard_setup.after_allhook_inintegrationstandard_setup_

      Team assignment of this issue was determined by:
      No assigned team found in offending version.
      No valid failure metadata tags found.
      Not a system/setup failure.
      No assigned team found for test file name.
      No assigned team found by task tags.
      No assigned team found by build variant tags.
      No assigned team found in task to team mapping.
      Found assignment by default team: Mongosh

      Not caused by you? Learn who to reassign it to in the wiki FAQ section 'Foliage has assigned a ticket to the wrong team, what do I do?'

      Logs: https://evergreen.mongodb.com/test_log/mongosh_tests_win32_mlatest_n20_test_shell_api_ab06bafdf52f942592e13423096ec42555f361e6_25_05_04_03_26_49/0?test_name=a11a9262736e0573e5c4d3dd60d453ec#L0:

      Foliage thinks that this is the breaking commit version in this task

      *In this github commit Recent runs (including this commit) had the following results:

      version task status finish time
      mongosh_ab06bafdf52f942592e13423096ec42555f361e6 task FAILED 2025-05-04 05:53:28.585000+00:00
      mongosh_ab06bafdf52f942592e13423096ec42555f361e6 task FAILED 2025-05-04 05:53:28.585000+00:00
      mongosh_5fa4c42c03f5d09796362fba8b8b45e48a7cbae8 task FAILED 2025-05-02 17:46:17.467000+00:00

      Reported by cron job with id 66f9ad87-616f-4d00-b142-772b741512eb

            Assignee:
            Unassigned
            Reporter:
            Cloud GitHub Webhooks
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: