is_ci_environment is recent-ish and I trust it was implemented for a good reason, but it still isnt a good pattern long-term. This is a placeholder issue to track down the places where it is used and try to make it unnecessary. e.g. if a test uses more RAM than is available on the CI, a better check might be specifically for low-ram environments.