How are you managing Cl costs with very large test suites?

A developer is seeking advice on managing high CI costs associated with extensive test suites, which include play-write/Chromium testing and screenshotting every page for visual inspection by ChatGPT. These tests accumulate to 60 minutes per PR, resulting in approximately 200k runner-minutes/month. Despite moving some workloads from GitHub-hosted runners, the costs remain substantial. The developer is exploring solutions like self-hosting, ephemeral runners, reducing the test matrix, or running expensive suites only after merging to control expenses.

This post uniquely details a developer's struggle with CI costs reaching 200k runner-minutes/month, specifically due to using ChatGPT for visual inspection of every page, unlike typical test suite cost discussions.