[SERVER-38120] Command in ban_from_views.js test can succeed when it's supposed to fail Created: 13/Nov/18 Updated: 27/Oct/23 Resolved: 26/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Bernard Gorman |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 3 | ||||
| Description |
|
In the change_streams_secondary_reads test suite, the ban_from_views.js may fail due to a command that it expects to fail succeeding. The failure is only triggered when artificial replication lag is induced (by adding a sleep before this line, for example). After adding the artifical repl lag, I was able to reproduce this consistently with the following resmoke invocation:
|
| Comments |
| Comment by Bernard Gorman [ 26/Jul/19 ] |
|
I haven't been able to reproduce this failure after multiple runs of both current master and a66a557, although adding the artificial sleep did cause the fixture setup/teardown to fail in many of the tests. Given this, and the fact that there have been no BFGs generated since the fix for |
| Comment by William Schultz (Inactive) [ 13/Nov/18 ] |
|
Symptom looks identical to BF-7588, but that was supposedly fixed by making sure there are voting secondaries in suite. |