Edgewall Software
Modify

Ticket #4026 (closed defect: duplicate)

Opened 5 years ago

Last modified 4 years ago

`generator ignored GeneratorExit` in Wiki formatting unit tests

Reported by: cboos Owned by: jonas
Priority: low Milestone:
Component: wiki system Version: 0.10
Severity: minor Keywords:
Cc:
Release Notes:
API Changes:

Description

In case someone runs the tests on trunk and wonders from where the generator ignored GeneratorExit exception are coming from:

$ PYTHONPATH=".;$PYTHONPATH" python trac/wiki/tests/formatter.py
.......................................................Exception exceptions.RuntimeError: 'generator ignored GeneratorExit' in <generator object at 0x02C2DAD0> ignored
..Exception exceptions.RuntimeError: 'generator ignored GeneratorExit' in <generator object at 0x02C362D8> ignored
....Exception exceptions.RuntimeError: 'generator ignored GeneratorExit' in generator object at 0x02C36DC8> ignored
..Exception exceptions.RuntimeError: 'generator ignored GeneratorExit' in <generator object at 0x02C372B0> ignored
Exception exceptions.RuntimeError: 'generator ignored GeneratorExit' in <generator object at 0x02C36F08> ignored
.............................................................................
----------------------------------------------------------------------
Ran 140 tests in 0.203s

OK

... so those exceptions are somehow related to the wiki formatting and to Python 2.5 of course, as I don't have those exceptions using 2.4 (on Windows).

It might be due to svn not being available, I'll check.

Attachments

Change History

comment:1 Changed 4 years ago by Rudolph

I got this exception in production use (Trac 0.10.4) running with Tracd or Fastcgi (didn't test under mod_python). With Fastcgi (under lighttpd) it results in lighttpd raising a 500 error (when using tracd you can see the page renders okay). I use all default packages from Ubuntu Gutsy (Python 2.5) and use PostgreSQL as DB backend. It only happens on some wiki pages (TracWiki being one of them).

comment:2 Changed 4 years ago by osimons

  • Milestone 0.11.1 deleted
  • Resolution set to duplicate
  • Status changed from new to closed

It does seem like this is the same issue as #5339.

As that ticket progressed quite far in trying to detect the problem (including patch), I'm closing this older ticket as a duplicate.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
to The owner will be changed from jonas. Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.