"bedevere/news — News entry file name incorrectly formatted"
Hello,
The NEWS file check failed in a weird way here: https://github.com/python/cpython/pull/11531
Could someone take a look and find out the reason for failure?
Thanks
Antoine.
On Jan 21, 2019, at 14:44, Antoine Pitrou <antoine@python.org> wrote:
The NEWS file check failed in a weird way here: https://github.com/python/cpython/pull/11531
Could someone take a look and find out the reason for failure?
I'm mystified. The blurb news file in the PR looks fine and produces a valid changelog with a local docs build. I don't see anything odd on the GitHub end of things. Perhaps Mariatta can take a look at the Bevedere end?
-- Ned Deily nad@python.org -- []
A potential explanation: the original PR title was formatted as "bpo-XXXXXX : ..." (note the space before the colon). I fixed it to "bpo-XXXXX: ..." but the bot didn't run again. Perhaps that's related?
Le 21/01/2019 à 21:05, Ned Deily a écrit :
On Jan 21, 2019, at 14:44, Antoine Pitrou <antoine@python.org> wrote:
The NEWS file check failed in a weird way here: https://github.com/python/cpython/pull/11531
Could someone take a look and find out the reason for failure?
I'm mystified. The blurb news file in the PR looks fine and produces a valid changelog with a local docs build. I don't see anything odd on the GitHub end of things. Perhaps Mariatta can take a look at the Bevedere end?
-- Ned Deily nad@python.org -- []
On Jan 21, 2019, at 15:07, Antoine Pitrou <antoine@python.org> wrote:
A potential explanation: the original PR title was formatted as "bpo-XXXXXX : ..." (note the space before the colon). I fixed it to "bpo-XXXXX: ..." but the bot didn't run again. Perhaps that's related?
Possibly, if you modified the news entry while the other CI checks were still running? I guess you could force the whole CI process to run again by closing and re-opening the PR. Or a release manager could override it with an appropriate bribe.
-- Ned Deily nad@python.org -- []
Le 21/01/2019 à 21:11, Ned Deily a écrit :
On Jan 21, 2019, at 15:07, Antoine Pitrou <antoine@python.org> wrote:
A potential explanation: the original PR title was formatted as "bpo-XXXXXX : ..." (note the space before the colon). I fixed it to "bpo-XXXXX: ..." but the bot didn't run again. Perhaps that's related?
Possibly, if you modified the news entry while the other CI checks were still running? I guess you could force the whole CI process to run again by closing and re-opening the PR. Or a release manager could override it with an appropriate bribe.
Right, I forced the CI checks and things seem fine now.
Thank you!
Antoine.
participants (2)
-
Antoine Pitrou -
Ned Deily