[PEAK] Trellis: undetected circularity via optional rules

Sergey Schetinin maluke at gmail.com
Thu Apr 16 20:04:26 EDT 2009

On Fri, Apr 17, 2009 at 02:59, P.J. Eby <pje at telecommunity.com> wrote:
> At 02:48 AM 4/17/2009 +0300, Sergey Schetinin wrote:
>> I wanted to attach a test log but the test suite output somehow routes
>> around >, >> and |.
> Hm.  I use:
> python setup.py test 2>&1|less

That works better, thanks.

Also the log I submitted for some reason says "/checkouts/trellis" in
test paths which is the working copy, I'm sure I ran tests from
"/checkouts/copy of trellis" which is a clean checkout. I've renamed
the working copy so it's not on pythonpath, and now tests don't
mention it, yet all the errors are in place.

>> I might be inept with console but when I tried the
>> stupid approach: setting console lines limit to 1000 and just
>> copy-paste the output, I discovered that running the test messes with
>> it and resets the console size so it's not big enough to capture the
>> output. Nice.
>> Anyway, I managed to capture the output with SciTE:
>> http://pastebin.com/pastebin.php?dl=m7ca82e2f
>> That's vanilla checkout with some tests disabled
>> (test_trellis.TestReactorEventLoop.testSequentialCalls,
>> test_trellis.TestWxEventLoop.testSequentialCalls,
>> test_trellis.TestTasks.testNoTodoRollbackIntoTask).
> What platform is this on, and what version of Python?

WinXP SP3, Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC
v.1310 32 bit (Intel)] on win32

More information about the PEAK mailing list