[SERVER-37197] Validation failure does not cause test to fail Created: 18/Sep/18 Updated: 29/Oct/23 Resolved: 19/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 4.1.3 |
| Fix Version/s: | 4.1.4 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Ian Boros | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-dataconsistency | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | TIG 2018-09-24 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Here's an evergreen build from the waterfall: Take a look at the test all_paths_index_multikey.js The test passes: But validation fails: Yet the test is not marked as a failure. The same happens if you run it in resmoke locally (the test is marked as successful, but validation fails). This is a pretty serious problem because it means collection validation could be failing for more severe reasons without our knowing. |
| Comments |
| Comment by Githook User [ 19/Sep/18 ] | |||||||
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: It would otherwise silently ignore cases where collection validation had | |||||||
| Comment by Max Hirschhorn [ 18/Sep/18 ] | |||||||
Thanks for finding this ian.boros! I agree it is a serious problem. The changes from c8f5485 as part of
|