Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-82355

Investigate why certain jscore tests fail when executed inside of a container

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Build
    • ALL

    Description

      There are certain jscore tests we disable when validating the container build for the mongo-container repo. For example:

      https://github.com/10gen/mongo-container/blob/master/6.0/ubuntu2204/Dockerfile.workload.j2#L38

      https://github.com/10gen/mongo-container/blob/master/7.0/ubuntu2204/Dockerfile.workload.j2#L34

      These may be failing due to minor performance differences when running in the container violating the timing expectations of the tests.

      It may be acceptable to disable a significant portion of these tests, seeing as the mongodb container that docker maintains is likely currently untested. The testing guarantees from jscore may be too strict for the correctness guarantees we want to provide when running on a container.

      This ticket aims to achieve the following goals:

      • Identifying why certain tests fail
      • Creating a subset of jscore tests that we believe is required to validate the correctness of the final container image
      • Creating confidence that new container test failures indicate an actual correctness issue so that we can pass the issues to server developers

      Attachments

        Activity

          People

            Unassigned Unassigned
            zack.winter@mongodb.com Zack Winter
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: