[SERVER-46714] dbtest StorageTimestampTests suite returns successful process exit code despite test failure Created: 09/Mar/20 Updated: 29/Oct/23 Resolved: 27/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc7, 4.7.0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Maria van Keulen |
| 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: |
v4.4
|
||||||||||||||||||||||||
| Sprint: | Execution Team 2020-05-04 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
The CI system currently reports the StorageTimestamp dbtest test suite as successful even though the test summary in the logs indicates a failure in the TimestampIndexBuilderOnPrimary test case. This test case is expected to fail because the underlying applyOps logic was modified in It appears the dbtest executable is exiting early in WiredTigerKVEngine::cleanShutdown() because of the changes in |
| Comments |
| Comment by Githook User [ 19/May/20 ] |
|
Author: {'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}Message: (cherry picked from commit 147beeb42b443c016615d6b101e0cd54b4d618bc) |
| Comment by Githook User [ 27/Apr/20 ] |
|
Author: {'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}Message: |
| Comment by Maria van Keulen [ 22/Apr/20 ] |
|
Looks like the stableTimestamp check fails because one of the StorageTimestampTests explicitly sets the initialDataTimestamp, but never sets the stableTimestamp. I think the quickest way to address this abnormality is to reset initialDataTimestamp to the null timestamp at the end of the offending test. |
| Comment by Maria van Keulen [ 22/Apr/20 ] |
|
Judging from the description of Update: The fix will still have to make sure StorageTimestampTests doesn't leave the timestamps in an invalid state, particularly if we want to guard against unexpected cases reaching the quickExit code path. |