It looks like the changes from https://github.com/mongodb/mongo/commit/3b4b7fd820a59b794c739daa062ffac9b87d3496 made it so the tests which are tagged with fully disabled feature flags cannot be run by resmoke at all, even when they are explicitly named, and even when they are explicitly named and --force-excluded-tests is specified.

Original slack thread: https://mongodb.slack.com/archives/C0V79S1PY/p1689865913280029

relevant comments from Max:

It might be better to fix --force-excluded-tests because I think https://github.com/mongodb/mongo/commit/2dbc2a40b841eef00e2ad1b79e3f938bad889c58#diff-f2cf305d49623a1306c7130f462[…]5620a04ed9a241adbeacd1e944d15418 isn't written in a way where it can identify tests which were excluded via tags. And so anywhere the python code appends to config.EXCLUDE_WITH_ANY_TAGS means those tests can't be run without any direct indicationMy thought right now would be for suitesconfig.py to instead generate a Suite which removes all inclusions/exclusions and only lists roots from the test_files

Specifying the test_files in the include_files section in addition to the roots section would allow the include_files to take precedence over the tag exclusions. Maybe that's a way to achieve the idea I'm proposing?