Open vsajip opened 1 year ago
Now I was in the 3.11 branch so I'm not sure it should be doing a git checkout main
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 git config --local --remove-section cherry-picker
.
I did
git config --local --remove-section cherry-picker
and tried again, but now I get
Not sure about this last traceback though. Maybe just network issues or GitHub being down? It seems you were eventually able to create the PR -- did the same command succeed when you ran it a second time?
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 git config --local --remove-section cherry-picker
. Perhaps miss-islington should clean up after herself in case of failure, even though the current design might be intentional in case people want to complete the backport and/or clean up things manually.
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 get