[SERVER-55375] Add a "burnin" type evergreen task that allows us to run relevant fuzzers repeatedly Created: 19/Mar/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sam Mercier | Assignee: | Backlog - Query Optimization |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | greenerbuild | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Optimization
|
||||||||
| Participants: | |||||||||
| Description |
|
It would be helpful to the query team to have an evergreen task that we can optionally run which would allow us to repeatedly generate query/agg/update fuzzer tasks in the way that the burnin evergreen task does for other types of tests. This would give us a way of quickly and thoroughly testing for low probability bugs that the fuzzer may catch on patches that we believe may cause fuzzer failures. This would also be very helpful for us when backporting query changes because the fuzzer runs infrequently on old release branches. Relevant example: https://github.com/mongodb/mongo/blob/4e410825f29880ff9502d41e3874b9ec8cef49cd/etc/evergreen.yml#L4340-L4352 |
| Comments |
| Comment by Sam Mercier [ 25/Mar/21 ] |
|
One could model this after this evergreen stage. There are two options for how to make this an "optional" task. One is to add the patch_only flag like this and the other is to set the `batchtime` to something large such that it runs every 10 years in the waterfall. |