Skip to content

Conversation

@FFY00
Copy link
Member

@FFY00 FFY00 commented Jan 29, 2025

@AA-Turner
Copy link
Member

Is there risk of flakiness from this job? It may be worth evaluating it for a few days to get a baseline, before requiring it for merge.

@FFY00
Copy link
Member Author

FFY00 commented Jan 30, 2025

There shouldn't be, we only run a subset of tests, which exercise most of the code that is relevant on cross builds. We can wait a couple days to evaluate it, though I don't currently have the bandwidth to keep an eye on other PRs to gauge it.

@FFY00
Copy link
Member Author

FFY00 commented Feb 8, 2025

We've waited a little bit, did anyone notice unexpected failures on this job in the meantime?

Copy link
Member

@hugovk hugovk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've not seen any issues with this one, I think we're good to merge.

@FFY00 FFY00 merged commit 2a0256f into python:main Feb 13, 2025
49 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants