Config publisher-profile-file doesnt work

Bug #143915 reported by Hans-Juergen Sell
2
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Low
Unassigned

Bug Description

In Issue 1036 of Zope Bugs, Features, and Patches Collector [ZC] it was described that due to a bug the profiler configuration will not work. Does this mean that with this Zope version a profiling is not possible, or can it be done otherwise?

Tags: bug zope
Revision history for this message
Andreas Jung (ajung) wrote :

Due to which bug?

Revision history for this message
Hans-Juergen Sell (hsell) wrote :

I don't know. This was my conclusion from Issue 1036 of Zope Bugs, Features, and Patches Collector [ZC].

Revision history for this message
Martijn Pieters (mjpieters) wrote :

1036 was resolved, so the profiler should work fine. Did you stop and start zope again with the zopectl controller, or from the Control Panel? The latter doesn't cause the relevant configuration to be re-read, I believe.

Revision history for this message
Martijn Pieters (mjpieters) wrote :

I ran into a problem with the profiler myself, there is indeed a bug, at least in the 2.9 branch I used. The profiler does work, but never saves the profiler data; sys._pr_ never is set to None.

See ZPublisher/Publish.py, publish_module_profiled

Changed in zope2:
importance: Medium → Low
status: New → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.

Changed in zope2:
status: Confirmed → Invalid
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.