Broken miss-inlington

Core Workflow
1

On my PR https://github.com/python/cpython/pull/12236 miss-inlington announced that it will try to backport my change, but then nothing. It seems like the bot is broken.

I will backport my change manually, as I did yesterday for another change.

cc @Mariatta @EWDurbin

2

Thanks. I’ve reverted the latest release of cherry-picker for now until I have time to investigate. Please file a bug in miss-islington repo.

3

It is still broken: https://github.com/python/cpython/pull/12383#issuecomment-473846779 the bot is working for 14 minute to create a backport, whereas previously it took less than 5 minutes (usually less than 1 minute).

4

Done Broken bot on https://github.com/python/cpython/ · Issue #219 · python/miss-islington · GitHub

5

@Mariatta FTR bot slowness reported by @vstinner may be related to having more synchronous subprocess calls in cherry-picker. The next step in its refactoring would probably be to make it all async. It’s because miss-Islington is asynchronous and more blocking calls freeze it more…