[SERVER-82355] Investigate why certain jscore tests fail when executed inside of a container Created: 20/Oct/23  Updated: 02/Feb/24

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Zack Winter Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Build
Operating System: ALL
Participants:

 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

Generated at Thu Feb 08 06:48:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.