This is an idea that Travis has but CircleCI does not. With Travis, I can tell the system that the failure of certain jobs should not cause the whole run to be considered a failure. See https://docs.travis-ci.com/user/customizing-the-build/#rows-that-are-allowed-to-fail for details.

The equivalent for CircleCI would be an "allow_failure" key on each job.

My particular use case is testing Perl libraries with many versions of Perl. I'd like to test them against the latest git HEAD of the perl core, but this may fail for reasons outside of my control. I'd like to investigate failures, but they shouldn't block merging of a PR for my library.

CCI-I-1204