[SERVER-68426] type_bracket.js should not run in parallel suite Created: 29/Jul/22 Updated: 29/Oct/23 Resolved: 02/Aug/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: | Hana Pearlman |
| 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: | 140 | ||||
| Description |
|
This test enabled/disables the optimization failpoint, which can interfere with other tests running in the parallel suite, so we should remove it from parallel. |
| Comments |
| Comment by Hana Pearlman [ 02/Aug/22 ] |
|
Update: We are going with the quick approach of adding type_bracket.js to the block list for the parallel task to stop any hot BFs being generated from bad interactions with this test. There is a larger plan to refactor some of the CQF tests which would remove the disable-pipeline-optimization failpoint from this test. The idea is to block type_bracket.js from parallel now, and then re-enable it later after this work is done. |
| Comment by Hana Pearlman [ 02/Aug/22 ] |
|
Taking over this ticket and the associated BF because we've got a plan to re-organize the CQF js tests a little bit, and it should address this problem (by removing reference to the optimization failpoint). |