-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ci] CI canary [WIP/RFC] #1692
[ci] CI canary [WIP/RFC] #1692
Conversation
Codecov ReportPatch has no changes to coverable lines. ❗ Your organization needs to install the Codecov GitHub app to enable full functionality. 📢 Thoughts on this report? Let us know!. |
c8c1982
to
dae76aa
Compare
This is progress: 9a08fcc Before: a CI error involving
where the symbol demangles to
-- note the placement of the |
0fcbf34
to
0b11d5d
Compare
Superseded by #1695 |
Internal-only/debug-only canary to examine CI issues arising simultaneously with #1691, while apparently not caused by #1691.
Our post-merge CI has fail-fast set to false -- run all tests to completion -- while our pre-merge CI has fail-fast set to true. This is, generally, a good idea as a large chunk of our CI compute resources are absorbed by pre-merge CI. However, on #1691 I want to see if the Python 3.7 fail there is related only to 3.7. As is on #1691, with fail-fast set to true, the 3.7 fail is cancelling signal from the other CI jobs.
Parent context: #866.