@shonfeder mentioned that the rev-deps bisect GitHub action by @Alizter has been useful to identify when regressions were introduced in a new release.
In a similar vein, it would be useful to have a GitHub Actions job (perhaps integrated with the same job, I haven't looked into the ergonomics of this yet) to bisect a cram test to identify when it started failing.
@shonfeder mentioned that the rev-deps bisect GitHub action by @Alizter has been useful to identify when regressions were introduced in a new release.
In a similar vein, it would be useful to have a GitHub Actions job (perhaps integrated with the same job, I haven't looked into the ergonomics of this yet) to bisect a cram test to identify when it started failing.