[SERVER-38167] Use 'requires_profiling' tag to exclude profile tests from core passthroughs Created: 15/Nov/18 Updated: 29/Oct/23 Resolved: 30/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Arun Banala |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | greenerbuild | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
Lines like this one currently exclude profiling tests from the sharded passthroughs:
We added the 'requires_profiling' tag at some point, it looks like it was used for the mobile build variants. I suggest we update the suites to exclude based on the tag rather than based on the name. We should then exclude this tag from other sharded suites, such as aggregation_mongos_passthrough. That should help us avoid causing failures and trouble by moving tests around and by naming the test something without 'profile', such as this other one. |
| Comments |
| Comment by Githook User [ 30/Sep/19 ] |
|
Author: {'name': 'Arun Banala', 'username': 'banarun', 'email': 'arun.banala@10gen.com'}Message: |