Sat Apr 15 23:09:49 2006
Ticket #41 (Closed: fixed)
profiler plugin is broken
| Priority: | normal | Reporter: | jpellerin |
|---|---|---|---|
| Severity: | normal | Assigned to: | jpellerin |
| Component: | nose:plugin:profile | Status: | closed |
| Version: | 0.9 | Resolution: | fixed |
| Milestone: | 0.9a1 | Keywords: | defect |
Description by jpellerin:
Trying to run with profiler enabled results in errors from the hotshot stats loader:
Could not identify fileId 10
Could not identify fileId 10
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/hotshot/stats.py", line 12, in load
return StatsLoader(filename).load()
File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/hotshot/stats.py", line 29, in load
for event in log:
File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/hotshot/log.py", line 120, in next
filename = self._filemap[fileno]
KeyError: 91
Changelog
Sun Apr 16 00:04:06 2006: Modified by jpellerin
Sun Apr 16 00:04:13 2006: Modified by jpellerin
- status changed from new to assigned
Sun Apr 16 13:00:57 2006: Modified by jpellerin
- resolution set to fixed
- status changed from assigned to closed
Fixed in [23]. test_core.py was calling begin() on plugins again. Boom!

It seems that some particular test case in the unit test suite is breaking the profiler, since it produces good logs for some single test cases.