[SERVER-46141] Testing burn_in_tests requires multiversion installation Created: 13/Feb/20 Updated: 29/Oct/23 Resolved: 01/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.3.6 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Lydia Stepanek (Inactive) | Assignee: | Alexander Costas (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | tig-burnin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | DAG 2020-04-06 | ||||||||||||
| Participants: | |||||||||||||
| Story Points: | 3 | ||||||||||||
| Description |
|
When I run the tests for burn_in_tests (`python -m unittest buildscripts\/tests\/test_burn_in_tests.py`), I get the following error that mongo-4.2 is not installed:
My understanding is that this test requires a developer to run `buildscripts\/evergreen_gen_multiversion_tests.py` locally in order to create the necessary multiversion mocks that the test needs to run. We should separate these tests into a separate file so that testing burn_in_tests does not also test multiversion setup, since they are different things. As a MongoDB engineer, I should be able to run burn_in_tests tests without needing any multiversion-related dependencies to be installed. AC:
|
| Comments |
| Comment by Githook User [ 07/Apr/20 ] |
|
Author: {'name': 'Alexander Costas', 'email': 'alexander.costas@mongodb.com', 'username': 'ancostas'}Message: |
| Comment by Githook User [ 01/Apr/20 ] |
|
Author: {'name': 'Alexander Costas', 'email': 'alexander.costas@mongodb.com', 'username': 'ancostas'}Message: |