> 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 bran
Jack diederich 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 quiti
