-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Unexpected run state encountered #65
Comments
It looks like it successfully backported your PR, and while cleaning up and switching back to main (which is expected at this stage) an error occurred. That left miss-islington in an inconsistent state that you fixed with
Not sure about this last traceback though. Maybe just network issues or GitHub being down? |
Yes, it did - perhaps it was a transient network issue. GitHub seemed generally fine - I was able to monitor the tests, close the issue once they completed etc. I just logged this issue to help fix whatever caused the inconsistent state to occur. You can close it if you don't need it for that purpose. |
I ran into errors in the past that required a |
When trying to backport this PR, miss-islington failed and advised running
cherry_picker
from the CLI. When runningcherry_picker 067597522a9002f3b8aff7f46033f10acb2381e4 3.11
It failed with this traceback:
Now I was in the 3.11 branch so I'm not sure it should be doing a
git checkout main
. But anyway, the PR was created (in that it opened the "Create pull request" page in the browser, which I clicked to confirm - the PR is here. But if I now try to do the same thing for 3.10, I getI did
git config --local --remove-section cherry-picker
and tried again, but now I getThe text was updated successfully, but these errors were encountered: