Test system says "Too mant positional arguments"

Bug #122260 reported by Matthew Paul Thomas
4
Affects Status Importance Assigned to Milestone
BlueBream
New
Undecided
Unassigned
Launchpad itself
Won't Fix
Medium
Unassigned
Zope 3
Won't Fix
Undecided
Unassigned
zope.testing
Fix Released
Medium
Unassigned

Bug Description

1. ./test.py -fp canonical product 2>&1 | less

What should happen: All the tests in product/ are run.
What actually happens:
------------
Traceback (most recent call last):
  File "./test.py", line 140, in ?
    result = testrunner.run(defaults)
  File "/home/mpt/hacking/lpsrc/2007-03-bug-page/lib/zope/testing/testrunner.py"
, line 238, in run
    failed = not run_with_options(options)
  File "/home/mpt/hacking/lpsrc/2007-03-bug-page/lib/zope/testing/testrunner.py"
, line 406, in run_with_options
    ran += resume_tests(options, layer_name, failures, errors)
  File "/home/mpt/hacking/lpsrc/2007-03-bug-page/lib/zope/testing/testrunner.py"
, line 606, in resume_tests
    raise SubprocessError(line+suberr.read())
zope.testing.testrunner.SubprocessError: usage: Usage: test.py [options] [MODULE
] [TEST]

test.py: error: Too mant positional arguments
------------

I think that's supposed to be "Too many".

description: updated
Changed in launchpad:
status: New → Confirmed
Revision history for this message
Christian Reis (kiko) wrote :

Stub says on-list:

> As the error says, there are Too mant (sic) positional arguments. This works:
> ./test.py -fvvv canonical --test=bug.txt
>
> This is a bug upstream in z3 I think. I tried dropping in current svn
> testrunner, but we get a different error instead. The typo has been fixed
> though :)

Changed in launchpad:
importance: Undecided → Low
Revision history for this message
Christian Reis (kiko) wrote : Re: [Bug 122260] Re: Test system says "Too mant positional arguments"

While not high, this is definitely a pretty ugly wart, and confusing to
newcomers.

Changed in launchpad:
importance: Low → Medium
Tres Seaver (tseaver)
Changed in zope3:
status: New → Won't Fix
Revision history for this message
Tres Seaver (tseaver) wrote :

I cannot reproduce this with the current testrunner:

 $ svn co svn://svn.zope.org/repos/main/zope.testrunner/trunk runner
 $ cd runner
 $ /opt/Python-2.6.5/bin/python bootstrap.py
 ...
 $ bin/buildout
 ...
 $ bin/test -fp zope sometest 2>&1
 Total: 0 tests, 0 failures, 0 errors in 0.000 seconds.

Can you provide info about the version of zope.testing where
you observed the bug?

Changed in zope.testing:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

No I can't, sorry, because I am no longer a Launchpad developer and therefore no longer use Zope.

Why can't you just grep the zope.testing source code for the string "mant positional"?

Changed in zope.testing:
status: Incomplete → New
Revision history for this message
Matthew Paul Thomas (mpt) wrote :
Revision history for this message
Tres Seaver (tseaver) wrote :

That string is not present in either zope.testing or zope.testrunner trunks:

 $ cd projects/Zope/Z3/ztk/src/zope.testing/
 $ find . -name "*.py" | xargs grep "mant pos"
 $ cd ../zope.testrunner/
 $ find . -name "*.py" | xargs grep "mant pos"

and hasn't been for art least two years.

Changed in zope.testing:
status: New → Fix Released
Revision history for this message
Robert Collins (lifeless) wrote :

We're looking to migrate away from having a custom testrunner, so there's no point putting effort into this [minor] wart.

Changed in launchpad-foundations:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.