[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:
Depends
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: SERVER-66276 Stop profile_write_conflict.js from running in parallel
Branch: master
https://github.com/mongodb/mongo/commit/6258bc03a01721ff481c44e400fa733113bd64a5

Generated at Thu Feb 08 06:04:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.