Re: [Zope-CMF] Still Failing - CMF-trunk_Zope-trunk - Build # 764
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/08/2015 06:58 AM, Maurits van Rees wrote: > Jenkins schreef op 08-06-15 om 04:09: >> CMF-trunk_Zope-trunk - Build # 764 - Still Failing: >> >> Check console output at >> https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/764/ to view the >> results. > > Tests should pass next time. Thank you! Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJVdkt3AAoJEPKpaDSJE9HYXjoQALjTdqU8AQNxJI2+iuNAPimK Fp/y5PeAhQ4FSz9QnqeHIG+hAwVAZ+cniiM8XYvmTT8a4lWa0oxbcQNswIbmw0QB TYzHSNvM5fC7kwvu5eZlaY3dVhETN5BknGEmRbeP0e3EWUxGr7c9AXy7kENKTYXe a11LuI2C0Tmg58/QoMkLAeGBgBwNK/StX2bzm4u5wQ/jAVpnmDDOffVqHJPCHo/B gJzjTVrmvB3OLuBRJrqdNGFdG3IvaHE/7SRGograHvbBGeVricjfVhE1HSCBS9PB U+6Fohe88SioeOxqs02iJriuJlBJJFp1uA2nw7/TlbwKKhcRp81i9BzOFMgQcJXM lCffVesb9J1XbqZi0wPwbyUEsFAiGg0AdnWjjPGypCxWrI6otDxAEzopHePzILTJ LpCU2CFzLh4l0II+SdvJYkMEpwtuudU187yoVPgtFkVy7bMa0tAeP5lEUVZlXkGO uO63XLXJbwHlHP2J/CEfm3PUP/IfQ3VuXjrKmt34xtPjFYA6xkHU30pLEBm64Jmu nBNi05s3tfvTV2NFJbqYqvRZRnCy1dbATIpBZonGe/rStv+k/8I4wX5XKYqxSFZ/ Kgu7vcTsaDXa00zIgwlDdv9hyvzWoT4iTZiR9Vw66pUNS0wKhhqmdwwLqM3e6sZl mumexI6gGMyO0XIiKaLh =AzJg -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-CMF] Fixed - CMF-trunk_Zope-trunk - Build # 765
CMF-trunk_Zope-trunk - Build # 765 - Fixed: Check console output at https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/765/ to view the results.___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-CMF] cmf-tests -
This is the summary for test reports received on the cmf-tests list between 2015-06-07 00:00:00 UTC and 2015-06-08 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 Non-OK results -- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Still Failing - CMF-trunk_Zope-trunk - Build # 754
Charlie Clark schreef op 29-05-15 om 11:02: Am .05.2015, 04:10 Uhr, schrieb Jenkins : Check console output at https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/754/ to view the results. One thing I don't like about Jenkins is the verbosity of the report and no summary of what failed. This is probably because I'm too stupid. The errors look fairly trivial but I have to work out how to checkout the sources from the new repo. Charlie Error in test test_DirectoryViewFolderCustom (Products.CMFCore.tests.test_DirectoryView.DirectoryViewFolderTests) Traceback (most recent call last): File "/usr/local/lib/python2.7/unittest/case.py", line 332, in run testMethod() File "/var/lib/jenkins/jobs/CMF-trunk_Zope-trunk/workspace/develop/Products.CMFCore/Products/CMFCore/tests/test_DirectoryView.py", line 225, in test_DirectoryViewFolderCustom testfolder = self.ob.fake_skin.test_directory AttributeError: test_directory In subversion there was an empty test_directory. In git, this is not possible. (Also, an empty directory does not end up in the final package, so I guess those tests would fail there too.) I have added a README.txt in the test_directory so git has the directory. Locally, the tests now pass. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Still Failing - CMF-trunk_Zope-trunk - Build # 764
Jenkins schreef op 08-06-15 om 04:09: CMF-trunk_Zope-trunk - Build # 764 - Still Failing: Check console output at https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/764/ to view the results. Tests should pass next time. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] A Tale of Two Repositories
Tres Seaver schreef op 26-05-15 om 03:10: I have cloned the "root" CMF buildout repository to Git, and pushed to Github[1] and Launchpad[2]. This one was involved enough that I'd like some extra eyeballs on it before clearing out the SVN 'trunk': in particular, I think it is possilbe that some of the historical changes (removing the products as direct contents, replacing them first with 'svn:externals', an later with 'mr.developer' checkouts), could be messed up. If you have the zen, please clone from either Git location and poke around. I tried to preserve "important" tags (those matching releases) and branches (the release lines) but left some of them behind. Please check for correct e-mail addresses in the logs, too. Note that the only current CI build is failing even though it is checked out still from SVN[3]. I haven't looked into it yet, but the likelihood is that it will be a relatively shallow fix. [1] https://github.com/zopefoundation/CMF-buildout [2] https://code.launchpad.net/zope-cmf-buildout [3] https://jenkins.starzel.de/job/CMF-trunk_Zope-trunk/750/ Tres. Thanks! Looks okay to me. I did a few more commits, adding .gitignore to all products and buildouts, updating buildout configs for the 2.2 and 2.3 branch, fixing the failing CMFCore test. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
