Re: [Zope-CMF] cmf-tests - OK: 3, UNKNOWN: 1

2011-08-07 Thread Jens Vagelpohl

On Aug 7, 2011, at 07:00 , CMF tests summarizer wrote:
 
 [1]UNKNOWN FAILED (failures=3, errors=4) : CMF-trunk Zope-trunk 
 Python-2.6.6 : Linux
   https://mail.zope.org/pipermail/cmf-tests/2011-August/015089.html

I have tried to pinpoint the reason for some of these test failures. Two of 
these tests are for the CMF Discussions functionality:

Failure in test test_deleteReplies 
(Products.CMFDefault.tests.test_Discussions.DiscussionTests)
Traceback (most recent call last):
  File /usr/local/lib/python2.6/unittest.py, line 279, in run
testMethod()
  File 
/usr/local/py26/cmf_trunk/src/Products.CMFDefault/Products/CMFDefault/tests/test_Discussions.py,
 line 301, in test_deleteReplies
self.assertEqual(len(ctool), 4)
  File /usr/local/lib/python2.6/unittest.py, line 350, in failUnlessEqual
(msg or '%r != %r' % (first, second))
AssertionError: 6 != 4

Failure in test test_itemCataloguing 
(Products.CMFDefault.tests.test_Discussions.DiscussionTests)
Traceback (most recent call last):
  File /usr/local/lib/python2.6/unittest.py, line 279, in run
testMethod()
  File 
/usr/local/py26/cmf_trunk/src/Products.CMFDefault/Products/CMFDefault/tests/test_Discussions.py,
 line 212, in test_itemCataloguing
% reply.getId()))
  File /usr/local/lib/python2.6/unittest.py, line 325, in failUnless
if not expr: raise self.failureException, msg
AssertionError

Those tests started failing after the following Zope-checkin:

http://svn.zope.org/?rev=122213view=rev

What ends up happening in both cases is discussion replies ending up with a 
wrong idea about their physical path. Normally, they all should have a physical 
path that points to the talkback discussion container object attached to the 
original content item that houses the discussion, like so:

/path/to/content/talkback/12345
/path/to/content/talkback/12346
/path/to/content/talkback/12347
…

All of a sudden a reply to a reply thinks it is stored not in the content 
object's talkback, but in a new talkback attached to the reply the user has 
replied to:

/path/to/content/talkback/12345
/path/to/content/talkback/12345/talkback/12346
/path/to/content/talkback/12345/talkback/12346/talkback/12347

The problem appears in CMFDefault.DiscussionItem.createReply on line 251, where 
the newly created discussion reply is aqcuisition-wrapped in the talkback 
object:

item = DiscussionItem( id, title=title, description=title )
self._container[id] = item
item = item.__of__(self)

After the wrapping, the discussion item has the wrong path. Even though self, 
the talkback object, has the correct path when calling getPhysicalPath on it. 
I can't see anything overly stupid in the DiscussionItem code, so there has to 
be an issue with that Zope getPhysicalPath change. Reverting that one change in 
the current Zope trunk fixes the tests.

jens


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] cmf-tests - OK: 3, UNKNOWN: 1

2011-08-07 Thread Hanno Schlichting
On Sun, Aug 7, 2011 at 8:25 PM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
 Hanno, have you got any stats on the optimisation? I looked briefly at the
 changes and I'm not sure if this is really worth it.

Nikolay is working on this and some more evil looking patches at
https://github.com/fafhrd91/experimental.performance

These fixes combined currently result in almost a 50% speedup in
rendering time and cut down the number of function calls
significantly.

Just one example he shared with me for rendering the edit screen of a
page in Plone (req/s, function calls):

Stock Plone 4.2:

~5.5, 17, /Plone/front-page/edit (manager)

With Chameleon:

~7.8, 101000, /Plone/front-page/edit (manager)

With evil looking optimizations:

~12.3,  43000, /Plone/front-page/edit (manager)

So yes, while these changes look at bit evil, they do have a major impact.

Hanno
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


Re: [Zope-CMF] cmf-tests - OK: 3, UNKNOWN: 1

2011-08-07 Thread Charlie Clark
Am 07.08.2011, 20:45 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:

 So yes, while these changes look at bit evil, they do have a major  
 impact.

Quite a speed-up! Unfortunately, as Jens has pointed out, it breaks  
DiscussionItem in a non-obvious way.

Charlie
-- 
Charlie Clark
Managing Director
Clark Consulting  Research
German Office
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226
___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests


[Zope-CMF] cmf-tests - OK: 3, UNKNOWN: 1

2011-08-07 Thread CMF tests summarizer
This is the summary for test reports received on the 
cmf-tests list between 2011-08-06 00:00:00 UTC and 2011-08-07 00:00:00 UTC:

See the footnotes for test reports of unsuccessful builds.

An up-to date view of the builders is also available in our 
buildbot documentation: 
http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds

Reports received


   CMF-2.2 Zope-2.12 Python-2.6.6 : Linux
   CMF-2.2 Zope-2.13 Python-2.6.6 : Linux
   CMF-trunk Zope-2.13 Python-2.6.6 : Linux
[1]FAILED (failures=3, errors=4) : CMF-trunk Zope-trunk Python-2.6.6 : Linux

Non-OK results
--

[1]UNKNOWN FAILED (failures=3, errors=4) : CMF-trunk Zope-trunk 
Python-2.6.6 : Linux
   https://mail.zope.org/pipermail/cmf-tests/2011-August/015093.html


___
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests