[SERVER-48609] ChangeStreamTest.assertChangeStreamThrowsCode should run getMore repeatedly Created: 05/Jun/20 Updated: 29/Oct/23 Resolved: 06/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc9, 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bernard Gorman | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | qexec-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Sprint: | Query 2020-06-15 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 16 | ||||||||
| Description |
|
The ChangeStreamTest.assertChangeStreamThrowsCode function expects to see a specific error code upon starting a change stream, but it only runs the initial aggregate and a single getMore before giving up. In a sharded cluster, it is conceivable that the exception will not be seen on the first getMore. We should run getMore in an assert.soon loop to ensure that we do not produce any false negatives. |
| Comments |
| Comment by Githook User [ 06/Jun/20 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: (cherry picked from commit 3a08edc2ed39f7747fa034b449caa569dba72ace) |
| Comment by Githook User [ 06/Jun/20 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: |