Heads up: possible double-comments on bpo for commits
I've activated the webhook for receiving comments on issues when a commit lands mentioning an issue, so if you see a commit from our hg integration and another from GitHub, understand that's why (mention issues as "bpo NNNN" in commit messages if you want to see it in action). If it becomes too much of a hassle to see the duplicates before we migrate I can turn off the notifications, but obviously more testing the better. :)
Hi, I noticed a strange issue with Roundup Robot on the issue #29318. I closed http://bugs.python.org/issue29318 as rejected: resolution: -> rejected status: open -> closed Roundup Robot made a first change: stage: -> resolved But then it made a second change: resolution: rejected -> fixed To finish with an empty change: => I got an email to notify me "Changes by Roundup Robot <devnull@psf.upfronthosting.co.za>", but with no useful email body. --- 8< --- Changes by Roundup Robot <devnull@psf.upfronthosting.co.za>: _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue29318> --- 8< --- Victor
2017-02-01 18:32 GMT+01:00 Victor Stinner <victor.stinner@gmail.com>:
To finish with an empty change:
Information on IRC: Known issue: http://psf.upfronthosting.co.za/roundup/meta/issue611 "Maciej is working on it" Good & thanks! Victor
On Thu, Feb 2, 2017 at 6:01 PM, Victor Stinner <victor.stinner@gmail.com> wrote:
2017-02-01 18:32 GMT+01:00 Victor Stinner <victor.stinner@gmail.com>:
To finish with an empty change:
Information on IRC:
Known issue: http://psf.upfronthosting.co.za/roundup/meta/issue611
"Maciej is working on it"
Good & thanks!
I just fixed all the problems mentioned by Victor in this thread, this includes: 1. accidentally closing issues 2. multiple entries in history 3. empty date for gh commit messages (path by Berker - thank you) Ezio confirmed pushing all the changes to bugs.python.org already. I'm very sorry for all the inconvenience caused by previous mistakes. If your issues was closed make sure to verify it was closed properly and re-open if needed. Maciej
2017-02-02 22:24 GMT+01:00 Maciej Szulik <soltysh@gmail.com>:
Ezio confirmed pushing all the changes to bugs.python.org already. I'm very sorry for all the inconvenience caused by previous mistakes. If your issues was closed make sure to verify it was closed properly and re-open if needed.
Don't worry. Brett warned us and it was quickly fixed. Thanks! Victor
Oh, I noticed another strange thing: The Roundup Robot closed the issue http://bugs.python.org/issue29368 but I don't see any explicit "Close issue #xxx" or "Close #xxx" in the commit message of the two commits. Is it deliberate to close an issue after any commit? Victor 2017-01-31 19:18 GMT+01:00 Brett Cannon <brett@python.org>:
I've activated the webhook for receiving comments on issues when a commit lands mentioning an issue, so if you see a commit from our hg integration and another from GitHub, understand that's why (mention issues as "bpo NNNN" in commit messages if you want to see it in action). If it becomes too much of a hassle to see the duplicates before we migrate I can turn off the notifications, but obviously more testing the better. :)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/victor.stinner%40gmail.co...
participants (3)
-
Brett Cannon -
Maciej Szulik -
Victor Stinner