[Python-Dev] Getting information out of the buildbots
I committed some new telnetlib tests yesterday to the trunk and I can see they are failing on Neal's setup but not what the failures are. Ideally I like to get the information out of the buildbots but they all seem to be hanging on stdio tests and quiting out. Ideas? TIA, -Jack ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Getting information out of the buildbots
Jack diederich jackdied at gmail.com writes: I committed some new telnetlib tests yesterday to the trunk and I can see they are failing on Neal's setup but not what the failures are. Ideally I like to get the information out of the buildbots but they all seem to be hanging on stdio tests and quiting out. You can commit some temporary debug output in the tests (just sprinkle those print()'s you need to get your tasty information). Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Getting information out of the buildbots
You can commit some temporary debug output in the tests (just sprinkle those print()'s you need to get your tasty information). Also, if you want to do a sequence of changes to test a specific machine, you might want to create a branch, make those changes, and then trigger a build of that branch just on that specific slave (use branches/name in the input field). When doing so, feel free to cancel any automated build that is currently running; make sure to use your real name in the UI so we know it's not spam. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
