Re: [Zope-dev] zope-tests - FAILED: 1, OK: 8
On Tue, Oct 15, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED Failure - zopetoolkit_trunk - Build # 427 https://mail.zope.org/pipermail/zope-tests/2013-October/079244.html Network timeout while trying to connect and fetch http://python-distribute.org/distribute_setup.py (I see there are still copies of bootstrap.py that execute code fetched over plain HTTP. Don't let Donald Stufft know.) 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: 1, OK: 9
On Sat, Oct 12, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079204.html The usual 24-hour winbot lag. 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 )
Re: [Zope-dev] zope-tests - FAILED: 1, OK: 9
On Thu, Oct 10, 2013 at 02:19:21PM +0300, Marius Gedminas wrote: On Thu, Oct 10, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079170.html I haven't found the round tuits to fix this yet. I still plan on doing that, whenever I can find the mythical spare time. Should be fixed with zope.testbrowser 4.0.4. 5.0.0 is still waiting for documentation testing and some crawling of all reverse dependencies to see how badly they break and how hard they're to fix. If any of you care about zope.testbrowser on Python 3, feel free to pitch in. 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: 1, OK: 9
On Thu, Oct 10, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079170.html I haven't found the round tuits to fix this yet. I still plan on doing that, whenever I can find the mythical spare time. 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: 5, OK: 9
On Fri, Sep 27, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / zc.ngi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078948.html
Intermittent error. An interesting one:
--
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.test, line 253, in async.test
Failed example:
zc.ngi.async.cleanup_map()
Exception raised:
Traceback (most recent call last):
File c:\Python26_32\lib\doctest.py, line 1253, in __run
compileflags, 1) in test.globs
File doctest async.test[64], line 1, in module
zc.ngi.async.cleanup_map()
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 175, in
cleanup_map
c.close()
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 707, in close
self.implementation.call_from_thread(lambda : self._close(handler))
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 69, in
call_from_thread
self.notify_select()
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 882, in
pull_trigger
self.trigger.send('x')
File c:\Python26_32\lib\socket.py, line 167, in _dummy
raise error(EBADF, 'Bad file descriptor')
error: [Errno 9] Bad file descriptor
--
[2]FAILED winbot / zope.app.authentication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078945.html
[3]FAILED winbot / zope.app.http_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078946.html
[4]FAILED winbot / zope.app.publication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078944.html
[5]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078947.html
WebTest version conflict.
(I'll get to it at some point, but ATM I'm busy.)
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: 1, OK: 9
On Wed, Sep 25, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078913.html Ah, the webtest version conflict is back. 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: 1, OK: 7
On Tue, Sep 24, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / ztk_11 py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-September/078904.html File c:\eggs\zope.testrunner-4.0.4-py2.7.egg\zope\testrunner\testrunner-layers-buff.txt, line 100, in testrunner-layers-buff.txt The 'LAYER FINISHED' text appears at a latter point than expected. Looks like a slight race condition in the test. 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: 12, OK: 8
On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote: On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [8]winbot / zope.app.wsgi_py_265_32 zope.testbrowser-caused WebTest version conflict. I've no idea why these errors disappeared. I plan to release zope.testbrowser 5.0.0 this week. It should fix these (and probably cause lots of pain elsewhere, if people use undocumented internals like .mech_browser directly, which they do). I basically chickened out. IIRC the new webtest-based zope.testbrowser breaks API pretty hard (e.g. you can't use zope.app.testing.functional.FunctionalTestLayer any more; you must create a WSGITestLayer from I-forgot-what-zope.-package). What's worse, it lacks documentation for how you're supposed to migrate from older zope.testbrowser versions (=4.x) to newer versions (5.x). I will not do a release until this documentation exists. It may take me some time to find the time and remember how everything fits together. It shouldn't be too hard (just find some zope package that did the migration in a py3 branch, then document what it did), but I find my motivation is pretty low this week. 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: 1, OK: 8
On Sat, Sep 21, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]winbot / zope.testbrowser_py_265_32 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 )
Re: [Zope-dev] zope-tests - FAILED: 6, OK: 12
On Fri, Sep 20, 2013 at 09:40:00AM -0400, Tres Seaver wrote: On 09/18/2013 06:40 AM, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [6]winbot / zope.testbrowser_py_265_32 The fix that was supposed to fix this didn't because https://github.com/Pylons/webtest/pull/87/files#r6427276 We're waiting for https://github.com/Pylons/webtest/pull/88 and WebTest 2.0.9 now. FWIW, WebTest 2.0.9 went out Wednesday: https://pypi.python.org/pypi/WebTest/2.0.9 Thank you, I didn't notice. Pushed a test fix (zope.testbrowser actually had a test that asserted the content type we specified was being ignored!). 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: 6, OK: 12
On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]winbot / ZODB_dev py_265_win64 Non-deterministic test failure: Failure in test c:\buildslave\zodb_dev_py_265_win64\build\src\ZODB\historical_connections.txt -- File c:\buildslave\zodb_dev_py_265_win64\build\src\ZODB\historical_connections.txt, line 220, in historical_connections.txt Failed example: [c in conns1 for c in conns2] Expected: [False, False, True, True] Got: [False, False, False, True] Cleared up all by itself on next build. [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [5]winbot / zope.app.wsgi_py_265_32 WebTest version conflict [6]winbot / zope.testbrowser_py_265_32 The fix that was supposed to fix this didn't because https://github.com/Pylons/webtest/pull/87/files#r6427276 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: 6, OK: 12
On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [6]winbot / zope.testbrowser_py_265_32 The fix that was supposed to fix this didn't because https://github.com/Pylons/webtest/pull/87/files#r6427276 We're waiting for https://github.com/Pylons/webtest/pull/88 and WebTest 2.0.9 now. 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] github etiquette
On Tue, Sep 17, 2013 at 12:04:04PM +0200, Jan-Wijbrand Kolman wrote: I wonder if there is a formal or informal write-up of how to nicely contribute code to the repositories under the zopefoundation umbrella. I don't think so. I'd like to see one. Back in the subversion days I would branch a project, amend code, write tests, commit this to the repository, ask for feedback on the list, and, when deemed acceptable, merge my changes back to the project's trunk, perhaps even make a release of the project. Yesterday I wanted to add a small feature to zope.formlib and wondered whether I should: 1) clone the canonical zope.formlib repository, make a branch, do my work, push the changes, ask for feedback on the list and eventually merge the branch to the mainline. or 2) fork the repository, make a branch in the fork, do my work, push the changes to my fork, and issue a pull request. The latter is what I did, without explicitly asking for feedback. Luckily someone did give me feedback (thanks!) :-) I think a pull request is right. It doesn't matter much if the branch you're asking to pull is in the main repository or in a private fork. Now that I mended the pull request, should I merge the pull request myself? Or is the current etiquette that someone else should merge the pull request? I think it's fine to merge own pull requests, provided that somebody +1'd it. (Or if nobody cared for a couple of weeks, even after asking for feedback on the list.) My apologies in case I missed an obvious document or reference somewhere that describes the way we should work with the zopefoundation's codebase... Can we please get the http://foundation.zope.org/ website source on GitHub, so it becomes maintainable by the community? 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] github etiquette
On Tue, Sep 17, 2013 at 07:47:42AM -0400, Jim Fulton wrote: On Tue, Sep 17, 2013 at 7:00 AM, Marius Gedminas mar...@gedmin.as wrote: Now that I mended the pull request, should I merge the pull request myself? Or is the current etiquette that someone else should merge the pull request? I think it's fine to merge own pull requests, provided that somebody +1'd it. (Or if nobody cared for a couple of weeks, even after asking for feedback on the list.) I strongly prefer that the reviewer do the merge. FWIW the only reason I'm in favour of self-merges is that this short-circuits the have you signed the ZF committer agreement? dance. Only people who have can merge. I also feel silly when I ask this question from people with very familiar names. (I feel that I have to do when I don't see ZF membership on their GitHub profile.) I'd also really like reviewers to take their responsibility seriously, making comments and suggestions where appropriate. Oh, absolutely. Software review, done well, improves the software, and, more importantly, improves the developers. 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] Misattribution of checkin emails
Certain Subversion commits show up on the checkins@ list misattributed to Marius Gedminas cvs-ad...@zope.org. Examples: r130062 - https://mail.zope.org/pipermail/checkins/2013-March/065903.html r130296 - https://mail.zope.org/pipermail/checkins/2013-August/067498.html r130309 - https://mail.zope.org/pipermail/checkins/2013-September/067596.html All of these were actually made by Gediminas Paulauskas (svn username 'menesis'). I've tried to raise this on the checkins@ list but received no response yet. 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] github etiquette
On Tue, Sep 17, 2013 at 09:35:58AM -0400, Jim Fulton wrote: On Tue, Sep 17, 2013 at 8:58 AM, Marius Gedminas mar...@gedmin.as wrote: FWIW the only reason I'm in favour of self-merges is that this short-circuits the have you signed the ZF committer agreement? dance. Only people who have can merge. Sorry, I don't understand the point you're making. I'll try to explain better. I also feel silly when I ask this question from people with very familiar names. (I feel that I have to do when I don't see ZF membership on their GitHub profile.) So are you saying you don't merge other people's code because you don't want to ask if they're contributors? No. I'm saying the reviewer-merges workflow looks like this: 1. Somebody creates a pull request 2. A reviewer reviews 3. OP fixes 4. Reviewer asks have you signed the agreement? if not please sign 5. OP says he/she signed it 6. Reviewer trusts OP's word and merges (I don't have a good short word for somebody who created the pull request, so I abused Original Poster.) Whereas I'd prefer 1. Somebody creates a pull request 2. A reviewer reviews 3. OP fixes 4. Reviewer says looks good to me, feel free to merge (if you're not a committer already, see http://foundation.zope.org/agreements) 5. OP merges It's not a very strong preference. I can feel myself changing my mind already ;-) OTOH the implicit trust in step 6 makes me a bit uneasy, and I'm not quite sure how to verify the fact of the signing. Wait for the user to show up in https://github.com/zopefoundation?tab=members ? I can understand this, but I'd still try to encourage a more review-centric workflow. +1 Also, if a change is trivial, the PR doesn't have to be from a contributor. I understand that triviality isn't always clear. It's completely unclear to me, once the PR goes beyond typo fixes. :( 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: 5, OK: 12
On Mon, Sep 16, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]winbot / zope.app.authentication_py_265_32
[2]winbot / zope.app.http_py_265_32
[3]winbot / zope.app.publication_py_265_32
[4]winbot / zope.app.wsgi_py_265_32
WebTest version conflict
[5]winbot / zope.testbrowser_py_265_32
Interesting new error:
Failure in test test_file_upload (zope.testbrowser.tests.test_browser)
Failed doctest test for zope.testbrowser.tests.test_browser.test_file_upload
File
c:\buildslave\zope.testbrowser\build\src\zope\testbrowser\tests\test_browser.py,
line 324, in test_file_upload
--
File
c:\buildslave\zope.testbrowser\build\src\zope\testbrowser\tests\test_browser.py,
line 358, in zope.testbrowser.tests.test_browser.test_file_upload
Failed example:
browser.getControl('OK').click() # doctest: +REPORT_NDIFF +ELLIPSIS
Differences (ndiff with -expected +actual):
POST / HTTP/1.1
- ...
- Content-disposition: form-data; name=foo; filename=x.csv
- Content-type: text/csv
+ Connection: close
+ Host: localhost
+ Referer: http://localhost/
+ User_Agent: Python-urllib/2.4
+ X_Zope_Handle_Errors: True
BLANKLINE
+ --
+ Content-disposition: form-data; name=foo; filename=x.csv
+ Content-type: application/octet-stream
+
- blah blah blah
+ blah blah blah
? +
- ...
+ --
+ BLANKLINE
Ran 39 tests with 1 failures, 0 errors and 0 skipped in 1.328 seconds.
At first I suspected Windows line endings, but look closer:
- Content-type: text/csv
+ Content-type: application/octet-stream
Any ideas?
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: 5, OK: 12
On Mon, Sep 16, 2013 at 01:50:32PM +0300, Marius Gedminas wrote:
On Mon, Sep 16, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[5]winbot / zope.testbrowser_py_265_32
Interesting new error:
...
At first I suspected Windows line endings, but look closer:
- Content-type: text/csv
+ Content-type: application/octet-stream
rdesktop winbot.zope.org
Git Bash
$ /c/python26_32/python
import mimetypes
mimetypes.guess_type('x.csv')
(None, None)
So that's fun.
The test in question does
browser.getControl(name='foo').add_file(
... b'blah blah blah', 'text/csv', 'x.csv')
and then we get to the implementation of .add_file(), which has this
nice little XXX comment
# XXX: webtest relies on mimetypes.guess_type to get mime type of
# upload file and doesn't let to set it explicitly, so we are ignoring
# content_type parameter here. If it is still unacceptable, consider
# using mock.object to force mimetypes to return right type.
self._form[self.name] = webtest.forms.Upload(filename or '', contents)
and then ignores the content_type argument.
First of all, monkey-patch? Instead of fixing the problem upstream?
Seriously?
Therefore https://github.com/Pylons/webtest/issues/86
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: 5, OK: 13
On Sun, Sep 15, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]winbot / zope.app.authentication_py_265_32
[2]winbot / zope.app.http_py_265_32
[3]winbot / zope.app.publication_py_265_32
[4]winbot / zope.app.wsgi_py_265_32
WebTest version conflict
[5]winbot / zope.testbrowser_py_265_32
This is new: bootstrap.py fails with
Traceback (most recent call last):
File bootstrap.py, line 108, in module
pkg_resources.Requirement.parse('distribute')).location
AttributeError: 'NoneType' object has no attribute 'location'
Last successful buildi (commit b0ed26c):
http://winbot.zope.org/builders/zope.testbrowser_py_265_32/builds/988
First failing build: commit c68904b.
What happened in between: I merged the py3 branch into master.
Old master used buildout 1.x. The py3 branch used buildout 2.0.
I'll try updating bootstrap.py to v2.2.
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: 12, OK: 8
On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]winbot / z3c.ptcompat_py_265_32 [5]winbot / zope.app.publisher_py_265_32 [6]winbot / zope.app.security_py_265_32 [7]winbot / zope.app.session_py_265_32 [9]winbot / zope.catalog_py_265_32 [10] winbot / zope.exceptions_py_265_32 [11] winbot / zope.session_py_265_32 [12] winbot / zope.viewlet_py_265_32 GitHub was unreachable: fatal: unable to connect to github.com: github.com[0: 192.30.252.130]: errno=No such file or directory Ironically, https://status.github.com/ is giving me a 500 Internal Server Error right now. a few minutes later It's back up and shows no downtime during the last 7 days. Must be a network problem. [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [8]winbot / zope.app.wsgi_py_265_32 zope.testbrowser-caused WebTest version conflict. I plan to release zope.testbrowser 5.0.0 this week. It should fix these (and probably cause lots of pain elsewhere, if people use undocumented internals like .mech_browser directly, which they do). 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: 4, OK: 8
On Tue, Sep 10, 2013 at 09:49:50AM +0200, Brian Sutherland wrote: On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote: IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support, built on top of WebTest, waiting in the py3 branch for... Actually, I'm not sure what it is waiting for. (I thought ZODB with Python 3 support, but it doesn't look like zope.testbrowser depends on ZODB, at least not directly.) Indeed, and it's had no changes for at least 5 months and been tested with a few existing codebases. +1 for releasing it One tests fails in the py3 branch: test_strip_linebreaks_from_textarea. It tests that if you inspect getControl(name='textarea').value, you'll see one initial '\n' stripped away. This fails when the textarea in question has two initial newlines: textarea Foo /textarea The test expects .value to be '\nFoo\n', but it actually gets 'Foo\n'. This test was added by Benji York in 2006 (commit 4545f144) and refers to issue 644 in some unspecified bug tracker. Google allowed me to find a copy of the issue in question: https://bugs.launchpad.net/zope3/+bug/98371 In particular the following comment is interesting: We've verified that browsers (we tested Firefox, Mozilla, Safari, and IE) will strip a single leading newline (crlf) if it is at the beginning of the string. -- Jim Fulton, https://bugs.launchpad.net/zope3/+bug/98371/comments/12 It was serious enough to warrant changes to the local copy of ClientForm (and an upstream submission of the patch). It looks like what happened here was that WebTest itself was modified to eat the first newline in a textarea: https://github.com/Pylons/webtest/pull/69 so now we eat two. This change was released in WebTest 2.0.6: http://webtest.pythonpaste.org/en/latest/changelog.html#id2 I guess what we have to do is remove the 1st newline stripping logic from zope.testbrowser and require WebTest = 2.0.6. Ok, fixed. 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: 4, OK: 8
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support,
built on top of WebTest, waiting in the py3 branch for... Actually, I'm
not sure what it is waiting for. (I thought ZODB with Python 3 support,
but it doesn't look like zope.testbrowser depends on ZODB, at least not
directly.)
I think I remembered now: a WebTest release with some bugfixes.
I'm trying to merge the py3 branch to master now. There's one issue:
the test for https://github.com/zopefoundation/zope.testbrowser/pull/4
uses the internal .mech_browser attribute.
I think what is actually wanted here is a new API:
browser.handleRedirects = False
browser.open(...) # or browser.submit()
assert browser.getHeaders('Status') == '302 Found'
Comments?
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: 4, OK: 8
On Mon, Sep 09, 2013 at 12:26:33PM -0400, Tres Seaver wrote: On 09/09/2013 11:53 AM, Marius Gedminas wrote: On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote: On 09/07/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html All four show the same failure in the bulidout phase: % --- While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 % --- Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest = 1.3.4']. OTOH it wasn't me who added that = constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7ab3da80cf394b75f977d91 I just made a release with all the accumulated changes. Looks like that was Adam: maybe we should be trying to push out a version of z.tb compatible with current WebTest? IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support, built on top of WebTest, waiting in the py3 branch for... Actually, I'm not sure what it is waiting for. (I thought ZODB with Python 3 support, but it doesn't look like zope.testbrowser depends on ZODB, at least not directly.) Andrey? 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: 4, OK: 8
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote: On 09/07/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html All four show the same failure in the bulidout phase: % --- c:\buildslave\zope.app.wsgi\buildcall C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 % --- Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest = 1.3.4']. OTOH it wasn't me who added that = constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7ab3da80cf394b75f977d91 I just made a release with all the accumulated changes. 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: 9, OK: 11
On Thu, Sep 05, 2013 at 08:53:54AM +0200, Adam GROSZER wrote: On 09/05/2013 02:58 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2013 07:00 PM, Zope tests summarizer wrote: [1]Failure - zopetoolkit_trunk - Build # 379 Fixed - zopetoolkit_trunk - Build # 389 [2]Still Failing - zopetoolkit_trunk - Build # 380 [3]Still Failing - zopetoolkit_trunk - Build # 381 [4]Still Failing - zopetoolkit_trunk - Build # 382 [5]Still Failing - zopetoolkit_trunk - Build # 383 [6]Still Failing - zopetoolkit_trunk - Build # 384 [7]Still Failing - zopetoolkit_trunk - Build # 385 [8]Still Failing - zopetoolkit_trunk - Build # 386 [9]Still Failing - zopetoolkit_trunk - Build # 387 Anybody understand what caused those errors? There isn't any activity during the range of time represented by those failures. It looks like the distribute/setuptools hell broke in. Maybe Patrick changed something? I'm guessing an upgrade of /usr/local/bin/virtualenv-2.7 to some version that ignores --distribute (since it's superseded by setuptools). Unfortunately buildout's bootstrap.py really really *really* wants to have distribute. BTW the last build was successful, so Patrick figured out how to appease bootstrap.py in the end. 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: 1, OK: 10
On Tue, Aug 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078256.html Nondeterministic timeout: File c:\buildslave\zc.ngi\build\src\zc\ngi\doc\index.txt, line 185, in index.txt Failed example: zc.ngi.async.connect(listener.address, one); zc.ngi.async.wait(1) Exception raised: Traceback (most recent call last): File c:\Python26_32\lib\doctest.py, line 1253, in __run compileflags, 1) in test.globs File doctest index.txt[0], line 1, in module zc.ngi.async.connect(listener.address, one); zc.ngi.async.wait(1) File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 118, in wait raise zc.ngi.interfaces.Timeout Timeout Last build succeeded despite running the exact same version of the zc.ngi code. 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: 38, OK: 8
On Mon, Aug 05, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]Failure - zopetoolkit_trunk - Build # 349 [2]winbot / z3c.baseregistry_py_265_32 [3]winbot / z3c.datagenerator_py_265_32 [4]winbot / z3c.jsonrpc_py_265_32 [5]winbot / z3c.layer.pagelet_py_265_32 [6]winbot / z3c.menu.ready2go_py_265_32 [7]winbot / z3c.password_py_265_32 [8]winbot / z3c.sampledata_py_265_32 [9]winbot / z3c.template_py_265_32 [10] winbot / z3c.testing_py_265_32 [11] winbot / zc.resourcelibrary_py_265_32 [12] winbot / zc.sourcefactory_py_265_32 [13] winbot / zodbpickle_py_265_32 [14] winbot / zope.app.authentication_py_265_32 [15] winbot / zope.app.content_py_265_32 [16] winbot / zope.app.generations_py_265_32 [17] winbot / zope.app.http_py_265_32 [18] winbot / zope.app.publication_py_265_32 [19] winbot / zope.app.zcmlfiles_py_265_32 [20] winbot / zope.applicationcontrol_py_265_32 [21] winbot / zope.authentication_py_265_32 [22] winbot / zope.browserpage_py_265_32 [23] winbot / zope.browserresource_py_265_32 [24] winbot / zope.contentprovider_py_265_32 [25] winbot / zope.dublincore_py_265_32 [26] winbot / zope.filerepresentation_py_265_32 [27] winbot / zope.i18n_py_265_32 [28] winbot / zope.i18nmessageid_py_265_32 [29] winbot / zope.intid_py_265_32 [30] winbot / zope.mimetype_py_265_32 [31] winbot / zope.principalannotation_py_265_32 [32] winbot / zope.renderer_py_265_32 [33] winbot / zope.securitypolicy_py_265_32 [34] winbot / zope.sendmail_py_265_32 [35] winbot / zope.session_py_265_32 [36] winbot / zope.testing_py_265_32 [37] winbot / zope.traversing_py_265_32 [38] winbot / zope.viewlet_py_265_32 Transient network errors. Subsequent builds all succeeded. 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: 9
On Sat, Jul 20, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]winbot / z3c.layer.pagelet_py_265_32 [2]winbot / zc.sourcefactory_py_265_32 [3]winbot / zope.schema_py_265_32 Last builds all succeeded. 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: 9
On Fri, Jul 19, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077886.html setuptools 0.9.5 is installed in site-packages; bootstrap.py insists on using distribute instead. I've upgraded to bootstrap v2.2, let's see if that helps. [2]FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077885.html Same [3]FAILED winbot / zope.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-July/077887.html While: Installing. Getting section tox. Error: The referenced section, 'tox', was not defined. A simple mistake in buildout.cfg. Fixed. 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 - OK: 10
Woot! 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: 5, OK: 8
On Tue, Jul 16, 2013 at 07:08:39PM -0400, Tres Seaver wrote: On 07/16/2013 06:53 AM, Marius Gedminas wrote: Perhaps manually installing setuptools = 0.7 into c:\python2*_64 would fix the failing builds? Further evidence for this suggestion: winbot's c:/python26_32/python.exe has import setuptools setuptools.__file__ '\\setuptools-0.7.1-...' and works fine, while winbot's c:/python26_64/python.exe has import setuptools setuptools.__file__ '\\distribute-0.6.44-...' and doesn't. +1. Let's just get past the distribute / old setuptools mess and get on with our lives. I'm somewhat ashamed to admit that I don't know how to do that. Normally I get setuptools with sudo apt-get install python-setuptools, or by creating a virtualenv. IIRC there's some sort of ez_setup.py that you can run? Never mind, I can read the fine manual: https://pypi.python.org/pypi/setuptools/0.9.5#windows So, here's what I did: - rdesktop'ed into winbot - Control Panel - Add/Remove Programs - removed Python 2.6 setuptools 0.6c11 (it said it was already removed, so I just OK'ed removing the add/remove programs item) - removed Python 2.7 setuptools 0.6c11 (this time it said it removed 18 files and directories) - left setuptools 0.6c11 installers for Python 2.4 and 2.5 alone because meh - launched Git bash - cd /c/Python26_64/Lib/site-packages - rm -rf setuptools* distribute* - cd /tmp - curl https://bitbucket.org/pypa/setuptools/downloads/ez_setup.py ez_setup.py - /c/Python26_64/python ez_setup.py - cd /c/Python27_64/Lib/site-packages - rm -rf setuptools* distribute* - cd /tmp - /c/Python27_64/python ez_setup.py And now I'm wondering if those control panel installers were about 32-bit or 64-bit installs, and I wonder if I broke Python27_32 by removing all traces of setuptools form there. Let's check: $ /c/Python27_32/python import setuptools setuptools.__file__ '\\distribute-0.6.44-...' Huh? And no builds failed on py_270_win32? I don't understand, and I don't _want_ to understand. Let's just see what buildbots report tomorrow. 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: 5, OK: 8
On Tue, Jul 16, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077848.html
[2]FAILED winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077850.html
[3]FAILED winbot / ztk_10 py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077841.html
[4]FAILED winbot / ztk_11 py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077844.html
[5]FAILED winbot / ztk_11 py_270_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077846.html
All of these fail with
ImportError: No module named pkg_resources
All of them use c:\Python27_64\python.exe
Some of them use c:\buildmaster\bootstrap.py, and some of them use a local
bootstrap.py. In all cases bootstrap downloads
http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg
I went through the list of winbot builders that work on win64, and found
only this (and a few setuptools builders that don't use buildout):
http://winbot.zope.org/builders/BlueBream_dev%20py_270_win64/builds/219
This is BlueBream on Python 2.7 (win64). It downloads
http://pypi.python.org/packages/source/d/distribute/distribute-0.6.34.tar.gz
Incidentally, BlueBream on Python 2.6 (win64) fails bootstrap with
pkg_resources.VersionConflict: (setuptools 0.6c11
(c:\python26_64\lib\site-packages\setuptools-0.6c11-py2.6.egg),
Requirement.parse('setuptools=0.7'))
Suggestion: compare the versions of setuptools in
c:\python2*_64\lib\site-packages with versions in
c:\python2*_32\lib\site-packages, see if there's a pattern.
Perhaps manually installing setuptools = 0.7 into c:\python2*_64 would
fix the failing builds?
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: 7, OK: 6
On Mon, Jul 15, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / ZODB_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2013-July/077831.html
[3]FAILED winbot / ZODB_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2013-July/077833.html
New error:
CalledProcessError: Command '['c:\\Python26_32\\python.exe', '-c', 'from
ZODB.tests.testSerialize import _functest_prep;
_functest_prep(c:\\buildslave\\ZODB_dev_py_265_win32\\build\\parts\\test\\tmp\\tmpy2lgphserializerfunc\\Data.fs)']'
returned non-zero exit status 1
Traceback (most recent call last):
File string, line 1, in module
File
c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\tests\testSerialize.py,
line 164, in _functest_prep
db = DB(fqn)
File c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\DB.py, line
402, in __init__
storage = ZODB.FileStorage.FileStorage(storage, **storage_args)
File
c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\FileStorage\FileStorage.py,
line 164, in __init__
self._lock_file = LockFile(file_name + '.lock')
File c:\eggs\zc.lockfile-1.1.0-py2.6.egg\zc\lockfile\__init__.py, line
81, in __init__
fp = open(path, 'a+')
IOError: [Errno 22] invalid mode ('a+') or filename:
'c:\x08uildslave\\ZODB_dev_py_265_win32\x08uild\\parts\test\tmp\tmpy2lgphserializerfunc\\Data.fs.lock'
Ouch, insufficient quoting of Windows filenames. \b becomes an ASCII
backspace.
[2]FAILED winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077832.html
[4]FAILED winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077834.html
[5]FAILED winbot / ztk_10 py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077825.html
[6]FAILED winbot / ztk_11 py_265_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077828.html
[7]FAILED winbot / ztk_11 py_270_win64
https://mail.zope.org/pipermail/zope-tests/2013-July/077830.html
All Win64 builds break with
ImportError: No module named pkg_resources
No idea why, the bootstrap step downloads an (ancient) version of
setuptools:
Downloading
http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg
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: 7, OK: 6
py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/07.html [6]FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077780.html [7]FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-July/077782.html All on Win64, all fail with ImportError: No module named pkg_resources in buildout 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] What happened to the test summary messages?
So what happened to the daily test summary messages? I miss them. 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: 59, OK: 5
On Thu, May 30, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]winbot / BTrees_py_265_32 [2]winbot / ZODB_dev py_265_win32 [3]winbot / ZODB_dev py_265_win64 [4]winbot / ZODB_dev py_270_win64 [5]winbot / persistent_py_265_32 [6]winbot / transaction_py_265_32 [7]winbot / z3c.baseregistry_py_265_32 [8]winbot / z3c.jsonrpc_py_265_32 [9]winbot / z3c.jsonrpcproxy_py_265_32 [10] winbot / z3c.language.negotiator_py_265_32 [11] winbot / z3c.language.session_py_265_32 [12] winbot / z3c.pdftemplate_py_265_32 [13] winbot / z3c.viewtemplate_py_265_32 [14] winbot / z3c.xmlhttp_py_265_32 [15] winbot / z3c.zrtresource_py_265_32 [16] winbot / zc.catalog_py_265_32 [17] winbot / zc.configuration_py_265_32 [18] winbot / zc.i18n_py_265_32 [19] winbot / zc.monitor_py_265_32 [20] winbot / zc.resourcelibrary_py_265_32 [21] winbot / zope.app.applicationcontrol_py_265_32 [22] winbot / zope.app.component_py_265_32 [23] winbot / zope.app.container_py_265_32 [24] winbot / zope.app.content_py_265_32 [25] winbot / zope.app.debug_py_265_32 [26] winbot / zope.app.error_py_265_32 [27] winbot / zope.app.form_py_265_32 [28] winbot / zope.app.generations_py_265_32 [29] winbot / zope.app.i18n_py_265_32 [30] winbot / zope.app.pagetemplate_py_265_32 [31] winbot / zope.app.rotterdam_py_265_32 [32] winbot / zope.app.schema_py_265_32 [33] winbot / zope.app.server_py_265_32 [34] winbot / zope.app.testing_py_265_32 [35] winbot / zope.app.wsgi_py_265_32 [36] winbot / zope.app.zopeappgenerations_py_265_32 [37] winbot / zope.browser_py_265_32 [38] winbot / zope.cachedescriptors_py_265_32 [39] winbot / zope.configuration_py_265_32 [40] winbot / zope.contenttype_py_265_32 [41] winbot / zope.copy_py_265_32 [42] winbot / zope.deprecation_py_265_32 [43] winbot / zope.dottedname_py_265_32 [44] winbot / zope.event_py_265_32 [45] winbot / zope.filerepresentation_py_265_32 [46] winbot / zope.hookable_py_265_32 [47] winbot / zope.i18nmessageid_py_265_32 [48] winbot / zope.interface_py_265_32 [49] winbot / zope.proxy_py_265_32 [51] winbot / zope.schema_py_265_32 [52] winbot / zope.server_py_265_32 [53] winbot / zope.size_py_265_32 [54] winbot / zope.testing_py_265_32 [55] winbot / ztk_10 py_265_win32 [56] winbot / ztk_10 py_265_win64 [57] winbot / ztk_11 py_265_win32 [58] winbot / ztk_11 py_265_win64 [59] winbot / ztk_11 py_270_win64 All failed with ImportError: No module named pkg_resources while running bin/buildout, after a successful bootstrap. [50] winbot / zope.ramcache_py_265_32 error: Download error for http://pypi.python.org/packages/source/z/zc.buildout/zc.buildout-2.1.0.tar.gz: timed out 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: 1, OK: 13
On Tue, May 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075191.html Looks like a transient network glitch: Reading http://pypi.python.org/simple/zope.interface/ No local packages or download links found for zope.interface 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: 81, OK: 12
On Tue, May 28, 2013 at 10:24:50PM -0400, Tres Seaver wrote: On 05/28/2013 09:00 PM, Zope tests summarizer wrote: [1]FAILED Failure - zopetoolkit_trunk - Build # 278 https://mail.zope.org/pipermail/zope-tests/2013-May/075192.html [2]FAILED Still Failing - zopetoolkit_trunk - Build # 279 https://mail.zope.org/pipermail/zope-tests/2013-May/075193.html These are both failures against PyPI, likely due to the recent CDN / https only changes there. Last builds succeeded for both. I think the rest are likely the same. Actually, they're much more fun: https://bitbucket.org/pypa/setuptools/issue/5/distribute_setuppy-fails-with tl;dr: recent version of distribute_setup.py on python-distribute.org is broken. 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: 1, OK: 13
On Sat, May 25, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]winbot / ZEO_py_265_32 Build #67 with same old error Build #68 was successful (yay! my last fix worked!) Build #69 failed in Git with a WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\buildslave\\ZEO\\build' Probably because I left an rdesktop session with a shell open in that working directory. Aaaugh, Windows, grow up. 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: 2, OK: 13
On Fri, May 24, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]winbot / ZEO_py_265_32 [2]winbot / ZEO_py_265_32 My attempt to blindly fix ZEO.tests.testZEO.client_has_newer_data_than_server was unsuccessful. I'll try to hold my nose and rdesktop into winbot to try and reproduce this, then look around at what's actually happening there. Wish me luck. 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: 2, OK: 12
On Thu, May 23, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 272 Last build successful! [2]winbot / ZEO_py_265_32 Same ZEO.tests.testZEO.client_has_newer_data_than_server that I was unable to reproduce on my laptop. Travis sees some more failures (especially on Python 3), but not this one: https://travis-ci.org/zopefoundation/ZEO 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
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 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 )
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 12
On Mon, May 20, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 269 Same old issue with sys.path lacking persistent. [2]winbot / z3c.datagenerator_py_265_32 [3]winbot / zope.app.locales_py_265_32 [4]winbot / zope.componentvocabulary_py_265_32 [5]winbot / zope.keyreference_py_265_32 [6]winbot / zope.password_py_265_32 [7]winbot / zope.publisher_py_265_32 [8]winbot / zope.security_py_265_32 [9]winbot / zope.tal_py_265_32 Last builds succeeded for all of these. 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: 78, OK: 12
On Tue, May 14, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 266 ImportError: persistent [2]winbot / ZEO_py_265_32 The two blob path issues [3]winbot / z3c.authenticator_py_265_32 [4]winbot / z3c.breadcrumb_py_265_32 [5]winbot / z3c.configurator_py_265_32 [6]winbot / z3c.contents_py_265_32 [7]winbot / z3c.coverage_py_265_32 [8]winbot / z3c.datagenerator_py_265_32 [9]winbot / z3c.form_py_265_32 [10] winbot / z3c.formui_py_265_32 [11] winbot / z3c.json_py_265_32 [12] winbot / z3c.layer.pagelet_py_265_32 [13] winbot / z3c.layer.ready2go_py_265_32 [14] winbot / z3c.macro_py_265_32 [15] winbot / z3c.menu.ready2go_py_265_32 [16] winbot / z3c.pagelet_py_265_32 [17] winbot / z3c.password_py_265_32 [18] winbot / z3c.ptcompat_py_265_32 [19] winbot / z3c.sampledata_py_265_32 [20] winbot / z3c.table_py_265_32 [21] winbot / z3c.tabular_py_265_32 [22] winbot / z3c.template_py_265_32 [23] winbot / z3c.testing_py_265_32 [24] winbot / zc.lockfile_py_265_32 [25] winbot / zc.queue_py_265_32 [26] winbot / zc.sourcefactory_py_265_32 [27] winbot / zope.app.authentication_py_265_32 [28] winbot / zope.app.http_py_265_32 [29] winbot / zope.app.locales_py_265_32 [30] winbot / zope.app.publication_py_265_32 [31] winbot / zope.applicationcontrol_py_265_32 [32] winbot / zope.authentication_py_265_32 [33] winbot / zope.browsermenu_py_265_32 [34] winbot / zope.browserpage_py_265_32 [35] winbot / zope.browserpage_py_265_32 [36] winbot / zope.browserresource_py_265_32 [37] winbot / zope.catalog_py_265_32 [38] winbot / zope.component_py_265_32 [39] winbot / zope.componentvocabulary_py_265_32 [40] winbot / zope.container_py_265_32 [41] winbot / zope.contentprovider_py_265_32 [42] winbot / zope.copypastemove_py_265_32 [43] winbot / zope.datetime_py_265_32 [44] winbot / zope.deferredimport_py_265_32 [45] winbot / zope.dublincore_py_265_32 [46] winbot / zope.error_py_265_32 [47] winbot / zope.exceptions_py_265_32 [48] winbot / zope.formlib_py_265_32 [49] winbot / zope.generations_py_265_32 [50] winbot / zope.i18n_py_265_32 [51] winbot / zope.index_py_265_32 [52] winbot / zope.intid_py_265_32 [53] winbot / zope.keyreference_py_265_32 [54] winbot / zope.location_py_265_32 [55] winbot / zope.login_py_265_32 [56] winbot / zope.mimetype_py_265_32 [57] winbot / zope.minmax_py_265_32 [58] winbot / zope.pagetemplate_py_265_32 [59] winbot / zope.password_py_265_32 [60] winbot / zope.pluggableauth_py_265_32 [61] winbot / zope.principalannotation_py_265_32 [62] winbot / zope.principalregistry_py_265_32 [63] winbot / zope.processlifetime_py_265_32 [64] winbot / zope.ptresource_py_265_32 [65] winbot / zope.publisher_py_265_32 [66] winbot / zope.ramcache_py_265_32 [67] winbot / zope.renderer_py_265_32 [68] winbot / zope.security_py_265_32 [69] winbot / zope.securitypolicy_py_265_32 [70] winbot / zope.sendmail_py_265_32 [71] winbot / zope.sequencesort_py_265_32 [72] winbot / zope.session_py_265_32 [73] winbot / zope.site_py_265_32 [74] winbot / zope.structuredtext_py_265_32 [75] winbot / zope.tal_py_265_32 [76] winbot / zope.tales_py_265_32 [77] winbot / zope.traversing_py_265_32 [78] winbot / zope.viewlet_py_265_32 Distribute/buildout issue. 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: 52, OK: 12
On Mon, May 13, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 265 Same old issue with persistent missing from sys.path [2]winbot / ZEO_py_265_32 One failure: renormalizer doesn't recognize that POSKeyError: u'No blob file at c:\\buildslave\\ZEO\\build\\parts\\test\\tmp\\testsovol5\\server-blobs\\0x00\\0x00\\0x00\\0x00\\0x00\\0x00\\0x00\\0x05\\0x039ea1a3c81e9567.blob' should be rewritten to POSKeyError: 'No blob file at BLOB STORAGE PATH' The other failure: exception is POSKeyError: 'No blob file' and doesn't even mention the filename, while the test expects to see POSKeyError: 'No blob file at BLOB STORAGE PATH' [3]winbot / z3c.authenticator_py_265_32 [4]winbot / z3c.breadcrumb_py_265_32 [5]winbot / z3c.configurator_py_265_32 [6]winbot / z3c.coverage_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.json_py_265_32 [9]winbot / z3c.jsontree_py_265_32 [10] winbot / z3c.language.switch_py_265_32 [11] winbot / z3c.layer.pagelet_py_265_32 [12] winbot / z3c.macro_py_265_32 [13] winbot / z3c.menu.ready2go_py_265_32 [14] winbot / z3c.sampledata_py_265_32 [15] winbot / z3c.table_py_265_32 [16] winbot / z3c.template_py_265_32 [17] winbot / z3c.testing_py_265_32 [18] winbot / zc.lockfile_py_265_32 [19] winbot / zc.queue_py_265_32 [20] winbot / zc.sourcefactory_py_265_32 [21] winbot / zope.app.authentication_py_265_32 [22] winbot / zope.app.basicskin_py_265_32 [23] winbot / zope.app.container_py_265_32 [24] winbot / zope.app.dependable_py_265_32 [25] winbot / zope.app.error_py_265_32 [26] winbot / zope.app.http_py_265_32 [27] winbot / zope.app.publication_py_265_32 [28] winbot / zope.authentication_py_265_32 [29] winbot / zope.browsermenu_py_265_32 [30] winbot / zope.browserpage_py_265_32 [31] winbot / zope.container_py_265_32 [32] winbot / zope.deferredimport_py_265_32 [33] winbot / zope.dublincore_py_265_32 [34] winbot / zope.error_py_265_32 [35] winbot / zope.exceptions_py_265_32 [36] winbot / zope.formlib_py_265_32 [37] winbot / zope.generations_py_265_32 [38] winbot / zope.i18n_py_265_32 [39] winbot / zope.intid_py_265_32 [40] winbot / zope.location_py_265_32 [41] winbot / zope.login_py_265_32 [42] winbot / zope.mimetype_py_265_32 [43] winbot / zope.minmax_py_265_32 [44] winbot / zope.pluggableauth_py_265_32 [45] winbot / zope.principalannotation_py_265_32 [46] winbot / zope.principalregistry_py_265_32 [47] winbot / zope.processlifetime_py_265_32 [48] winbot / zope.renderer_py_265_32 [49] winbot / zope.sendmail_py_265_32 [50] winbot / zope.structuredtext_py_265_32 [51] winbot / zope.testrunner_py_265_32 [52] winbot / zope.traversing_py_265_32 All caused by https://github.com/buildout/buildout/issues/117 aka https://bitbucket.org/tarek/distribute/issue/376/distribute-0639-broke-zcbuildout-210 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: 4, OK: 12
On Thu, Apr 25, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 243 [2]Still Failing - zopetoolkit_trunk - Build # 247 Same old [3]winbot / z3c.contents_py_265_32 Same old -- and I just managed to reproduce it at last. [4]winbot / z3c.form_py_265_32 Last build 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 )
Re: [Zope-dev] zope-tests - FAILED: 4, OK: 12
On Thu, Apr 25, 2013 at 11:21:37AM +0300, Marius Gedminas wrote: On Thu, Apr 25, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [3]winbot / z3c.contents_py_265_32 Same old -- and I just managed to reproduce it at last. ZODB.utils.newTid(None) returns '\\x03\\x9e8\\x9a:\\x12\\x88', i.e. the repr of an 8-byte string instead of the 8-byte string itself. AFAICT it's because repr(persistent.timestamp.TimeStamp(2013, 04, 25, 11, 30, 0)) changed in persistent 4.0.5: https://github.com/zopefoundation/persistent/commit/e692af8281466fa309aae9273864039dcb287383 This was fixed in ZODB 4.0.4a4: https://github.com/zopefoundation/ZODB/commit/8dfbff499d109b1cf86d1b4b2b98a6cf8d17ce43 https://github.com/zopefoundation/ZODB/commit/994af0c5f9df63d403a0e21d80eec51d69686bc4 https://github.com/zopefoundation/ZODB/commit/19e851c2230a20cfcebc68fca37ce2c0bb716b92 https://github.com/zopefoundation/ZODB/commit/2ce7b945003ca8494f970a6946e4143dc18848e6 So latest stable ZODB3 (3.10.5) is incompatible with the two latest stable persistent releases (4.0.5 and 4.0.6). What should we do? Release ZODB3 3.10.6 with a backport of these patches? 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: 4, OK: 12
On Thu, Apr 25, 2013 at 09:49:28AM -0400, Tres Seaver wrote: On 04/25/2013 04:36 AM, Marius Gedminas wrote: So latest stable ZODB3 (3.10.5) is incompatible with the two latest stable persistent releases (4.0.5 and 4.0.6). What should we do? Release ZODB3 3.10.6 with a backport of these patches? ZODB 3.10 bundles its own version of persistent: the standalone one shouldn't be used at all if ZODB 3.10 is in play. Yet somehow we're getting both in a z3c.contents buildout. Note that z3c.contents doesn't directly require either one. It looks like we're getting persistent via BTrees 4.0.5, and we're getting BTrees via zope.annotation 4.2.0, and we're getting zope.annotation via zope.copypastemove 3.8.0, which is a direct requirement of z3c.contents. Are BTrees bundled with ZODB3 as well? (Yes.) Can setuptools dependencies express complicated Debian-package-like concepts like ZODB3 provides BTrees, persistent and ZODB3 conflicts with BTrees, persistent? Are there other ways of avoiding a flag day? I don't think we can reasonably require that no final-version PyPI package may depend on BTrees or persistent until ZODB 4.0.0 final is finally out. 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: 4, OK: 12
On Wed, Apr 24, 2013 at 02:36:28PM +0300, Gediminas Paulauskas wrote: 2013/4/24 Zope tests summarizer nore...@zope.org: This is the summary for test reports received on the zope-tests list between 2013-04-22 00:00:00 UTC and 2013-04-23 00:00:00 UTC: [4]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/074075.html The tests were using an xpath query like './/xmlns:ul[1]' but expecting multiple ul tags. Those tests should have failed long ago, and they do fail on my machine in much older versions of z3c.form. The difference is a newer version of libxml2 = 2.9.0 (the version in Ubuntu 13.04). I have fixed the test and pushed to z3c.form master. Thank you for solving this mystery! 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: 53, OK: 12
On Fri, Apr 19, 2013 at 01:00:03AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 237 [2]Still Failing - zopetoolkit_trunk - Build # 241 [3]winbot / BTrees_py_265_32 [4]winbot / z3c.baseregistry_py_265_32 [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.form_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.jsonrpcproxy_py_265_32 [9]winbot / z3c.language.session_py_265_32 [10] winbot / z3c.layer.pagelet_py_265_32 [11] winbot / z3c.layer.ready2go_py_265_32 [12] winbot / z3c.menu.ready2go_py_265_32 [13] winbot / z3c.password_py_265_32 [14] winbot / z3c.pdftemplate_py_265_32 [15] winbot / z3c.sampledata_py_265_32 [16] winbot / z3c.table_py_265_32 [17] winbot / z3c.template_py_265_32 [18] winbot / z3c.testing_py_265_32 [19] winbot / z3c.viewtemplate_py_265_32 [20] winbot / zc.configuration_py_265_32 [21] winbot / zc.i18n_py_265_32 [22] winbot / zc.lockfile_py_265_32 [23] winbot / zc.resourcelibrary_py_265_32 [24] winbot / zc.sourcefactory_py_265_32 [25] winbot / zope.app.applicationcontrol_py_265_32 [26] winbot / zope.app.authentication_py_265_32 [27] winbot / zope.app.container_py_265_32 [28] winbot / zope.app.error_py_265_32 [29] winbot / zope.app.generations_py_265_32 [30] winbot / zope.app.principalannotation_py_265_32 [31] winbot / zope.app.rotterdam_py_265_32 [32] winbot / zope.app.zcmlfiles_py_265_32 [33] winbot / zope.browser_py_265_32 [34] winbot / zope.browserpage_py_265_32 [35] winbot / zope.configuration_py_265_32 [36] winbot / zope.deprecation_py_265_32 [37] winbot / zope.dottedname_py_265_32 [38] winbot / zope.dublincore_py_265_32 [39] winbot / zope.error_py_265_32 [40] winbot / zope.filerepresentation_py_265_32 [41] winbot / zope.formlib_py_265_32 [42] winbot / zope.intid_py_265_32 [43] winbot / zope.mimetype_py_265_32 [44] winbot / zope.minmax_py_265_32 [45] winbot / zope.pluggableauth_py_265_32 [46] winbot / zope.principalannotation_py_265_32 [47] winbot / zope.renderer_py_265_32 [48] winbot / zope.securitypolicy_py_265_32 [49] winbot / zope.sendmail_py_265_32 [50] winbot / zope.structuredtext_py_265_32 [51] winbot / zope.testing_py_265_32 [52] winbot / zope.testrunner_py_265_32 [53] winbot / zope.traversing_py_265_32 Looks like PyPI was down? All the failures are due to failing bootstrap.py: No local packages or download links found for zc.buildout Note how the latest v1 bootstrap fails to exit with a non-zero status in this case. 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: 6, OK: 8
On Fri, Apr 05, 2013 at 01:00:02AM +, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-04-03 00:00:00 UTC and 2013-04-04 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 # 223 10 packages fail in the latest build due to missing persistent: - test-ztk-zope.traversing - test-ztk-zope.site - test-ztk-zope.session - test-ztk-zope.index - test-ztk-zope.container - test-ztk-zope.intid - test-ztk-zope.dublincore - test-ztk-zope.catalog - test-ztk-zope.annotation - test-ztk-zope.keyreference There were only 5 last time: - test-ztk-zope.traversing - test-ztk-zope.session - test-ztk-zope.container - test-ztk-zope.catalog - test-ztk-zope.dublincore [2]winbot / ZODB_dev py_265_win32 [3]winbot / ZODB_dev py_265_win64 [4]winbot / ZODB_dev py_270_win32 *sigh* I managed not to notice that there was a second doctest assertion needing the same change 20 lines below the one I fixed. [5]winbot / z3c.contents_py_265_32 ValueError: _p_serial must be an 8-character bytes array [6]winbot / z3c.form_py_265_32 Missing Required input is missing for Address. 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: 8, OK: 8
On Thu, Apr 04, 2013 at 01:46:00PM -0400, Tres Seaver wrote: On 04/03/2013 09:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 222 https://mail.zope.org/pipermail/zope-tests/2013-April/073673.html Ugh. I think Marius had some clue to this one, but I'm baffled. I suspected https://bugs.launchpad.net/zc.buildout/+bug/257555 IIRC BTrees setup_requires=['persistent'] in setup.py. When mr.developer instructs buildout to develop BTrees, setuptools end up downloading persistent-*.egg in the source directory, outside buildout's jurisdiction, and then, somehow, buildout assumes that persistent is installed system-wide and doesn't add the persistent egg to the sys.path of the generated bin/test-ztk-whatever script. That's just a guess, I haven't spent any appreciable time debugging this. [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073684.html [3]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073685.html [4]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073686.html [5]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073687.html Looks like more renormalizer fun. Yes. I think I got it this time. But I thought so the previous two times too. ;-) [8]FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073675.html Network failure during 'git pull'. Last zope.security 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 )
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 nore...@zope.org
[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
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 nore...@zope.org [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: 4, OK: 12
On Tue, Mar 26, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 213 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 Same old failures I can't reproduce. :( [4]winbot / zope.app.authentication_py_265_32 Last build 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 )
Re: [Zope-dev] zope-tests - FAILED: 14, OK: 12
On Mon, Mar 25, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Repository policy check found errors in 497 projects [3]Total languishing bugs for zope2: 1 [4]Total languishing bugs for zope: 68 [5]Total languishing bugs for zopeapp: 1 [6]Total languishing bugs for zopetoolkit: 195 Did not read. [2]Still Failing - zopetoolkit_trunk - Build # 212 Same four failures. [7]winbot / z3c.baseregistry_py_265_32 Last build successful. [8]winbot / z3c.contents_py_265_32 Same _p_serial issue. [9]winbot / z3c.form_py_265_32 Same missing error. [10] winbot / zc.configuration_py_265_32 Last build successful. [11] winbot / zope.app.authentication_py_265_32 Buildout tried to upgrade distribute 0.6.35 to 0.6.14 and fell over with IOError: [Errno 13] Permission denied: 'c:\\buildslave\\zope.app.authentication\\build\\bin\\buildout.exe' for two builds in a row. This is bootstrap.py for buildout 2.0. distribute is pinned to 0.6.14 by the inclusion of http://download.zope.org/zopetoolkit/index/1.0/ztk-versions.cfg I guess it ought to be enough to override the distribute pin in zope.app.authentication's buildout.cfg [12] winbot / zope.app.locales_py_265_32 [13] winbot / zope.dublincore_py_265_32 [14] winbot / zope.size_py_265_32 Last build 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 )
Re: [Zope-dev] zope-tests - FAILED: 7, OK: 12
On Sun, Mar 24, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 211 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 Same old [4]winbot / z3c.json_py_265_32 Network error during git pull? fatal: read error: Invalid argument [5]winbot / zope.app.locales_py_265_32 [6]winbot / zope.processlifetime_py_265_32 [7]winbot / zope.processlifetime_py_265_32 New z3c.recipe.tag requires zc.buildout 2.0; zope.app.locales and zope.processfiletime need to upgrade or pin z3c.recipe.tag to 0.6. 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 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 )
Re: [Zope-dev] zope-tests - FAILED: 6, OK: 12
On Thu, Mar 21, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 208 Same four failures I can't reproduce. Can anyone? [2]winbot / z3c.contents_py_265_32 ValueError: _p_serial must be an 8-character bytes array deep in c:\eggs\zodb3-3.10.5-py2.6-win32.egg\ZODB\Connection.py, during layer setup. Actually let me paste the whole traceback: Traceback (most recent call last): File c:\eggs\zope.testrunner-4.3.3-py2.6.egg\zope\testrunner\runner.py, line 385, in run_layer setup_layer(options, layer, setup_layers) File c:\eggs\zope.testrunner-4.3.3-py2.6.egg\zope\testrunner\runner.py, line 681, in setup_layer layer.setUp() File c:\eggs\zope.app.testing-3.10.0-py2.6.egg\zope\app\testing\functional.py, line 336, in setUp self.config_file, product_config=self.product_config) File c:\eggs\zope.app.testing-3.10.0-py2.6.egg\zope\app\testing\functional.py, line 215, in __init__ self.app = Debugger(self.db, config_file) File c:\eggs\zope.app.debug-3.4.1-py2.6.egg\zope\app\debug\debug.py, line 37, in __init__ self.db = database(db) File c:\eggs\zope.app.appsetup-3.16.0-py2.6.egg\zope\app\appsetup\appsetup.py, line 147, in database notify(zope.processlifetime.DatabaseOpened(db)) File c:\eggs\zope.event-4.0.2-py2.6.egg\zope\event\__init__.py, line 31, in notify subscriber(event) File c:\eggs\zope.component-4.1.0-py2.6.egg\zope\component\event.py, line 27, in dispatch component_subscribers(event, None) File c:\eggs\zope.component-4.1.0-py2.6.egg\zope\component\_api.py, line 139, in subscribers return sitemanager.subscribers(objects, interface) File c:\eggs\zope.interface-4.0.5-py2.6-win32.egg\zope\interface\registry.py, line 323, in subscribers return self.adapters.subscribers(objects, provided) File c:\eggs\zope.interface-4.0.5-py2.6-win32.egg\zope\interface\adapter.py, line 601, in subscribers subscription(*objects) File c:\eggs\zope.app.appsetup-3.16.0-py2.6.egg\zope\app\appsetup\bootstrap.py, line 160, in bootStrapSubscriber db, connection, root, root_folder = getInformationFromEvent(event) File c:\eggs\zope.app.appsetup-3.16.0-py2.6.egg\zope\app\appsetup\bootstrap.py, line 145, in getInformationFromEvent root_folder = root.get(ZopePublication.root_name, None) File c:\eggs\zodb3-3.10.5-py2.6-win32.egg\ZODB\Connection.py, line 860, in setstate self._setstate(obj) File c:\eggs\zodb3-3.10.5-py2.6-win32.egg\ZODB\Connection.py, line 915, in _setstate obj._p_serial = serial ValueError: _p_serial must be an 8-character bytes array So that's, you know, *interesting*. I've no clue, and also cannot reproduce locally. I wish we knew what `serial` actually was. (Silly idea: log all exceptions in tests to a Sentry instance, then we could browse around and inspect stack locals. Hm, maybe s/silly/genius/.) [3]winbot / z3c.form_py_265_32 Actual failure in c:\buildslave\z3c.form\build\src\z3c\form\tests\..\group.txt: The test expects two field errors: Last Name: Required input is missing. Address: Required input is missing. it gets only one error: Last Name: Required input is missing. Oh, and I can't reproduce this by running tox in git master. [4]winbot / z3c.formui_py_265_32 [5]winbot / zope.datetime_py_265_32 [6]winbot / zope.i18n_py_265_32 Last builds successful for all three. 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: 6, OK: 12
On Thu, Mar 21, 2013 at 09:11:05AM +0200, Marius Gedminas wrote: I've no clue, and also cannot reproduce locally. I keep forgetting about bin/buildout prefer-final=false 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: 6, OK: 12
On Thu, Mar 21, 2013 at 10:17:43PM +0200, Marius Gedminas wrote: On Thu, Mar 21, 2013 at 09:11:05AM +0200, Marius Gedminas wrote: I've no clue, and also cannot reproduce locally. I keep forgetting about bin/buildout prefer-final=false Nope. Tried this on z3c.contents, z3c.form, and zope.traversing -- couldn't reproduce any of the failures. 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: 5, OK: 12
On Wed, Mar 20, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 207 Same four persistent import errors. Back in February I thought these were caused by an incorrect setup.py in ZODB. That's been fixed, yet the errors persist. And I can't reproduce them using upstream master checkouts of, e.g., zope.container or zope.traversal. [2]winbot / z3c.form_py_265_32 We're out of the lxml swamp and get exciting new failures! \r\n instead of \n [3]winbot / z3c.formui_py_265_32 Network error while fetching distribute during bootstrap. Aside: I sometimes hate how the new buildout 2.0 bootstrap.py always downloads distribute.py. It could at least use the buildout cache. [4]winbot / z3c.layer.ready2go_py_265_32 [5]winbot / z3c.pagelet_py_265_32 Last builds succeeded for both! 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: 5, OK: 12
On Wed, Mar 20, 2013 at 08:30:27AM +0100, Adam GROSZER wrote: On 03/20/2013 07:27 AM, Marius Gedminas wrote: [3]winbot / z3c.formui_py_265_32 Network error while fetching distribute during bootstrap. Aside: I sometimes hate how the new buildout 2.0 bootstrap.py always downloads distribute.py. It could at least use the buildout cache. pypi distribute download count is at *51*, and that's just the latest version. btw, I think earlier bootstraps too download setuptools/distribute ignoring the buildout cache. I have the recollection that earlier bootstraps always used my /usr/lib/python2.7/dist-packages/setuptools, while the new bootstrap always downloads (and then likes to upgrade from bootstrap-downloaded 0.6.35 to 0.6.28 from /usr/lib/python2.7 on the next bin/buildout run, unless you run it with -n or -o). 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: 5, OK: 12
On Wed, Mar 20, 2013 at 08:27:58AM +0200, Marius Gedminas wrote: On Wed, Mar 20, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 207 Same four persistent import errors. Back in February I thought these were caused by an incorrect setup.py in ZODB. That's been fixed, yet the errors persist. And I can't reproduce them using upstream master checkouts of, e.g., zope.container or zope.traversal. I cannot reproduce these from a zopetoolkit checkout either. [2]winbot / z3c.form_py_265_32 We're out of the lxml swamp and get exciting new failures! \r\n instead of \n Fixed. [3]winbot / z3c.formui_py_265_32 Network error while fetching distribute during bootstrap. Aside: I sometimes hate how the new buildout 2.0 bootstrap.py always downloads distribute.py. It could at least use the buildout cache. Checked for similar \r\n issues, found none. 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: 6, OK: 12
On Tue, Mar 19, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 206 - zope.traversing: ImportError: No module named persistent - zope.container: ImportError: No module named persistent.cPersistence - zope.dublincore: ImportError: No module named persistent - zope.catalog: ImportError: No module named persistent Most of these have BTrees in the traceback. [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.contents_py_265_32 [4]winbot / z3c.formui_py_265_32 [5]winbot / z3c.layer.ready2go_py_265_32 [6]winbot / z3c.pagelet_py_265_32 lxml. 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: 11, OK: 12
On Mon, Mar 18, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Repository policy check found errors in 487 projects The full log of errors can be found here: http://uter.gocept.com/~ctheune/report-2013-03-17T02:15:02.457592.txt; No it can't, uter.gocept.com is NXDOMAIN. [2]Still Failing - zopetoolkit_trunk - Build # 205 Still unreachable. [3]Total languishing bugs for zope2: 1 [4]Total languishing bugs for zope: 67 [5]Total languishing bugs for zopeapp: 1 [6]Total languishing bugs for zopetoolkit: 195 Didn't read. [7]winbot / z3c.contents_py_265_32 [8]winbot / z3c.form_py_265_32 [9]winbot / z3c.formui_py_265_32 [10] winbot / z3c.layer.ready2go_py_265_32 [11] winbot / z3c.pagelet_py_265_32 lxml. 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: 8, OK: 12
On Sun, Mar 17, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 204 Can't check, jenkins.starzel.de is not reachable (504 Gateway Time-out) [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 [4]winbot / z3c.form_py_265_32 [5]winbot / z3c.formui_py_265_32 [6]winbot / z3c.layer.ready2go_py_265_32 [7]winbot / z3c.pagelet_py_265_32 lxml [8]winbot / zope.viewlet_py_265_32 Last build 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 )
Re: [Zope-dev] zope-tests - FAILED: 8, OK: 12
On Sat, Mar 16, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 203 ERROR: git pull of 'zope.copypastemove' failed. ERROR: fatal: The remote end hung up unexpectedly Transient network failure? [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.formui_py_265_32 [4]winbot / z3c.layer.ready2go_py_265_32 [5]winbot / z3c.pagelet_py_265_32 lxml zope.wineggbuilder now has access to https://pypi.python.org/pypi/lxml, so this will be solved Real Soon Now! [6]winbot / zope.app.localpermission_py_265_32 [7]winbot / zope.site_py_265_32 Last build successful. [8]winbot / zope.viewlet_py_265_32 Needs the same kind of fixing that I did to zope.site yesterday, I just didn't get around to it. 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: 10, OK: 12
On Fri, Mar 15, 2013 at 01:00:01AM +, Zope tests summarizer wrote:
[1]Still Failing - zopetoolkit_trunk - Build # 202
Back to regular failures:
- test-ztk-zope.traversing
- test-ztk-zope.dublincore
- test-ztk-zope.container
- test-ztk-zope.catalog
ImportError: No module named persistent
ImportError: No module named persistent.dict
AttributeError: 'module' object (BTrees) has no attribute 'Interfaces'
ImportError: No module named persistent.cPersistence
ImportError: cannot import name
(zope.container._zope_container_contained.)ContainedProxyBase
These sound familiar.
[2]winbot / z3c.form_py_265_32
[3]winbot / z3c.form_py_265_32
[4]winbot / z3c.formui_py_265_32
[5]winbot / z3c.layer.ready2go_py_265_32
[6]winbot / z3c.pagelet_py_265_32
lxml
[7]winbot / zope.app.localpermission_py_265_32
https://github.com/zopefoundation/zope.app.localpermission does not have
a buildout.cfg
Lossy git conversion? A buildout.cfg existed in
http://zope3.pov.lt/trac/browser/zope.app.localpermission/trunk?rev=126937
It was created by an svn mv from zope.localpermission in r98059:
http://zope3.pov.lt/trac/log/zope.app.localpermission/trunk/buildout.cfg?rev=126937
[8]winbot / zope.app.wsgi_py_265_32
I misunderstood last time. *** empty log message *** does not mean
this is a clone of an empty repo. It's *the actual svn commit message*
of the last commit: http://zope3.pov.lt/trac/changeset/124092
The actual problem is
c:\Python26_32\python.exe bootstrap.py
Downloading
http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg
Traceback (most recent call last):
File bootstrap.py, line 257, in module
import zc.buildout.buildout
File
c:\temp\tmpjpk_wq\zc.buildout-2.0.1-py2.6.egg\zc\buildout\buildout.py, line
18, in module
import zc.buildout.easy_install
File
c:\temp\tmpjpk_wq\zc.buildout-2.0.1-py2.6.egg\zc\buildout\easy_install.py,
line 61, in module
pkg_resources.Requirement.parse('distribute')
AttributeError: 'NoneType' object has no attribute 'location'
Weird.
[9]winbot / zope.site_py_265_32
buildout fails with
We already have: zope.security 3.9.0
but zope.site 4.0.0a2.dev0 requires 'zope.security=4.0.0a3'.
[10] winbot / zope.viewlet_py_265_32
buildout fails with
We already have: zope.security 3.9.0
but zope.publisher 4.0.0a2 requires 'zope.security=4.0.0a1'.
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: 10, OK: 12
On Fri, Mar 15, 2013 at 09:39:16AM +0100, Wichert Akkerman wrote:
On Mar 15, 2013, at 07:57, Marius Gedminas mar...@gedmin.as wrote:
[8]winbot / zope.app.wsgi_py_265_32
I misunderstood last time. *** empty log message *** does not mean
this is a clone of an empty repo. It's *the actual svn commit message*
of the last commit: http://zope3.pov.lt/trac/changeset/124092
The actual problem is
c:\Python26_32\python.exe bootstrap.py
Downloading
http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg
Traceback (most recent call last):
File bootstrap.py, line 257, in module
import zc.buildout.buildout
File
c:\temp\tmpjpk_wq\zc.buildout-2.0.1-py2.6.egg\zc\buildout\buildout.py,
line 18, in module
import zc.buildout.easy_install
File
c:\temp\tmpjpk_wq\zc.buildout-2.0.1-py2.6.egg\zc\buildout\easy_install.py,
line 61, in module
pkg_resources.Requirement.parse('distribute')
AttributeError: 'NoneType' object has no attribute 'location'
Weird.
That is likely buildout 2 with an older bootstrap.py
Ah, of course. I got it mixed up with zope.app.http.
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: 6, OK: 12
On Thu, Mar 14, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 201 ZODB3 moved to github. I updated zopetoolkit's ztk-sources.cfg in svn. [2]winbot / z3c.contents_py_265_32 [3]winbot / zope.app.applicationcontrol_py_265_32 [4]winbot / zope.app.content_py_265_32 [5]winbot / zope.app.pagetemplate_py_265_32 lxml [6]winbot / zope.app.wsgi_py_265_32 https://github.com/zopefoundation/zope.app.wsgi was an empty repository at the time of that build. 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] Location of RelStorage
What's the official location of RelStorage? I see two source trees: * http://zope3.pov.lt/trac/browser/relstorage/trunk * https://github.com/zodb/relstorage They have the same commits (~1 year old). Note how the github repo is not part of the zopefoundation organisation. 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: 56, OK: 12
On Wed, Mar 13, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 200 Picked: zope.security = 4.0.0b1 [2]winbot / z3c.baseregistry_py_265_32 [8]winbot / z3c.json_py_265_32 [9]winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsonrpcproxy_py_265_32 [11] winbot / z3c.jsontree_py_265_32 [12] winbot / z3c.language.negotiator_py_265_32 [13] winbot / z3c.language.session_py_265_32 [14] winbot / z3c.language.switch_py_265_32 [15] winbot / z3c.layer.ready2go_py_265_32 [16] winbot / z3c.layer.ready2go_py_265_32 [17] winbot / z3c.pagelet_py_265_32 [18] winbot / z3c.pagelet_py_265_32 [19] winbot / z3c.pdftemplate_py_265_32 [20] winbot / z3c.recipe.paster_py_265_32 [21] winbot / z3c.tabular_py_265_32 [22] winbot / z3c.viewtemplate_py_265_32 [23] winbot / z3c.xmlhttp_py_265_32 [24] winbot / z3c.zrtresource_py_265_32 [25] winbot / zc.i18n_py_265_32 [27] winbot / zc.ngi_py_265_32 [28] winbot / zc.resourcelibrary_py_265_32 [29] winbot / zc.table_py_265_32 [31] winbot / zope.app.basicskin_py_265_32 [32] winbot / zope.app.broken_py_265_32 [33] winbot / zope.app.component_py_265_32 [34] winbot / zope.app.container_py_265_32 [35] winbot / zope.app.debug_py_265_32 [36] winbot / zope.app.dependable_py_265_32 [37] winbot / zope.app.error_py_265_32 [38] winbot / zope.app.exception_py_265_32 [39] winbot / zope.app.folder_py_265_32 [40] winbot / zope.app.form_py_265_32 [41] winbot / zope.app.generations_py_265_32 [43] winbot / zope.app.i18n_py_265_32 [44] winbot / zope.app.interface_py_265_32 [45] winbot / zope.app.locales_py_265_32 [46] winbot / zope.app.localpermission_py_265_32 [47] winbot / zope.app.principalannotation_py_265_32 [49] winbot / zope.app.publisher_py_265_32 [50] winbot / zope.app.rotterdam_py_265_32 [51] winbot / zope.app.schema_py_265_32 [52] winbot / zope.app.security_py_265_32 [53] winbot / zope.app.session_py_265_32 [54] winbot / zope.app.testing_py_265_32 [55] winbot / zope.app.zcmlfiles_py_265_32 [56] winbot / zope.app.zopeappgenerations_py_265_32 Moved to Github [3]winbot / z3c.contents_py_265_32 [4]winbot / z3c.contents_py_265_32 [5]winbot / z3c.form_py_265_32 [6]winbot / z3c.formui_py_265_32 [7]winbot / z3c.formui_py_265_32 lxml [26] winbot / zc.monitor_py_265_32 svn can't handle symlinks (bootstrap.py - .bootstrap/bootstrap.py, where .bootstrap is an svn:external). Anyway, it's been moved to github with the rest of 'em, and I'm not sure why I didn't get an error about _that_. Oh, because a copy of the source tree still exists in svn. [30] winbot / zope.app.authentication_py_265_32 Same old unicode principal id thing [42] winbot / zope.app.http_py_265_32 [48] winbot / zope.app.publication_py_265_32 I thought Adam reconfigured winbot to use the package's own bootstrap.py? 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: 10, OK: 12
On Tue, Mar 12, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 199 Error: Picked: zope.security = 4.0.0b1 [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 [4]winbot / z3c.formui_py_265_32 [5]winbot / z3c.layer.ready2go_py_265_32 [7]winbot / z3c.pagelet_py_265_32 lxml Fix for this is in progress AFAIU. Last I heard Adam was waiting for some Rackspace credentials so he can make a backup of the winbot VM before messing with compilers. [6]winbot / z3c.menu.ready2go_py_265_32 Moved to github; zope.winbot fix pushed [8]winbot / zope.app.authentication_py_265_32 Unicode principal names [9]winbot / zope.app.http_py_265_32 AttributeError: 'NoneType' object has no attribute 'group' inside zc.buildout-1.7.1-py2.6.egg\zc\buildout\easy_install.py I've a sense of deja vu about this, but I don't remember if I got to the root of the problem when I saw it first. [10] winbot / zope.app.publication_py_265_32 Same as [9] 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] Version Numbering for Ported Packages
On Tue, Mar 12, 2013 at 08:35:46AM -0400, Stephan Richter wrote:
On Monday, March 11, 2013 10:09:51 PM Tres Seaver wrote:
Also, is somebody running / reporting tests via
Travis? Where are those results going?
They should be running for all packages. I have turned off any notifications
pending an agreement of where we want the reports to go. The easiest thing
right now would be a Wiki page that shows the status icon for each package.
FWIW whenever I get a failure notification from Travis about a package
that doesn't have a .travis.yml, I uncheck the Active checkbox in Github
repo settings.
Packages without a .travis.yml are treated as Ruby packages, and,
obviously, always fail.
Note: I think most packages pass fine under Travis, but some are failing for
some obscure reasons.
An overview would be good.
I could add a Travis column to http://zope3.pov.lt/py3/, I suppose. The
image URLs are trivial to generate, assuming Travis knows about every ZF
repo on Github:
https://api.travis-ci.org/zopefoundation/${reponame}.png?branch=master
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: 11, OK: 12
On Thu, Mar 07, 2013 at 10:05:30AM +0100, Adam GROSZER wrote: On 03/07/2013 09:51 AM, Marius Gedminas wrote: On Thu, Mar 07, 2013 at 01:00:02AM +, Zope tests summarizer wrote: Oh, right, the bootstrap step is c:\Python26_32\python.exe c:\buildmaster\bootstrap.py everything is clear now. (Including the fact that most packages I try to build locally fail because their bootstrap is too old. I was wondering why they didn't fail en-masse on winbot.) Ohh yeah, there's some crap laying around regarding bootstraps. This was the easy solution. Now that we seem to care about the packages again I could switch it back to the package's own bootstrap. Eventually, yes. Let's not do that before we find a volunteer who will check out every package tested by buildout and see if bootstrap.py needs to be outdated. Sounds like a fun project for an afternoon. 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: 11, OK: 12
On Thu, Mar 07, 2013 at 10:51:14AM +0200, Marius Gedminas wrote: [9]winbot / zope.app.pagetemplate_py_265_32 [11] winbot / zope.browserpage_py_265_32 \r\n I made the tests accept \r\n as correct. I'm not sure that's the right thing to do. Perhaps page templates, when given a file on disk with \r\n, should normalize the line endings to \n? Opinions? 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: 16, OK: 12
On Wed, Mar 06, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [12] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073081.html zope.app.http wants zope.app.wsgi.testlayer. zope.app.wsgi 4.0.0a3 introduces a new setuptools extra [testlayer] that has all the dependencies required for zope.app.wsgi.testlayer. I fixed zope.app.http's buildout.cfg to pin zope.app.wsgi 4.0dev for now. 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: 16, OK: 12
On Wed, Mar 06, 2013 at 02:44:19PM +0200, Marius Gedminas wrote: On Wed, Mar 06, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [12] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073081.html zope.app.http wants zope.app.wsgi.testlayer. zope.app.wsgi 4.0.0a3 introduces a new setuptools extra [testlayer] that has all the dependencies required for zope.app.wsgi.testlayer. I fixed zope.app.http's buildout.cfg to pin zope.app.wsgi 4.0dev for now. zope.app.publication had the same issue, fixed in the same way. 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: 16, OK: 12
On Wed, Mar 06, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [6]winbot / z3c.language.switch_py_265_32 Missing extra_requires of zope.app.testing for the [test] extra. Fixed. 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: 18, OK: 13
On Mon, Mar 04, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Repository policy check found errors in 436 projects Contains a broken link to http://uter.gocept.com/~ctheune/report-2013-03-03T02:15:02.792640.txt (Host uter.gocept.com not found: 3(NXDOMAIN)) I suspect the script doesn't know about MOVED_TO_GITHUB and therefore complains about missing LICENCE.txt etc. [2]Still Failing - zopetoolkit_trunk - Build # 190 Early in the build there's + ./bin/develop up -f /tmp/hudson7093928157358980278.sh: 1: ./bin/develop: not found what's that about? It doesn't seem to break the build (and the develop script is, apparently, generated later and then executed successfully). The failure is here: + ./bin/buildout -t 3 -v -c development-python.cfg While: Initializing. Error: Couldn't open /home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/development-python.cfg [3]Total languishing bugs for zope: 69 I think it was the first time I read this summary (shame on me etc. etc.), it was rather interesting. I closed https://bugs.launchpad.net/z3c.form/+bug/1125906 (please move to github) [4]Total languishing bugs for zopeapp: 1 [5]Total languishing bugs for zopetoolkit: 205 I closed https://bugs.launchpad.net/zope.datetime/+bug/642474 (please make setup.py test work[1]), because it was fixed during the porting effort. [1] Here I use quotation marks for my paraphrasings instead of actual citations. Apologies for playing fast an loose with punctuation. There are a lot of Turn package documentation into Sphinx style bugs. I think a http://zope3.pov.lt/py3/ style summary page might be more useful for tracking this, but maybe that's just me. I closed https://bugs.launchpad.net/zope.interface/+bug/140875 because binary Windows eggs for zope.interface exist (and have existed for quite a while). Closed https://bugs.launchpad.net/zope.interface/+bug/911995 (class-advice decorators should fail loudly, not silently, in Python 3) because it's been fixed in 4.0.0 AFAIU. Marked https://bugs.launchpad.net/zope.interface/+bug/1090762 as incomplete because it's about zope.interface 4.0.2 and now 4.0.5 is out, and also because I don't understand what the problem is. My, those Turn package documentation into Sphinx style bugs aren't helpful at all. Closed https://bugs.launchpad.net/zope.sequencesort/+bug/642481 (make setup.py test work) by applying the supplied patch. This also made tests fail under Python 3 and confirmed the recent report about the port being somewhat incomplete. tox/detox make it easy to not notice when your test setup is incorrect (e.g. no tests are run, or test failures do not cause sys.exit(1)). I tripped on this thing with zope.testrunner once. I tried to fix the tests under Python 3.[23], but got bogged down in the various TypeError: unorderable types: dict() dict() errors. Help? Closed https://bugs.launchpad.net/zope.session/+bug/353647 (zope.session 3.6 doesn't work on Python 2.4) because there's a comment claiming 3.6.1 fixed that. In 2009. And nobody ever contradicted. Closed https://bugs.launchpad.net/zope.structuredtext/+bug/642481 because it's been fixed. Reassigned 16 zope.testing bugs dealing with the test runner to zope.testrunner. Noticed that I cannot change the importance field of zope.testrunner's bugs (I can change it for zope.testing's bugs). *whew* That was a bit depressing. [6]winbot / z3c.contents_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.formui_py_265_32 [10] winbot / z3c.pagelet_py_265_32 lxml [9]winbot / z3c.language.switch_py_265_32 ImportError: No module named (zope.app.)testing [11] winbot / zc.resourcelibrary_py_265_32 WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-l9qzwt' [12] winbot / zope.app.authentication_py_265_32 Unicode principal IDs [13] winbot / zope.app.http_py_265_32 [15] winbot / zope.app.publication_py_265_32 ImportError: No module named webtest [14] winbot / zope.app.pagetemplate_py_265_32 \r\n [16] winbot / zope.app.renderer_py_265_32 Initialized empty Git repository in c:/buildslave/zope.app.renderer/source/.git/ fatal: remote error: Repository not found. [17] winbot / zope.browserpage_py_265_32 \r\n [18] winbot / zope.formlib_py_265_32 Moved to github a while ago 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: 15, OK: 12
On Tue, Mar 05, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 191 Error: Couldn't open /home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/development-python.cfg [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 [4]winbot / z3c.formui_py_265_32 [7]winbot / z3c.pagelet_py_265_32 lxml [5]winbot / z3c.language.switch_py_265_32 ImportError: No module named (zope.app.)testing [6]winbot / z3c.menu.ready2go_py_265_32 [15] winbot / zope.formlib_py_265_32 Moved to github. [8]winbot / zc.resourcelibrary_py_265_32 WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-l9qzwt' Strange. Adam rebooted winbot last morning, so it's not some hung old process holding a file open. [9]winbot / zope.app.authentication_py_265_32o Unicode principal IDs [10] winbot / zope.app.http_py_265_32 [12] winbot / zope.app.publication_py_265_32 ImportError: No module named webtest [11] winbot / zope.app.pagetemplate_py_265_32 [14] winbot / zope.browserpage_py_265_32 \r\n [13] winbot / zope.app.renderer_py_265_32 It's been renamed to zope.renderer; winbot needs to be told (and I'd like a BBB release on PyPI that urges every user to change their imports via DeprecationWarnings) 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: 15, OK: 12
On Sun, Mar 03, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 189 Error: Picked: zope.untrustedpython = 4.0.0 mr.developer: Can't switch package 'z3c.recipe.compattest' to '^/z3c.recipe.compattest/trunk' because it's dirty. [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 [4]winbot / z3c.formui_py_265_32 [7]winbot / z3c.pagelet_py_265_32 No lxml [5]winbot / z3c.language.switch_py_265_32 No zope.app.testing [6]winbot / z3c.layer.pagelet_py_265_32 No webtest [8]winbot / zc.resourcelibrary_py_265_32 WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-rz412g' [9]winbot / zope.app.authentication_py_265_32 The unicode thing [10] winbot / zope.app.http_py_265_32 No zope.testbrowser.wsgi [11] winbot / zope.app.pagetemplate_py_265_32 \r\n [12] winbot / zope.app.publication_py_265_32 No zope.testbrowser.wsgi [13] winbot / zope.app.renderer_py_265_32 Initialized empty Git repository in c:/buildslave/zope.app.renderer/source/.git/ fatal: remote error: Repository not found. zope.app.renderer doesn't exist on github! But http://zope3.pov.lt/trac/browser/zope.app.renderer/trunk/MOVED_TO_GITHUB claims it does. My guess: some automated script is missing some error checking (e.g. for github said repository was not created). Stephan, do you still have a copy of that git repo on your laptop? [14] winbot / zope.browserpage_py_265_32 \r\n [15] winbot / zope.formlib_py_265_32 Moved to github; I fixed the wineggbuilder URL yesterday but I don't know the procedure for svnuping and restarting winbot. 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: 18, OK: 12
On Sat, Mar 02, 2013 at 01:00:02AM +, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-02-28 00:00:00 UTC and 2013-03-01 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 # 188 These look like error messages: Error: Picked: zope.untrustedpython = 4.0.0 mr.developer: Can't switch package 'z3c.recipe.compattest' to '^/z3c.recipe.compattest/trunk' because it's dirty. mr.developer: There have been errors, see messages above. /tmp/hudson5245049843336471917.sh: 1: ./bin/test-ztk: not found [2]winbot / z3c.contents_py_265_32 [3]winbot / z3c.form_py_265_32 [4]winbot / z3c.formui_py_265_32 [8]winbot / z3c.pagelet_py_265_32 No lxml. [5]winbot / z3c.language.switch_py_265_32 from zope.app.testing import placelesssetup ImportError: No module named testing [6]winbot / z3c.layer.pagelet_py_265_32 [7]winbot / z3c.layer.pagelet_py_265_32 File c:\eggs\zope.testbrowser-4.0.2-py2.6.egg\zope\testbrowser\wsgi.py, line 21, in module from webtest import TestApp ImportError: No module named webtest Missing install_requires in zope.testbrowser? [9]winbot / z3c.recipe.paster_py_265_32 The usual opaque dependency churn; I didn't get around to fixing this yesterday. Now fixed (again, only until next time dependencies of dependencies change). [10] winbot / zc.catalog_py_265_32 [11] winbot / zc.queue_py_265_32 Moved to github. [12] winbot / zc.resourcelibrary_py_265_32 Bootstrap fails because WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-rz412g' [13] winbot / zope.app.authentication_py_265_32 Same unicode thing. [14] winbot / zope.app.http_py_265_32 from zope.testbrowser.wsgi import Layer as WSGILayer, AuthorizationMiddleware ImportError: No module named testbrowser.wsgi [15] winbot / zope.app.pagetemplate_py_265_32 Same \r\n issue. [16] winbot / zope.app.publication_py_265_32 ImportError: No module named testbrowser.wsgi [17] winbot / zope.browserpage_py_265_32 Same \r\n issue. [18] winbot / zope.formlib_py_265_32 Error: Couldn't open c:\buildslave\zope.formlib\build\buildout.cfg Probably moved to github. 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] procedures for moving package to github and porting to Python 3
On Fri, Mar 01, 2013 at 09:51:05AM +0100, Jan-Wijbrand Kolman wrote: Disclaimer: it's been a while since I actively followed zope-dev and grok-dev. So, please forgive me my ignorance. A single up-to-date web page sure beats reading months of list archives. Spurred by the recent ZTK-2.0 discussion, I'm trying to get back on track on the topics of 1) migrating package to github and 2) porting packages to Python 3. As a first step, I'd like to get the packages directly related to Grok moved over to github. Could someone perhaps tell me if there's a guideline document, some kind of recipe, or perhaps a conclusive posting on the mailinglist on how to proceed on this topic? My attempt at this: https://gist.github.com/mgedmin/4944724 AFAIK Stephan migrated most of the zope.* packages using this process. 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] procedures for moving package to github and porting to Python 3
On Fri, Mar 01, 2013 at 11:24:31AM +0100, Jan-Wijbrand Kolman wrote: On 3/1/13 10:17 AM, Marius Gedminas wrote: My attempt at this: https://gist.github.com/mgedmin/4944724 AFAIK Stephan migrated most of the zope.* packages using this process. Stephan tells me there are scripts at https://github.com/zopefoundation/zope.githubsupport that can do the entire process (create repo, convert history, upload it), if you've the right permissions on Github (few people do). So perhaps the easiest thing is to ask for the package to be converted. 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: 22, OK: 12, UNKNOWN: 2
On Thu, Feb 28, 2013 at 07:15:57AM -0500, Stephan Richter wrote: On Thursday, February 28, 2013 09:00:30 AM Marius Gedminas wrote: [9]winbot / z3c.form_py_265_32 [10] winbot / z3c.formui_py_265_32 No lxml on winbot So we have to solve this issue. I cannot declare lxml=2.3 anymore, because only lxml 3.0+ supports Python 3. If we want to keep supporting Windows, someone must sign up to create Windows binaries. I filed a bug: https://bugs.launchpad.net/lxml/+bug/1135686 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: 22, OK: 12, UNKNOWN: 2
On Thu, Feb 28, 2013 at 09:00:30AM +0200, Marius Gedminas wrote: On Thu, Feb 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 186 Same six failures, caused by ImportError: No module named persistent inside BTrees. Weird. *puts brown paper bag over his head* So, it turns out install_requires=[ 'lots', 'of, 'packages', ] + ['one extra'] if PY3 else [], doesn't group the way I expected it to group. Should be fixed in ZODB's py3 branch. Kudos to Gediminas Paulauskas for spotting this. 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: 15, OK: 17, UNKNOWN: 2
New issues: - ZTK drops zope.untrustedpython, zope.pagetemplate pulls it back in - zope.testbrowser.wsgi disappeared?! The usual suspects: - lxml for Windows - authentication: str vs unicode - newlines on Windows: should page templates normalize to \n? - z3c.recipe.paster still fragile - moves to github cause temporary churn On Fri, Mar 01, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]Still Failing - zopetoolkit_trunk - Build # 187 Build # 188 fails with Error: Picked: zope.untrustedpython = 4.0.0 while Installing 'zope.pagetemplate[test,untrusted]', 'zope.testrunner'. [2]UNKNOWN : Zope-trunk Python-2.6.8 : Linux [3]UNKNOWN : Zope-trunk Python-2.7.3 : Linux Waiting for buildbot owners to react to Zope's migration to Github. [4]winbot / z3c.formui_py_265_32 No lxml on winbot [5]winbot / z3c.layer.ready2go_py_265_32 Moved to github. [6]winbot / z3c.recipe.paster_py_265_32 This nonsense again. Argh. AFAIR AttributeError: 'NoneType' object has no attribute 'location' inside zc.buildout-1.7.1 (not 2.0!) means some of z3c.recipe.paster's dependencies used to depend on WebTest, and now it doesn't any more, so you have to manually update the test environment description because I'm too shtoopid to do that for you, and also too shtoopid to emit a clear error message hurr durr. [7]winbot / z3c.testing_py_265_32 Moved to github; last build already green. [8]winbot / zc.resourcelibrary_py_265_32 Moved to github. [9]winbot / zope.app.authentication_py_265_32 [10] winbot / zope.app.authentication_py_265_32 Same Unicode issues. [11] winbot / zope.app.http_py_265_32 Whoa. Test-module import failures: Module: zope.app.http.tests.test_put Traceback (most recent call last): File c:\buildslave\zope.app.http\build\src\zope\app\http\tests\test_put.py, line 28, in module from zope.app.wsgi.testlayer import BrowserLayer File c:\eggs\zope.app.wsgi-4.0.0a1.dev-py2.6.egg\zope\app\wsgi\testlayer.py, line 19, in module from zope.testbrowser.wsgi import Layer as WSGILayer, AuthorizationMiddleware ImportError: No module named testbrowser.wsgi [12] winbot / zope.app.pagetemplate_py_265_32 Same \r\n issues. [13] winbot / zope.app.publication_py_265_32 ImportError: No module named testbrowser.wsgi [14] winbot / zope.browserpage_py_265_32 Same \r\n issues. [15] winbot / zope.formlib_py_265_32 Moved to github. [16] winbot / zope.generations_py_265_32 [17] winbot / zope.ptresource_py_265_32 Moved to github; last build already green. 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: 21, OK: 15, UNKNOWN: 1
On Wed, Feb 27, 2013 at 11:52:56AM +0100, Patrick Gerken wrote: Both the daily zope app tests and the zope app tests that run with each commits have been deactivated. And Marius, thanks for dedication to look into the errors each day! I tricked myself into looking at this task as a way to play with my new toy https://gist.github.com/mgedmin/4995950 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] ZTK 2.0 process
On Wed, Feb 27, 2013 at 11:04:46AM -0500, Sebastien Douche wrote: 2. z3c.recipe.compattest and zc.recipe.testrunner doesn't work with Buildout 2. The latter has been fixed in zc.recipe.testrunner 2.0.0. 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: 21, OK: 19
On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote: On Tue, Feb 26, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.contents_py_265_32 There's this lovely bit at the beginning I don't remember from before, but it's not counted as a test failure: ZopeXMLConfigurationError: File c:\buildslave\z3c.contents\build\src\z3c\contents\ftesting.zcml, line 41.2-41.32 ZopeXMLConfigurationError: File c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51 WindowsError: [Error 3] The system cannot find the path specified: u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*' ... [11] winbot / z3c.layer.ready2go_py_265_32 [12] winbot / z3c.layer.ready2go_py_265_32 ZopeXMLConfigurationError: File c:\buildslave\z3c.layer.ready2go\build\src\z3c\layer\ready2go\ftesting.zcml, line 62.2-62.32 ZopeXMLConfigurationError: File c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51 WindowsError: [Error 3] The system cannot find the path specified: u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*' Okay, this does cause a test failure. Scratch that, a layer setup failure. Broken z3c.form release that's missing some locales? Some packages have special build steps (compile *.mo or something) before you're supposed to do setup.py sdist register upload. I've released z3c.form 3.0.0a2 with the missing locale files. Looks like it was a simple case of an incomplete MANIFEST.in [13] winbot / z3c.recipe.paster_py_265_32 Error: Couldn't find a distribution for 'beautifulsoup4'. Fixed. Marius three fixes before breakfast 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: 21, OK: 19
On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote: [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.contents_py_265_32 There's this lovely bit at the beginning I don't remember from before, but it's not counted as a test failure: ZopeXMLConfigurationError: File c:\buildslave\z3c.contents\build\src\z3c\contents\ftesting.zcml, line 41.2-41.32 ZopeXMLConfigurationError: File c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51 WindowsError: [Error 3] The system cannot find the path specified: u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*' and then we have the form id name vs form name id in README.txt that I cannot reproduce. Figured out why: I need to bin/buildout -n buildout:prefer-final=true and then I can reproduce this fine. [9]winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsontree_py_265_32 Same old Invalid request id returned. Because request ID is None in the response, and there's an error message in the JSON about 'TypeError: expecting a bytes object, got unicode'. This error is caused by zope.publisher 4.0.0a1: bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes the test pass, while bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes them fail. 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: 21, OK: 19
On Tue, Feb 26, 2013 at 02:41:02PM +0200, Marius Gedminas wrote: On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote: [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.contents_py_265_32 There's this lovely bit at the beginning I don't remember from before, but it's not counted as a test failure: ZopeXMLConfigurationError: File c:\buildslave\z3c.contents\build\src\z3c\contents\ftesting.zcml, line 41.2-41.32 ZopeXMLConfigurationError: File c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51 WindowsError: [Error 3] The system cannot find the path specified: u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*' and then we have the form id name vs form name id in README.txt that I cannot reproduce. Figured out why: I need to bin/buildout -n buildout:prefer-final=true and then I can reproduce this fine. Fixed. [9]winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsontree_py_265_32 Same old Invalid request id returned. Because request ID is None in the response, and there's an error message in the JSON about 'TypeError: expecting a bytes object, got unicode'. This error is caused by zope.publisher 4.0.0a1: bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes the test pass, while bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes them fail. Not fixed: going to lunch. (also, I need to review the changes in zope.publisher to see why it started complaining _now_) 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: 21, OK: 19
On Tue, Feb 26, 2013 at 08:48:10AM -0500, Stephan Richter wrote: This brings up a bigger question: Even though, most ported packages are fully Python 3 compatible, they might depend on packages that are not ready to get a final release. Those two are: * zope.security 4.0.0 (pending PyPy support from Tres) * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) Any package that depends directly or indirectly on those two packages has an alpha release right now. Strictly speaking this is not necessary for any package not depending on ZODB (ZODB is special because the dep changes from ZODB3 to ZODB). If it is okay with everyone, we could change the releases to their final version numbers with the understanding that Python 3 support will not be available until all dependencies have their final release. Python 2 should work just fine once we get the trunk builds back to green. I'm not a fan of non-alpha versions of packages depending on alpha versions of other packages, so -0.5. 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: 21, OK: 15, UNKNOWN: 1
On Wed, Feb 27, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]FAILED (failures=1) : Zope-trunk Python-2.7.3 : Linux Failure in test test_combined_scored_search_planned (Products.ZCatalog.tests.test_catalog.TestScoring) Traceback (most recent call last): File /home/stefan/autotest/temp/python27-zope214all/eggs/Products.ZCatalog-3.0-py2.7.egg/Products/ZCatalog/tests/test_catalog.py, line 1099, in test_combined_scored_search_planned self.assertEqual(brains[0].title, '111') AssertionError: '11' != '111' [2]Still Failing - zopetoolkit_trunk - Build # 185 Build #186 has failures in - test-ztk-zope.traversing - test-ztk-zope.dublincore - test-ztk-zope.container - test-ztk-zope.component - test-ztk-zope.catalog - test-ztk-zope.ramcache All of them are variations of ImportError: No module named persistent which is sort of surprising, given Getting required 'persistent' required by ZODB 4.0.0dev. We have a develop egg: persistent 4.0.7dev [3]Still Failing - zopetoolkit_trunk_app - Build # 167 Build #168: /tmp/hudson2996479762744665535.sh: 1: ./bin/test-zopeapp: not found and I just noticed, early on there's + ./bin/develop up -f /tmp/hudson2610355406837563482.sh: 1: ./bin/develop: not found [4]winbot / z3c.authenticator_py_265_32 Same Unicode prefix thing. [5]winbot / z3c.contents_py_265_32 Moved to github. [6]winbot / z3c.form_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.formui_py_265_32 Same: failure to build lxml. [9]winbot / z3c.jsonrpc_py_265_32 svn step failed with exceptions.WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\buildslave\\z3c.jsonrpc\\build' [10] winbot / z3c.jsontree_py_265_32 Last build is successful! [11] winbot / zc.resourcelibrary_py_265_32 buildout step failed with WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-eex7yk' [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.authentication_py_265_32 Moved to github [14] winbot / zope.app.pagetemplate_py_265_32 Same \r\n differences. [15] winbot / zope.app.wsgi_py_265_32 Same PEP- violation. [16] winbot / zope.browserpage_py_265_32 Same \r\n differences. [17] winbot / zope.generations_py_265_32 [18] winbot / zope.ptresource_py_265_32 [19] winbot / zope.ptresource_py_265_32 Moved to github. [20] winbot / ztk_11 py_254_win32 [21] winbot / ztk_11 py_265_win64 [22] winbot / ztk_11 py_270_win64 Error: Couldn't install: coverage 3.5.3 (winbot compiler troubles that I'm not qualified to debug) 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: 21, OK: 15, UNKNOWN: 1
On Wed, Feb 27, 2013 at 08:55:21AM +0200, Marius Gedminas wrote: [3]Still Failing - zopetoolkit_trunk_app - Build # 167 Build #168: /tmp/hudson2996479762744665535.sh: 1: ./bin/test-zopeapp: not found Given http://zope3.pov.lt/trac/changeset/129871/zopetoolkit (aka remove all traces of zopeapp including test-zopeapp) this job should be disabled. [5]winbot / z3c.contents_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.authentication_py_265_32 [18] winbot / zope.ptresource_py_265_32 [19] winbot / zope.ptresource_py_265_32 Moved to github. These are already corrected in SVN. 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: 21, OK: 19
On Tue, Feb 26, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
This is the summary for test reports received on the
zope-tests list between 2013-02-24 00:00:00 UTC and 2013-02-25 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 # 184
IOError: [Errno 2] No such file or directory:
'/home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.app.wsgi/setup.py'
I see two other zope.app packages also moved to Github:
zope.app.http
zope.app.appsetup
I've updated all three in zopeapp-sources.cfg.
[2]Still Failing - zopetoolkit_trunk_app - Build # 166
Same.
[3]winbot / z3c.authenticator_py_265_32
[4]winbot / z3c.authenticator_py_265_32
There's an echo? Anyway, same old
Failed example:
p.password
Expected:
u'secret'
Got:
'secret'
and I'd fix it if I knew whether passwords ought to be unicode or byte
strings.
[5]winbot / z3c.contents_py_265_32
[6]winbot / z3c.contents_py_265_32
There's this lovely bit at the beginning I don't remember from before,
but it's not counted as a test failure:
ZopeXMLConfigurationError: File
c:\buildslave\z3c.contents\build\src\z3c\contents\ftesting.zcml, line
41.2-41.32
ZopeXMLConfigurationError: File
c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51
WindowsError: [Error 3] The system cannot find the path specified:
u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*'
and then we have the form id name vs form name id in README.txt that
I cannot reproduce.
[7]winbot / z3c.form_py_265_32
Winbot failed to build lxml:
Getting distribution for 'lxml==3.1.0'.
Building lxml version 3.1.0.
Building without Cython.
ERROR: 'xslt-config' is not recognized as an internal or external command,
operable program or batch file.
** make sure the development packages of libxml2 and libxslt are installed
**
...
c:\temp\easy_install-tgshvo\lxml-3.1.0\src\lxml\includes\etree_defs.h(9)
: fatal error C1083: Cannot open include file:
'libxml/xmlversion.h': No such file or directory
[8]winbot / z3c.formui_py_265_32
Same: no lxml.
[9]winbot / z3c.jsonrpc_py_265_32
[10] winbot / z3c.jsontree_py_265_32
Same old Invalid request id returned.
[11] winbot / z3c.layer.ready2go_py_265_32
[12] winbot / z3c.layer.ready2go_py_265_32
ZopeXMLConfigurationError: File
c:\buildslave\z3c.layer.ready2go\build\src\z3c\layer\ready2go\ftesting.zcml,
line 62.2-62.32
ZopeXMLConfigurationError: File
c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51
WindowsError: [Error 3] The system cannot find the path specified:
u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*'
Okay, this does cause a test failure. Scratch that, a layer setup
failure.
Broken z3c.form release that's missing some locales? Some packages have
special build steps (compile *.mo or something) before you're supposed
to do setup.py sdist register upload.
[13] winbot / z3c.recipe.paster_py_265_32
Error: Couldn't find a distribution for 'beautifulsoup4'.
Pulled in by WebTest 2.0, which is pulled in by zope.app.wsgi 3.15.0.
WebTest also pulls in waitress.
These two packages need to be explicitly made available to the test
environment.
[14] winbot / zope.app.authentication_py_265_32
File
c:\buildslave\zope.app.authentication\build\src\zope\app\authentication\principalfolder.txt,
line 28, in principalfolder.txt
Failed example:
principals.authenticateCredentials({'login': 'login1', 'password': '123'})
Expected:
PrincipalInfo(u'principal.p1')
Got:
PrincipalInfo('principal.p1')
and similar.
[15] winbot / zope.app.pagetemplate_py_265_32
Same old AssertionError: u'42\r\n' != '42\n'
[16] winbot / zope.app.wsgi_py_265_32
[17] winbot / zope.app.wsgi_py_265_32
Same old PEP- violation.
[18] winbot / zope.browserpage_py_265_32
[19] winbot / zope.browserpage_py_265_32
My guess would be extra \r's in output, because look:
Failed example:
print(MyView(MyContent('bob'), TestRequest())(x=42))
Expected:
htmlbody
Hello bob
The URL is http://127.0.0.1
The positional arguments were ()
The keyword argument x is 42
/body/html
BLANKLINE
Got:
htmlbody
Hello bob
The URL is http://127.0.0.1
The positional arguments were ()
The keyword argument x is 42
/body/html
BLANKLINE
Also other tests fail like this
AssertionError: 'htmlbodypdone/p/body/html\r\n' !=
'htmlbodypdone/p/body/html\n'
[20] winbot / zope.sendmail_py_265_32
[21] winbot / zope.structuredtext_py_265_32
All tests pass in latest build
Marius Gedminas
--
http://pov.lt
