zope-tests - FAILED: 6, OK: 17
This is the summary for test reports received on the zope-tests list between 2012-11-30 00:00:00 UTC and 2012-12-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 ---------------- Successful - zopetoolkit_trunk - Build # 93 Successful - zopetoolkit_trunk_app - Build # 77 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux [1] winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 [3] winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / zc.lockfile_py_265_32 [6] winbot / zope.app.i18n_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069693.html [2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069694.html [3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069695.html [4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069696.html [5] FAILED winbot / zc.lockfile_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069675.html [6] FAILED winbot / zope.app.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069697.html
On Sat, Dec 1, 2012 at 8:00 PM, Zope tests summarizer <noreply@zope.org> wrote: ...
[1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069693.html
[2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069694.html
[3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069695.html
[4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069696.html
This is due to the release yesterday. I can and will "fix" this, by providing a test extra, but this will only cause no tests to run. The fix may be needed for test of third-party packages that depend on ZODB3 [test]. The winbot needs to be modified to run the tests for persistent, BTrees, ZODB and ZEO separately.
[5] FAILED winbot / zc.lockfile_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069675.html
I'll look at this today. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/02/2012 08:55 AM, Jim Fulton wrote:
On Sat, Dec 1, 2012 at 8:00 PM, Zope tests summarizer <noreply@zope.org> wrote:
...
[1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069693.html
[2] FAILED winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2012-December/069694.html
[3] FAILED winbot / ZODB_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2012-December/069695.html
[4] FAILED winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2012-December/069696.html
This is due to the release yesterday.
I can and will "fix" this, by providing a test extra, but this will only cause no tests to run. The fix may be needed for test of third-party packages that depend on ZODB3 [test].
The winbot needs to be modified to run the tests for persistent, BTrees, ZODB and ZEO separately.
[5] FAILED winbot / zc.lockfile_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/069675.html
I'll look at this today.
If ZODB3 no longer has tests (as a pure meta-package), then dropping the 'test' dependency and changing the buldout.cfg accordingly seems correct. If you want to allow thrid-party pacakges to use the '[test]' extra, you could have it depend on the corresponding extras (if any) for the underlying real packages. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC7gpIACgkQ+gerLs4ltQ7tEQCfRxFDioiJ51o+WWnZIh05daxv 5ZgAn04Xe61mG8TVbW26agkfYroBf5Ng =8Uhh -----END PGP SIGNATURE-----
On Sun, Dec 2, 2012 at 11:32 AM, Tres Seaver <tseaver@palladion.com> wrote: ...
If ZODB3 no longer has tests (as a pure meta-package), then dropping the 'test' dependency and changing the buldout.cfg accordingly seems correct. If you want to allow thrid-party pacakges to use the '[test]' extra, you could have it depend on the corresponding extras (if any) for the underlying real packages.
Yup, in the long run, bit in the short run, I don't want to break packages that depend on "ZODB3 [test]". I released a2 which ads back this extra. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/02/2012 11:32 AM, Tres Seaver wrote:
If ZODB3 no longer has tests (as a pure meta-package), then dropping the 'test' dependency and changing the buldout.cfg accordingly seems correct. If you want to allow thrid-party pacakges to use the '[test]' extra, you could have it depend on the corresponding extras (if any) for the underlying real packages.
Oops, I missed seeing that you had already done the latter. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlC7gzcACgkQ+gerLs4ltQ4+pgCfVa9dX45r+4R9VAwArOPLYcOV 7nIAn3aJ6RbHZvSYmSg5jahDiBaOv7q/ =8PQR -----END PGP SIGNATURE-----
Hello, On 12/02/2012 02:55 PM, Jim Fulton wrote:
On Sat, Dec 1, 2012 at 8:00 PM, Zope tests summarizer <noreply@zope.org> wrote:
...
[1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069693.html
[2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069694.html
[3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2012-December/069695.html
[4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2012-December/069696.html
This is due to the release yesterday.
I can and will "fix" this, by providing a test extra, but this will only cause no tests to run. The fix may be needed for test of third-party packages that depend on ZODB3 [test].
The winbot needs to be modified to run the tests for persistent, BTrees, ZODB and ZEO separately.
I think the winbot does the right job. Those tests are running against svn://svn.zope.org/repos/main/ZODB/trunk Now the tests pass as you added [test] back: Total: 3407 tests, 0 failures, 0 errors in 5 minutes 15.068 seconds. http://winbot.zope.org/builders/ZODB_dev%20py_265_win32/builds/861/steps/tes... I just need to add a builder for ZEO now -- Best regards, Adam GROSZER -- Quote of the day: How you look depends on where you go.
On Mon, Dec 3, 2012 at 3:15 AM, Adam GROSZER <agroszer.ll@gmail.com> wrote:
Hello,
On 12/02/2012 02:55 PM, Jim Fulton wrote:
On Sat, Dec 1, 2012 at 8:00 PM, Zope tests summarizer <noreply@zope.org> wrote:
...
[1] FAILED winbot / ZODB_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2012-December/069693.html
[2] FAILED winbot / ZODB_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2012-December/069694.html
[3] FAILED winbot / ZODB_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2012-December/069695.html
[4] FAILED winbot / ZODB_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2012-December/069696.html
This is due to the release yesterday.
I can and will "fix" this, by providing a test extra, but this will only cause no tests to run. The fix may be needed for test of third-party packages that depend on ZODB3 [test].
The winbot needs to be modified to run the tests for persistent, BTrees, ZODB and ZEO separately.
I think the winbot does the right job. Those tests are running against
svn://svn.zope.org/repos/main/ZODB/trunk
Now the tests pass as you added [test] back:
Ah, there was a bug in the buildout config, which I just fixed. There's no way that ZODB should be depending on ZODB3, even in the buildout. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm
participants (4)
-
Adam GROSZER -
Jim Fulton -
Tres Seaver -
Zope tests summarizer