They were using "not enough resources" to support the idea of blacklisting. If they meant it as you say, that means they're blanketly blacklisting the most common config despite having the resources to test it, which is even worse.
The common distribution was blacklisted not because it was not tested, but because it clearly has issues observed and reported by the users.
If a driver does not work in popular configs, and needs to be blacklisted in those configs, your solution is to still whitelist it in other configs and have the browser likely not work.
yes, "every company" does exactly what google did. you are being purposely dense, trying to catch a "technically correct" chance of not admitting the stupidity of your question. The problem is, you are not even technically correct - just purposely dense.
And the test suite failed on a minor issue where the cause was uncertain, which gets in the way of checking for the bigger definitely-the-driver problem.