[SERVER-57951] Incorrect data files archived by hook_test_archival.py Created: 22/Jun/21 Updated: 29/Oct/23 Resolved: 28/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.2, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Robert Guo (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v5.0
|
||||
| Sprint: | STM 2021-07-12 | ||||
| Participants: | |||||
| Story Points: | 2 | ||||
| Description |
|
I ran a patch that failed with the expectation that the correct data files were archived, but looking at the task logs, this is what was archived:
However, looking at the test logs, a different dbpath was used for the fixture (mongorunner/, not resmoke/):
I had to apply the following change for this test to archive the correct data files:
Not sure if this matters, but this test is in the slow1 suite. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 27/Jul/21 ] |
|
Author: {'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}Message: (cherry picked from commit ffe55a9d08ecd09e70fb1298b3a37253a3be9cb4) |
| Comment by Githook User [ 27/Jun/21 ] |
|
Author: {'name': 'Robert Guo', 'email': 'robert.guo@mongodb.com'}Message: |
| Comment by Robert Guo (Inactive) [ 24/Jun/21 ] |
|
gregory.wlodarek Thanks for digging into this. You're totally right that the issue is with the distinct fixtures. In general, we expect suites to either use shell or resmoke fixtures, but not both. I've loosened the restriction for archival as part of this ticket, but there might be other limitations in the future if both are used. |
| Comment by Gregory Wlodarek [ 22/Jun/21 ] |
|
I think this issue is caused because slow1 starts up its own fixture: https://github.com/mongodb/mongo/blob/da173c4995cd000da3d585c254f681f13edd0b2c/buildscripts/resmokeconfig/suites/slow1.yml#L18-L22. |