[SERVER-66276] Failpoint set in profile_write_conflict.js fails on parallel suites Created: 06/May/22 Updated: 29/Oct/23 Resolved: 06/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alya Berciu | Assignee: | Alya Berciu |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 46 | ||||
| Description |
|
This test can cause other tests in the parallel suite to fail if they trigger the failpoint earlier than expected. Similarly, if another test gracefully recovers from triggering a failpoint early, this test will fail because it counted the wrong number of conflicts in the profiler entry (since the query that triggered the failpoint may not be the one returned by query to the profiler). |
| Comments |
| Comment by Githook User [ 06/May/22 ] |
|
Author: {'name': 'Alya Berciu', 'email': 'alya.berciu@mongodb.com', 'username': 'alyacb'}Message: |