[SERVER-72928] Expand burn-in-tags to all required & suggested variants Created: 17/Jan/23 Updated: 29/Oct/23 Resolved: 01/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, 6.0.7, 7.0.0-rc3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tausif Rahman (Inactive) | Assignee: | Tausif Rahman (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Server Development Platform
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v7.0, v6.0
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 160 | ||||||||||||||||||||||||
| Description |
We've looked into burn-in-tags & have decided this sends a better signal on whether a devs jstest changes will introduce multiversion failures (or other failures) or not. Instead, we've decided to expand burn-in-tags coverage to all required and suggested variants. A separate task-generator ticket will be done in conjunction with this to make the UX more clear that jstests have been affected as a result of the current changes. |
| Comments |
| Comment by Githook User [ 01/Jun/23 ] |
|
Author: {'name': 'Tausif Rahman', 'email': 'tausif.rahman@mongodb.com', 'username': 'trahman1318'}Message: (cherry picked from commit a4837acbd304b879a35026a34fcb9da6a96f2ef6) |
| Comment by Githook User [ 01/Jun/23 ] |
|
Author: {'name': 'Tausif Rahman', 'email': 'tausif.rahman@mongodb.com', 'username': 'trahman1318'}Message: (cherry picked from commit a4837acbd304b879a35026a34fcb9da6a96f2ef6) |
| Comment by Githook User [ 31/May/23 ] |
|
Author: {'name': 'Tausif Rahman', 'email': 'tausif.rahman@mongodb.com', 'username': 'trahman1318'}Message: |
| Comment by Githook User [ 26/May/23 ] |
|
Author: {'name': 'Tausif Rahman', 'email': 'tausif.rahman@mongodb.com', 'username': 'trahman1318'}Message: |
| Comment by Annie Black [ 24/May/23 ] |
|
That works. Thanks for taking a look! |
| Comment by Alex Neben [ 23/May/23 ] |
|
I think the situation where we generate more than 2k tasks is very unlikely (but possible). I don't think we need to block this since the odds that someone does this are extremely slim. If someone does manage to do this in the next two weeks I will explain to them that they cannot run this burn in with 50k tasks. I am moving this to unblocked. Lmk if you feel strongly against this. |
| Comment by Tausif Rahman (Inactive) [ 23/May/23 ] |
|
Okay, that sounds promising on our end w/ this ticket. We can very easily set an upper limit to the number of generated burn-in tasks that we activate. After EVG-19965 I think we'll have a pretty good idea. |
| Comment by Annie Black [ 23/May/23 ] |
|
(We have actually noticed that 50,000 tasks can exist, they just can't all be activated. We'll look into understanding where we stop being able to activate tasks.) |
| Comment by Tausif Rahman (Inactive) [ 23/May/23 ] |
|
annie.black@mongodb.com Sounds good! I'm okay with waiting on this & checking back in a week. |
| Comment by Annie Black [ 23/May/23 ] |
|
tausif.rahman@mongodb.com we may need to block this work on EVG-19960 (planned for next week) – we discovered in EVG-19859 that projects that generate an extreme number of tasks (specifically we tested 50,000 tasks) can break the UI. If the work you have here is likely to generate many more tasks we'd suggest that you wait until this work is done to verify that patch pages are still possible. This week we're going to estimate our limit for tasks in EVG-19965 which should give us a better understanding. |