Re: [Zope-dev] Zope Tests: 26 OK, 10 Failed, 5 Unknown
Hello,
I think I got it, see r114275. Let's wait for the bot to confirm.
The environment was completely REPLACED, thus wiping away PATH.
Tuesday, July 6, 2010, 8:45:51 PM, you wrote:
AG huh
AG weird, svn.exe is in c:\svn and it's on path:
AG excerpt from the log:
AG OS=Windows_NT
AG
PATH=C:\svn;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\python25_sys;c:\python25_sys\scripts;C:\Program
AG Files (x86)\GnuWin32\bin
AG PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PY
AG On Tue, Jul 6, 2010 at 8:37 PM, Hanno Schlichting ha...@hannosch.eu wrote:
On Tue, Jul 6, 2010 at 1:58 PM, Zope Tests Summarizer
zope-te...@epy.co.at wrote:
Summary of messages to the zope-tests list.
Period Mon Jul 5 12:00:00 2010 UTC to Tue Jul 6 12:00:00 2010 UTC.
There were 41 messages: 6 from Zope Tests, 3 from buildbot at
enfoldsystems.com, 11 from buildbot at winbot.zope.org, 11 from ccomb at
free.fr, 1 from ct at gocept.com, 9 from jdriessen at thehealthagency.com.
Test failures
-
Subject: FAILED : winbot / ztk_dev py_265_win64
From: buildbot at winbot.zope.org
Date: Mon Jul 5 22:46:05 EDT 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016126.html
One of the test failures is this:
Running test-zopeapp-zope.app.applicationcontrol
test-zopeapp-zope.app.applicationcontrol failed with:
Running zope.app.applicationcontrol.testing.ApplicationControlLayer tests:
Set up zope.app.applicationcontrol.testing.ApplicationControlLayer
in 1.843 seconds.
Ran 4 tests with 0 failures and 0 errors in 0.516 seconds.
Running zope.testing.testrunner.layer.UnitTests tests:
Tear down zope.app.applicationcontrol.testing.ApplicationControlLayer
in 0.000 seconds.
Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
'svn' is not recognized as an internal or external command,
operable program or batch file.
Failure in test test_WrongLocale
(zope.app.applicationcontrol.tests.test_zopeversion.Test)
Traceback (most recent call last):
File c:\Python26_32\lib\unittest.py, line 279, in run
testMethod()
File
c:\buildslave\ztk_dev_py_265_win32\build\src\zope.app.applicationcontrol\src\zope\app\applicationcontrol\tests\test_zopeversion.py,
line 136, in test_WrongLocale
self.assert_(zv.result.startswith('Development/Revision: '))
File c:\Python26_32\lib\unittest.py, line 325, in failUnless
if not expr: raise self.failureException, msg
AssertionError
Note the 'svn' is not recognized as an internal or external command, in
there.
Adam, does the build environment have Subversion installed and
accessible as svn on the path?
Hanno
--
Best regards,
Adam GROSZERmailto:agros...@gmail.com
--
Quote of the day:
Opacity is an irresistible challenge
___
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 Toolkit - 1.0a1 release
Am 30.06.2010 um 21:47 schrieb Hanno Schlichting: Hi. On behalf of the Zope Toolkit release team and the Zope community, I'm happy to announce the first 1.0 alpha release of the Zope Toolkit. You can read more about the release at http://docs.zope.org/zopetoolkit/releases/overview-1.0a1.html. The first ZTK release supports all of Python 2.4, 2.5 and 2.6. To use the ZTK release, you can use: [buildout] extends = http://download.zope.org/zopetoolkit/index/1.0a1/ztk-versions.cfg http://download.zope.org/zopetoolkit/index/1.0a1/zopeapp-versions.cfg Tried it with a project of mine. It works nearly completely fine. I only saw some a test breaking because between zope.testbrowser 3.6.0a2 and 3.9.0 behavior of browser.goBack() seems to have changed. It does now a reload of the previous page (causing form re-submit in my test). But maybe this is caused by the new mechanize 0.2.x version. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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] Python 2.7 disables deprecation warnings by default
I'm guessing that this has already been noticed and discussed, but
Python 2.7 disables deprecation warnings by default.
This will cause many tests to fail that checked that deprecation were
issued.
This change seems likely to make Python's deprecation system useless
and thus unused.
I noticed this yesterday when testing a project with Python 2.7 that
had some deprecation tests. I modified the test runner script to call:
warnings.simplefilter('default')
to renable deprecation warnings. This allowed my tests to pass and
also, ironically, showed new useful deprecation warnings in asyncore.
I'm not sure what the best way to handle this is. My initial thought
is that all test runners should enable deprecations by default. This
seems hard to enforce.
Individual test modules can do this, but I'm uncomfortable having a
test script make a global setting like this and the warning module
doesn't seem to provide a way to capture the current state so it can
be reset after running tests.
Jim
--
Jim Fulton
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 30 OK, 24 Failed, 2 Unknown
Summary of messages to the zope-tests list. Period Tue Jul 6 12:00:00 2010 UTC to Wed Jul 7 12:00:00 2010 UTC. There were 56 messages: 6 from Zope Tests, 2 from buildbot at enfoldsystems.com, 18 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 1 from ct at gocept.com, 18 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Jul 6 14:03:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016156.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Jul 6 14:58:04 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016157.html Subject: FAILED: Repository policy check found errors in 417 projects From: ct at gocept.com Date: Tue Jul 6 21:14:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016160.html Subject: FAILED : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Tue Jul 6 22:13:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016170.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Tue Jul 6 22:25:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016171.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Tue Jul 6 22:36:42 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016172.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Tue Jul 6 22:48:06 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016173.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Jul 6 23:02:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016174.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Jul 6 23:16:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016175.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Tue Jul 6 23:24:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016176.html Subject: FAILED : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Tue Jul 6 23:31:23 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016177.html Subject: FAILED : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Tue Jul 6 23:38:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016178.html Subject: FAILED : winbot / ztk_10 py_265_win64 From: buildbot at winbot.zope.org Date: Tue Jul 6 23:45:29 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016179.html Subject: FAILED : winbot / ztk_10 py_270_win32 From: buildbot at winbot.zope.org Date: Tue Jul 6 23:58:37 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016180.html Subject: FAILED : winbot / ztk_10 py_270_win64 From: buildbot at winbot.zope.org Date: Wed Jul 7 00:06:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016187.html Subject: FAILED : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Jul 7 02:54:49 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016193.html Subject: FAILED : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Jul 7 02:55:18 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016194.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Wed Jul 7 02:58:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016195.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Wed Jul 7 03:46:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016197.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Wed Jul 7 04:41:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016199.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Wed Jul 7 04:53:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016200.html Subject: FAILED : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Wed Jul 7 07:17:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016203.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Wed Jul 7 07:19:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016205.html Subject: FAILED : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Jul 7 07:22:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-July/016207.html Unknown --- Subject: [zodb-tests] buildbot failure in Enfold
Re: [Zope-dev] Python 2.7 disables deprecation warnings by default
On Wed, Jul 7, 2010 at 12:55 PM, Jim Fulton j...@zope.com wrote: I'm not sure what the best way to handle this is. My initial thought is that all test runners should enable deprecations by default. This seems hard to enforce. Individual test modules can do this, but I'm uncomfortable having a test script make a global setting like this and the warning module doesn't seem to provide a way to capture the current state so it can be reset after running tests. What about letting the testrunner (zope.testing / zope.testrunner) enable deprecation warnings by default, but add a command line switch to disable them or use the Python default? The test.py script from Zope 2 used to have a --nowarn option to disable all warnings. I think developers should always care about deprecation warnings and it's only developers who will run tests. I can understand why normal users of a Python program shouldn't see deprecation warnings - they usually cannot do anything about them. I also heard many reports from people asking questions about those deprecation warnings in a Plone context. Normal users don't know the difference between a deprecation warning and a SyntaxError or any other warning for that matter. All they see is a warning and get anxious. Hanno ___ 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] Python 2.7 disables deprecation warnings by default
On Wed, Jul 7, 2010 at 8:43 AM, Hanno Schlichting ha...@hannosch.eu wrote: On Wed, Jul 7, 2010 at 12:55 PM, Jim Fulton j...@zope.com wrote: I'm not sure what the best way to handle this is. My initial thought is that all test runners should enable deprecations by default. This seems hard to enforce. Individual test modules can do this, but I'm uncomfortable having a test script make a global setting like this and the warning module doesn't seem to provide a way to capture the current state so it can be reset after running tests. What about letting the testrunner (zope.testing / zope.testrunner) enable deprecation warnings by default, but add a command line switch to disable them or use the Python default? As I said, I think it makes the most sense for the testrunner to enable deprecation warnings, but it will be hard to get all test runners to do this. Keep in mind that our packages may be run with other test runners, most notably, but not exclusively the setup test runner. The test.py script from Zope 2 used to have a --nowarn option to disable all warnings. A flag to disable warnings will cause test failures is tests that deprercation warnings are issued. I guess such tests need to be changed to use some sort of warning mock so they don't depend on the unpredictable state of warnings. The warnings module is such a mess. If it weren't in the standard library, I might be tempted to help try to help fix it. :) Jim -- Jim Fulton ___ 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] Python 2.7 disables deprecation warnings by default
On Wed, Jul 07, 2010 at 02:43:14PM +0200, Hanno Schlichting wrote: On Wed, Jul 7, 2010 at 12:55 PM, Jim Fulton j...@zope.com wrote: I'm not sure what the best way to handle this is. My initial thought is that all test runners should enable deprecations by default. This seems hard to enforce. What about letting the testrunner (zope.testing / zope.testrunner) enable deprecation warnings by default, but add a command line switch to disable them or use the Python default? +1 Although tests that check for functions emitting DeprecationWarnings should not rely on this; they should explicitly ensure DeprecationWarnings are not filtered away in their own setup. Individual test modules can do this, but I'm uncomfortable having a test script make a global setting like this and the warning module doesn't seem to provide a way to capture the current state so it can be reset after running tests. There's the warnings.catch_warnings context manager (since Python 2.6): http://docs.python.org/library/warnings.html#testing-warnings I'm sure it can be backported to older Python versions, or the test setUp/tearDown can fiddle with warnings.filters[:] directly. Marius Gedminas -- http://pov.lt/ -- Zope 3 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] Python 2.7 disables deprecation warnings by default
On Wed, Jul 7, 2010 at 9:16 AM, Marius Gedminas mar...@gedmin.as wrote: On Wed, Jul 07, 2010 at 02:43:14PM +0200, Hanno Schlichting wrote: On Wed, Jul 7, 2010 at 12:55 PM, Jim Fulton j...@zope.com wrote: I'm not sure what the best way to handle this is. My initial thought is that all test runners should enable deprecations by default. This seems hard to enforce. What about letting the testrunner (zope.testing / zope.testrunner) enable deprecation warnings by default, but add a command line switch to disable them or use the Python default? +1 Although tests that check for functions emitting DeprecationWarnings should not rely on this; they should explicitly ensure DeprecationWarnings are not filtered away in their own setup. AFAICT, there's no documented way of doing this. Individual test modules can do this, but I'm uncomfortable having a test script make a global setting like this and the warning module doesn't seem to provide a way to capture the current state so it can be reset after running tests. There's the warnings.catch_warnings context manager (since Python 2.6): http://docs.python.org/library/warnings.html#testing-warnings This doesn't work if warnings are disabled. It can't enable them. It would be nice if passing record=True enabled all warnings, but it doesn't. I'm sure it can be backported to older Python versions, or the test setUp/tearDown can fiddle with warnings.filters[:] directly. Do you have any reason to believe that filters is a part of the warning module's public interface and not subject to change? It's not documented and not in __all__. I'm more inclined to create a test utility that temporarily replaces warnings.warn. Jim -- Jim Fulton ___ 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] Python 2.7 disables deprecation warnings by default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
I'm guessing that this has already been noticed and discussed, but
Python 2.7 disables deprecation warnings by default.
This will cause many tests to fail that checked that deprecation were
issued.
This change seems likely to make Python's deprecation system useless
and thus unused.
I noticed this yesterday when testing a project with Python 2.7 that
had some deprecation tests. I modified the test runner script to call:
warnings.simplefilter('default')
to renable deprecation warnings. This allowed my tests to pass and
also, ironically, showed new useful deprecation warnings in asyncore.
I'm not sure what the best way to handle this is. My initial thought
is that all test runners should enable deprecations by default. This
seems hard to enforce.
Individual test modules can do this, but I'm uncomfortable having a
test script make a global setting like this and the warning module
doesn't seem to provide a way to capture the current state so it can
be reset after running tests.
As of Python 2.6, the warnings module sports a context manager::
with warnings.catch_warnings():
warnings.simplefilter(default)
fxn()
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkw0iDUACgkQ+gerLs4ltQ4C7gCfd8WbirfwtAxnc99yhjfdPlvK
4SYAoNxDTkSp1TAdOe2Go3sBJtM0b1/t
=3cc2
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Python 2.7 disables deprecation warnings by default
On Wed, Jul 7, 2010 at 9:59 AM, Tres Seaver tsea...@palladion.com wrote: Individual test modules can do this, but I'm uncomfortable having a test script make a global setting like this and the warning module doesn't seem to provide a way to capture the current state so it can be reset after running tests. As of Python 2.6, the warnings module sports a context manager:: with warnings.catch_warnings(): warnings.simplefilter(default) fxn() Ah, this works because catch_warnings saves and later restores the filter configuration. Cool. Jim -- Jim Fulton ___ 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 )
