Hi all,
Just got this output from pushing a commit:
""" pushing to ssh://hg@hg.python.org/cpython searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 1 changes to 1 files remote: buildbot: change(s) NOT sent, something went wrong: remote: buildbot: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectError'>: An error occurred while connecting: 113: No route to host. remote: buildbot: ] remote: sent email to roundup at report@bugs.python.org remote: notified python-checkins@python.org of incoming changeset c964b6b83720 """
Trying to load buildbot.python.org timed out as well. Has the fleet sailed away?
-- Zach
On 06.02.2014 22:52, Zachary Ware wrote:
Hi all,
Just got this output from pushing a commit:
""" pushing to ssh://hg@hg.python.org/cpython searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 1 changes to 1 files remote: buildbot: change(s) NOT sent, something went wrong: remote: buildbot: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectError'>: An error occurred while connecting: 113: No route to host. remote: buildbot: ] remote: sent email to roundup at report@bugs.python.org remote: notified python-checkins@python.org of incoming changeset c964b6b83720 """
Trying to load buildbot.python.org timed out as well. Has the fleet sailed away?
Probably just a temporary network/DNS failure. It seems to work fine now.
On ven., 2014-02-07 at 09:55 +0100, M.-A. Lemburg wrote:
Trying to load buildbot.python.org timed out as well. Has the fleet sailed away?
Probably just a temporary network/DNS failure. It seems to work fine now.
According to infrastructure, there had been a kernel panic. The VM has been restarted.
Regards
Antoine.
participants (3)
-
Antoine Pitrou -
M.-A. Lemburg -
Zachary Ware