Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
On Tue, May 21, 2013 at 09:45:52AM -0400, Tres Seaver wrote: > On 05/21/2013 06:28 AM, Marius Gedminas wrote: > >>> [1]Still Failing - zopetoolkit_trunk - Build # 270 > > One zope.session failure: > > > > File > > "/var/lib/jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.session/src/zope/session/http.py", > > line 442, in zope.session.http.CookieClientIdManager.setRequestId > > Failed example: expires > now + timedelta(0, 55 * 60) Expected: True > > Got: False > > Hmm, I changed that yesterday because the old test code (using > 'time.mktime') was failiing on my box, likely due to an odd mix of naive > and GMT times. The *actual* cookie being set by the code-under-test is > correct -- we just have a problem writing good assertinos about it. I can reproduce this. Looks like the error only shows up when the system timezone is east of the prime meridian (e.g. Europe/Vilnius or Europe/London -- at least during summer; the error went away with TZ set to America/New_York or UTC). Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
On Tue, May 21, 2013 at 09:45:52AM -0400, Tres Seaver wrote: > On 05/21/2013 06:28 AM, Marius Gedminas wrote: > >>> [2]winbot / ZEO_py_265_32 > > > > One failure: > > > > File "c:\buildslave\zeo\build\src\ZEO\tests\testZEO.py", line 1162, in > > ZEO.tests.testZEO.client_has_newer_data_than_server Failed example: > > len(client_errors) >= 2 Expected: True Got: False > > This is another place where I have tweaked the test code, trying to > remove race conditions: the test is trying to make assertionas about > errors being logged, and does a bunch of sleeping trying to ensure that > "enough" stuff gets logged. Again, it is a bad test, and not a real > issue with the code being tested. I couldn't reproduce this on my laptop (using detox), but I managed to get Python 3.2 tests to deadlock (40 minutes and still running, with 0% CPU usage). I see that the tests also deadlock on Travis: https://travis-ci.org/zopefoundation/ZEO/builds/7364121 (And I see that Travis doesn't currently run Python 3 tests for ZEO master. I'll fix that.) Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/21/2013 06:28 AM, Marius Gedminas wrote: >>> [1]Still Failing - zopetoolkit_trunk - Build # 270 > One zope.session failure: > > File > "/var/lib/jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.session/src/zope/session/http.py", > line 442, in zope.session.http.CookieClientIdManager.setRequestId > Failed example: expires > now + timedelta(0, 55 * 60) Expected: True > Got: False Hmm, I changed that yesterday because the old test code (using 'time.mktime') was failiing on my box, likely due to an odd mix of naive and GMT times. The *actual* cookie being set by the code-under-test is correct -- we just have a problem writing good assertinos about it. >>> [2]winbot / ZEO_py_265_32 > > One failure: > > File "c:\buildslave\zeo\build\src\ZEO\tests\testZEO.py", line 1162, in > ZEO.tests.testZEO.client_has_newer_data_than_server Failed example: > len(client_errors) >= 2 Expected: True Got: False This is another place where I have tweaked the test code, trying to remove race conditions: the test is trying to make assertionas about errors being logged, and does a bunch of sleeping trying to ensure that "enough" stuff gets logged. Again, it is a bad test, and not a real issue with the code being tested. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGbepAACgkQ+gerLs4ltQ56IACeIrEUbC/TC+Y0d+AvjVom6rID GkEAn2nNosl/7EhWpymlf2n/zcN6avi+ =ZYlR -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
On Tue, May 21, 2013 at 01:00:02AM +, Zope tests summarizer wrote: > [1]Still Failing - zopetoolkit_trunk - Build # 270 One zope.session failure: File "/var/lib/jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.session/src/zope/session/http.py", line 442, in zope.session.http.CookieClientIdManager.setRequestId Failed example: expires > now + timedelta(0, 55 * 60) Expected: True Got: False > [2]winbot / ZEO_py_265_32 One failure: File "c:\buildslave\zeo\build\src\ZEO\tests\testZEO.py", line 1162, in ZEO.tests.testZEO.client_has_newer_data_than_server Failed example: len(client_errors) >= 2 Expected: True Got: False > [3]winbot / zope.testrunner_py_265_32 Intermittent Github connection error. Last build was successful. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-05-19 00:00:00 UTC and 2013-05-20 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 [1]Still Failing - zopetoolkit_trunk - Build # 270 [2]winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [3]winbot / zope.testrunner_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 270 https://mail.zope.org/pipermail/zope-tests/2013-May/075082.html [2]FAILED winbot / ZEO_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075081.html [3]FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075080.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-04-09 00:00:00 UTC and 2013-04-10 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 [1]Still Failing - zopetoolkit_trunk - Build # 229 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 229 https://mail.zope.org/pipermail/zope-tests/2013-April/073779.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073780.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073778.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-04-08 00:00:00 UTC and 2013-04-09 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 [1]Still Failing - zopetoolkit_trunk - Build # 228 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 228 https://mail.zope.org/pipermail/zope-tests/2013-April/073764.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073765.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073763.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/06/2013 09:00 PM, Zope tests summarizer wrote: > > [1]FAILED Still Failing - zopetoolkit_trunk - Build # 225 > https://mail.zope.org/pipermail/zope-tests/2013-April/073719.html AFACT, these failures are bugs in z3c.recipe.compattest: it is generating the test scripts without full expanding the transitive depencencies of the tested packages. None of the separate buldouts fail. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFhkIIACgkQ+gerLs4ltQ7xhgCg3NkGvCxl0Qf0L4TcNFO6Ejz5 SYoAn0yl8eG53jrb9PIXcDXEZSsn93zq =se8y -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-04-05 00:00:00 UTC and 2013-04-06 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 [1]Still Failing - zopetoolkit_trunk - Build # 225 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 225 https://mail.zope.org/pipermail/zope-tests/2013-April/073719.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073720.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073718.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-27 00:00:00 UTC and 2013-03-28 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 [1]Still Failing - zopetoolkit_trunk - Build # 216 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 216 https://mail.zope.org/pipermail/zope-tests/2013-March/073579.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073578.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073577.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-26 00:00:00 UTC and 2013-03-27 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 [1]Still Failing - zopetoolkit_trunk - Build # 215 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 215 https://mail.zope.org/pipermail/zope-tests/2013-March/073564.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073563.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073562.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
On Wed, Mar 27, 2013 at 09:53:56PM +0200, Marius Gedminas wrote: > On Wed, Mar 27, 2013 at 12:00:17PM +0100, Patrick Gerken wrote: > > 2013/3/27 Zope tests summarizer > > > [1]FAILED Still Failing - zopetoolkit_trunk - Build # 214 > > >https://mail.zope.org/pipermail/zope-tests/2013-March/073549.html ... > svn co svn+ssh://svn.zope.org/repos/main/zopetoolkit/trunk zopetoolkit > cd zopetoolkit > virtualenv -p python2.7 python > python/bin/python bootstrap.py > bin/buildout -c development-python2.cfg buildout:prefer-final=false > bin/test-ztk-zope.traversing > > I can reproduce the problem, and my bin/test-ztk-zope.traversing does > *not* include persistent in sys.path. I think we've been bit by https://bugs.launchpad.net/zc.buildout/+bug/257555 $ ls -d src/*/*.egg src/BTrees/persistent-4.0.6-py2.7-linux-x86_64.egg src/BTrees/zope.interface-4.0.5-py2.7-linux-x86_64.egg src/ZODB/persistent-4.0.6-py2.7-linux-x86_64.egg src/ZODB/zope.interface-4.0.5-py2.7-linux-x86_64.egg src/zope.security/zope.interface-4.0.5-py2.7-linux-x86_64.egg src/zope.security/zope.proxy-4.1.3-py2.7-linux-x86_64.egg $ grep setup_requires src/*/setup.py src/BTrees/setup.py: setup_requires=['persistent'], src/ZODB/setup.py: setup_requires=['persistent'], src/zope.security/setup.py:setup_requires = [] src/zope.security/setup.py:setup_requires = ['zope.proxy >= 4.1.0'] src/zope.security/setup.py: setup_requires=setup_requires, Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
On Wed, Mar 27, 2013 at 12:00:17PM +0100, Patrick Gerken wrote:
> 2013/3/27 Zope tests summarizer
> > [1]FAILED Still Failing - zopetoolkit_trunk - Build # 214
> >https://mail.zope.org/pipermail/zope-tests/2013-March/073549.html
>
> I can reproduce the problems.
Hehe, there's a U+200B ZERO WIDTH SPACE in front of that sentence.
> I do not understand at all, why buildout does not add persistent into the
> path for zope.traverser. Through dependency chains it depends on BTrees and
> BTrees depends on persistent, still, persistent is not in the paths for my
> script. Marius, can you show me your buildout script and your test script
> for zope traverser? Mine is:
>
> do3cc@BRICK> cat bin/buildout | sed -e 's/\(
> *\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/'
mg@platonas: ~/src/zopetoolkit [svn:trunk] $ cat bin/buildout | sed -e 's/\(
> *\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/'
sed: -e expression #1, char 4: unterminated `s' command
I'm not sure what that sed expression was supposed to do, so there's the entire
thing:
mg@platonas: ~/src/zopetoolkit [svn:trunk] $ cat bin/buildout
#!/home/mg/src/zopetoolkit/python/bin/python
import sys
sys.path[0:0] = [
'/home/mg/.buildout/eggs/distribute-0.6.35-py2.7.egg',
'/home/mg/.buildout/eggs/zc.buildout-2.0.1-py2.7.egg',
]
import zc.buildout.buildout
if __name__ == '__main__':
sys.exit(zc.buildout.buildout.main())
/home/mg/src/zopetoolkit/python is a virtualenv for Python 2.7, to avoid
/usr/lib/python2.7/dist-packages/zope.interface (which is 3.6.1).
mg@platonas: ~/src/zopetoolkit [svn:trunk] $ cat bin/test-ztk-zope.traversing
#!/home/mg/src/zopetoolkit/python/bin/python
import sys
sys.path[0:0] = [
'/home/mg/.buildout/eggs/zope.traversing-4.0.0a2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.testrunner-4.2.0-py2.7.egg',
'/home/mg/.buildout/eggs/zope.interface-4.0.4-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.exceptions-4.0.6-py2.7.egg',
'/home/mg/.buildout/eggs/six-1.2.0-py2.7.egg',
'/home/mg/.buildout/eggs/distribute-0.6.35-py2.7.egg',
'/home/mg/.buildout/eggs/zope.testing-4.1.2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.tales-4.0.1-py2.7.egg',
'/home/mg/.buildout/eggs/zope.security-4.0.0b1-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.configuration-4.0.2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.component-4.1.0-py2.7.egg',
'/home/mg/.buildout/eggs/zope.browserresource-4.0.0-py2.7.egg',
'/home/mg/.buildout/eggs/zope.annotation-4.2.0-py2.7.egg',
'/home/mg/.buildout/eggs/zope.publisher-4.0.0a2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.proxy-4.1.1-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.location-4.0.1-py2.7.egg',
'/home/mg/.buildout/eggs/zope.i18nmessageid-4.0.2-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.i18n-4.0.0a4-py2.7.egg',
'/home/mg/.buildout/eggs/transaction-1.4.1-py2.7.egg',
'/home/mg/.buildout/eggs/zope.schema-4.3.2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.event-4.0.2-py2.7.egg',
'/home/mg/.buildout/eggs/zope.contenttype-4.0.1-py2.7.egg',
'/home/mg/.buildout/eggs/BTrees-4.0.5-py2.7-linux-x86_64.egg',
'/home/mg/.buildout/eggs/zope.browser-2.0.1-py2.7.egg',
'/home/mg/.buildout/eggs/pytz-2012j-py2.7.egg',
'/home/mg/.buildout/eggs/persistent-4.0.6-py2.7-linux-x86_64.egg',
]
import os
sys.argv[0] = os.path.abspath(sys.argv[0])
os.chdir('/home/mg/src/zopetoolkit/parts/test-ztk-zope.traversing')
import zope.testrunner
if __name__ == '__main__':
sys.exit(zope.testrunner.run([
'--test-path',
'/home/mg/.buildout/eggs/zope.traversing-4.0.0a2-py2.7.egg',
]))
What I did was
svn co svn+ssh://svn.zope.org/repos/main/zopetoolkit/trunk zopetoolkit
cd zopetoolkit
virtualenv -p python2.7 python
python/bin/python bootstrap.py
bin/buildout prefer-final=false
bin/test-ztk-zope.traversing
because I didn't realize I needed to use a different buildout config!
Trying now to
bin/buildout -c development-python2.cfg buildout:prefer-final=false
bin/test-ztk-zope.traversing
I can reproduce the problem, and my bin/test-ztk-zope.traversing does
*not* include persistent in sys.path.
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
signature.asc
Description: Digital signature
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
2013/3/27 Zope tests summarizer > This is the summary for test reports received on the > zope-tests list between 2013-03-25 00:00:00 UTC and 2013-03-26 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 > > > [1]Still Failing - zopetoolkit_trunk - Build # 214 >winbot / ZODB_dev py_265_win32 >winbot / ZODB_dev py_265_win64 >winbot / ZODB_dev py_270_win32 >winbot / ZODB_dev py_270_win64 > [2]winbot / z3c.contents_py_265_32 > [3]winbot / z3c.form_py_265_32 >winbot / ztk_10 py_254_win32 >winbot / ztk_10 py_265_win32 >winbot / ztk_10 py_265_win64 >winbot / ztk_11 py_254_win32 >winbot / ztk_11 py_265_win32 >winbot / ztk_11 py_265_win64 >winbot / ztk_11 py_270_win32 >winbot / ztk_11 py_270_win64 > > Non-OK results > -- > > [1]FAILED Still Failing - zopetoolkit_trunk - Build # 214 >https://mail.zope.org/pipermail/zope-tests/2013-March/073549.html > I can reproduce the problems. I do not understand at all, why buildout does not add persistent into the path for zope.traverser. Through dependency chains it depends on BTrees and BTrees depends on persistent, still, persistent is not in the paths for my script. Marius, can you show me your buildout script and your test script for zope traverser? Mine is: do3cc@BRICK> cat bin/buildout | sed -e 's/\( *\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/' /bin/python import sys sys.path[0:0] = [ /eggs/distribute-0.6.35-py2.7.egg', /eggs/zc.buildout-2.0.1-py2.7.egg', ] import zc.buildout.buildout if __name__ == '__main__': sys.exit(zc.buildout.buildout.main()) do3cc@BRICK> cat bin/test-ztk-zope.traversing | sed -e 's/\( *\).*\(\/[^\/]*\)\(\/[^\/]*\)/\1\2\3/' /bin/python import sys sys.path[0:0] = [ /zope.traversing/src', /zope.testrunner/src', /zope.interface/src', /zope.exceptions/src', /eggs/six-1.2.0-py2.7.egg', /eggs/distribute-0.6.35-py2.7.egg', /zope.testing/src', /zope.tales/src', /zope.security/src', /zope.configuration/src', /zope.component/src', /zope.browserresource/src', /zope.annotation/src', /zope.publisher/src', /zope.proxy/src', /zope.location/src', /zope.i18nmessageid/src', /zope.i18n/src', /src/transaction', /src/BTrees', /zope.schema/src', /zope.event/src', /zope.contenttype/src', /zope.browser/src', /eggs/pytz-2012j-py2.7.egg', ] import os sys.argv[0] = os.path.abspath(sys.argv[0]) /parts/test-ztk-zope.traversing') import zope.testrunner if __name__ == '__main__': sys.exit(zope.testrunner.run([ /zope.traversing/src', ])) I am using python 2.7 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-25 00:00:00 UTC and 2013-03-26 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 [1]Still Failing - zopetoolkit_trunk - Build # 214 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 214 https://mail.zope.org/pipermail/zope-tests/2013-March/073549.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073548.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073547.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-21 00:00:00 UTC and 2013-03-22 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 [1]Still Failing - zopetoolkit_trunk - Build # 210 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 210 https://mail.zope.org/pipermail/zope-tests/2013-March/073473.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073472.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073471.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 3, OK: 12
On Fri, Mar 22, 2013 at 01:00:02AM +, Zope tests summarizer wrote: > [1]Still Failing - zopetoolkit_trunk - Build # 209 > [2]winbot / z3c.contents_py_265_32 > [3]winbot / z3c.form_py_265_32 Same as yesterday: three failures I can't reproduce. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 3, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-20 00:00:00 UTC and 2013-03-21 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 [1]Still Failing - zopetoolkit_trunk - Build # 209 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 209 https://mail.zope.org/pipermail/zope-tests/2013-March/073458.html [2]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073457.html [3]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073456.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
