GitHub mystery: "Check for source changes (pull_request)" failed
New one to me!
The new
https://github.com/python/cpython/pull/30555
is dead in the water, with a "Check for source changes (pull_request)" failure.
Afraid to say I don't even know what that's trying to check.
The details show this at the end:
Error: Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_e6eccc97-eabe-4596-b4b2-6ea2f8c672cb/8fca955b-16e0-4c1b-81a8-38d568264bd6.tar.gz. return code: 2.
Clues? It's a simple PR, making a few changes to just one C file.
Bizarre. "Check for source changes (pull_request)" apparently fixed itself by magic. Now "Check if generated files are up to date (pull_request)" is failing instead, in a similar way ("Can't use 'tar -xzf' extract archive file"). Nope! No idea here what that's trying to check either ;-)
On Tue, Jan 11, 2022 at 8:57 PM Tim Peters <tim.peters@gmail.com> wrote:
New one to me!
The new
https://github.com/python/cpython/pull/30555
is dead in the water, with a "Check for source changes (pull_request)" failure.
Afraid to say I don't even know what that's trying to check.
The details show this at the end:
Error: Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_e6eccc97-eabe-4596-b4b2-6ea2f8c672cb/8fca955b-16e0-4c1b-81a8-38d568264bd6.tar.gz. return code: 2.
Clues? It's a simple PR, making a few changes to just one C file.
It seems to an incident of GitHub. https://www.githubstatus.com/incidents/cypv026dr23w?utm_ts=1641954539
On Wed, Jan 12, 2022 at 12:24 PM Tim Peters <tim.peters@gmail.com> wrote:
Bizarre. "Check for source changes (pull_request)" apparently fixed itself by magic. Now "Check if generated files are up to date (pull_request)" is failing instead, in a similar way ("Can't use 'tar -xzf' extract archive file"). Nope! No idea here what that's trying to check either ;-)
On Tue, Jan 11, 2022 at 8:57 PM Tim Peters <tim.peters@gmail.com> wrote:
New one to me!
The new
https://github.com/python/cpython/pull/30555
is dead in the water, with a "Check for source changes (pull_request)" failure.
Afraid to say I don't even know what that's trying to check.
The details show this at the end:
Error: Can't use 'tar -xzf' extract archive file: /home/runner/work/_actions/_temp_e6eccc97-eabe-4596-b4b2-6ea2f8c672cb/8fca955b-16e0-4c1b-81a8-38d568264bd6.tar.gz. return code: 2.
Clues? It's a simple PR, making a few changes to just one C file.
python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/H... Code of Conduct: https://www.python.org/psf/codeofconduct/
-- Inada Naoki <songofacandy@gmail.com>
Hello,
Le 11/01/2022 à 22:23, Tim Peters a écrit :
Bizarre. "Check for source changes (pull_request)" apparently fixed itself by magic.
That was me! 🧙 I re-ran the workflow to see if it was a sporadic failure.
Now "Check if generated files are up to date (pull_request)" is failing instead
Then I saw that and looked at the github status website, which indicated an issue. Patience is the remedy!
Cheers
[Tim]
Bizarre. "Check for source changes (pull_request)" apparently fixed itself by magic.
[Éric Araujo <merwok@netwok.org>]
That was me! 🧙 I re-ran the workflow to see if it was a sporadic failure.
Cool! No more or less mysterious to me than if you hadn't ;-)
Now "Check if generated files are up to date (pull_request)" is failing instead
Then I saw that and looked at the github status website, which indicated an issue. Patience is the remedy!
Too late! It passes now :-) After waiting a couple hours, I poked around until finding a button that made it try that part again. This time it passed.
But somehow I managed to convince it run nearly 70 different jobs A mystery I will happily leave uninvestigated.
Thanks for chipping in!
The 70 different jobs were presumably the full complement of buildbots (requested by setting a special label on the PR, which one of our GitHub bots watches).
On Tue, Jan 11, 2022 at 9:22 PM Tim Peters <tim.peters@gmail.com> wrote:
[Tim]
Bizarre. "Check for source changes (pull_request)" apparently fixed itself by magic.
[Éric Araujo <merwok@netwok.org>]
That was me! 🧙 I re-ran the workflow to see if it was a sporadic failure.
Cool! No more or less mysterious to me than if you hadn't ;-)
Now "Check if generated files are up to date (pull_request)" is failing instead
Then I saw that and looked at the github status website, which indicated an issue. Patience is the remedy!
Too late! It passes now :-) After waiting a couple hours, I poked around until finding a button that made it try that part again. This time it passed.
But somehow I managed to convince it run nearly 70 different jobs A mystery I will happily leave uninvestigated.
Thanks for chipping in!
python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-leave@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/J... Code of Conduct: https://www.python.org/psf/codeofconduct/
-- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
participants (4)
-
Guido van Rossum -
Inada Naoki -
Tim Peters -
Éric Araujo