remove_stale_bytecode stops test run, if unlink fails

Bug #257515 reported by Michael Howitz on 2008-08-13
2
Affects Status Importance Assigned to Milestone
zope.testing
Undecided
Unassigned
zope.testrunner
Undecided
Unassigned

Bug Description

When trying to remove stale bytecode files the developer is not allowed to the test run stops with the following traceback.

Removing stale bytecode file /home/zope/local/lib/python2.4/site-packages.org/_xmlplus/FtCore.pyc
Traceback (most recent call last):
...
  File ".../zope/testing/testrunner.py", line 932, in run
    failed = not run_with_options(options)
  File ".../zope/testing/testrunner.py", line 1038, in run_with_options
    remove_stale_bytecode(options)
  File ".../zope/testing/testrunner.py", line 1812, in remove_stale_bytecode
    os.unlink(fullname)
OSError: [Errno 13] Permission denied: '/home/zope/local/lib/python2.4/site-packages.org/_xmlplus/FtCore.pyc'

It would be helpful to have an option to produce a warning instead.

Marius Gedminas (mgedmin) wrote :

This needs to be fixed in zope.testrunner, not zope.testing.

Changed in zope.testing:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers