-
Notifications
You must be signed in to change notification settings - Fork 867
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
pin python 3.12 in CI and requires-python
#4102
pin python 3.12 in CI and requires-python
#4102
Conversation
The last set of tests never started. Thus, we are stuck here. Any thoughts, @DanielYang59 ? |
I don't know the exact reason, but my guess is the unstarted set is the cached set for our current config (python > 3.10 for Ubuntu). As the finished number of tests is exactly what we asked I didn't find any related reports in GitHub Community so I might open one later, https://github.com/orgs/community/discussions/141301 |
Head branch was pushed to by a user without write access
requires-python
@DanielYang59 @JaGeo I think that the branch protection rules require a check under the name |
@ab5424 Bravo! you are the savior.
I don't have write access to the repo, but sounds like the branch protection rules are dynamically generated based the test matrix config from the master branch?
Maintainers should be able to do a manual (force) merge not using auto-merge? @shyuep |
For some reason I'm still seeing "ghost" expected checks from other PR where the config should have been updated on master branch, perhaps the branch protection rule is hard coding to expect |
Summary