-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Querying, Testing Infrastructure
-
Fully Compatible
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Lines like this one currently exclude profiling tests from the sharded passthroughs:
sharded_collections_jscore_passthrough.yml
Unable to find source-code formatter for language: yml. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
- jstests/core/profile*.js # profiling.
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.