On Mon, Apr 27, 2009 at 08:44:42PM -0700, Christopher Lee wrote:
-> On Apr 26, 2009, at 12:01 PM, C. Titus Brown wrote:
-> 
-> > The following branches should be considered for merge into master:
-> >
-> > runtest_single  (author ctb, reviewed by ialbert)
-> > cleanflag       (author ialbert, reviewed by ctb)
-> > review_issue40  (author ctb, fixes obvious bugs -> leec)
-> > nicer-error     (author ialbert, reviewed by ctb)
-> 
-> I pushed cleanflag to master.

ok!

-> I am playing with runtest_single; not sure why, but XMLRPC tests are  
-> failing on Python 2.3 on linux -- annoying permission error?  I'll  
-> investigate this more.  Also I don't yet understand how SkipTest are  
-> handled on platforms lacking nose... and sqltable_test.py still has  
-> its get_suite()?  Thought SkipTest was supposed to supercede that.

Huh.  I thought I'd tested it on python2.3... very annoying.  On my 2.3
install, I sometimes see that the XML-RPC server is running on one port
but the connection attempt is to another port.  Perhaps in 2.3 ports
aren't relinquished so easily and so you get clashes if you use a single
port??  Dunno why this would show up now!  Ahh, the test running order
may have changed slightly.  Interesting.

Merging in the xmlrpc_random_port branch actually fixes this problem,
implying that port release is, indeed, the issue.  Hmm.

The sqltable_test having a get_suite is an oversight.  We should axe it.

See testlib/unittest_extensions.py, method addError, for the skip
functionality.

-> I'm working on review_issue40.

great!

-> Haven't looked at nicer-error yet...

ok.

--titus
-- 
C. Titus Brown, c...@msu.edu

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pygr-dev" group.
To post to this group, send email to pygr-dev@googlegroups.com
To unsubscribe from this group, send email to 
pygr-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to