Operational Defect Database

BugZero found this defect 212 days ago.

MongoDB | 2480257

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

Last update date:

3/15/2024

Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.

Description:

Info

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

Top User Comments


Steps to Reproduce


Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Closed

Learn More

Search:

...