Dealing with breaking infra changes

It’s hard for me to know if I need to act on changes that breaks CI that are submitted to GitHub - bemanproject/timed_lock_alg: Timed lock algorithms for multiple lockables (P3832) and std::multi_lock (P3833) · GitHub which now shows CI failing on:

I don’t know if that’s because of my previous commit ( Add beman-tidy . --verbose --require-all to pre-commit hook · bemanproject/timed_lock_alg@d76e27c · GitHub ) where I aimed to enable beman-tidy . --verbose --require-all in the pre-commit hook or if it’s something else. It does look like something else to me, but, is that something going to be fixed by someone else or do I need to do something?

The specific error you linked has started happening recently and I don’t know the root cause, but I think it’s a bug in something outside the Beman project, and it’s transient. It only happens for MSVC jobs. It should go away by clicking “re-run failed jobs”:

1 Like