[SERVER-25345] Replace all wasserts Created: 29/Jul/16 Updated: 11/Oct/20 Resolved: 20/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | 3.3.10 |
| Fix Version/s: | 3.7.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 1 |
| Labels: | neweng, platforms-interns-2017 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Platforms 2018-01-29 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
There are about a couple dozen wasserts, most of them don't do anything. We should replace them with invariant/fasserts or uasserts to avoid confusing behavioral difference debug and non-debug builds. We're also not hitting any wasserts in our test suites. We could consider adding test coverage for some of these cases. |
| Comments |
| Comment by Githook User [ 20/Jan/18 ] |
|
Author: {'name': 'Mathias Stearn', 'email': 'mathias@10gen.com', 'username': 'RedBeard0531'}Message: |