Re: [Zope3-dev] Zope3 tarball build/test run log
On Wed, Jan 04, 2006 at 11:29:47AM -0500, Jim Fulton wrote: > Brian Sutherland wrote: > > Yes, building and testing tarballs. > > What does this mean? What tar balls? Do you mean releases? basically the contents of releases/Zope-test.py. For schooltool, the testing script I use is the same as the script I use to make a schooltool release. In fact the products of these tests are called the schooltool nightly tarballs and are actually released. > > Another interesting idea is testing old bodies of code against newer > > Zope 3 versions. For backwards compatibility. For example, schoolbell, > > released with Zope 3.1 fails its tests with Zope3.2. > > I think this is a great idea. We do this internally. Of course, > it doesn't make sense to send schoolbell test failures to the Zope 3 list. > It does often make sense to raise breakage issues in the collector, > or on the list. Great, here is the first: from zope.server.http.publisherhttpserver import PublisherHTTPServer Traceback (most recent call last): File "test.py", line 1115, in ? exitcode = main(sys.argv) File "test.py", line 1077, in main test_cases = get_test_cases(test_files, cfg, tracer=tracer) File "test.py", line 333, in get_test_cases test_suite = func() File "/home/jinty/src/schooltoolrepo/schoolbell-1.2.x/src/schoolbell/app/tests/test_main.py", line 630, in test_suite optionflags=doctest.ELLIPSIS), File "/home/jinty/src/schooltoolrepo/schoolbell-1.2.x/Zope3/src/zope/testing/doctest.py", line 2334, in DocTestSuite module = _normalize_module(module) File "/home/jinty/src/schooltoolrepo/schoolbell-1.2.x/Zope3/src/zope/testing/doctest.py", line 235, in _normalize_module return __import__(module, globals(), locals(), ["*"]) File "/home/jinty/src/schooltoolrepo/schoolbell-1.2.x/src/schoolbell/app/main.py", line 49, in ? from zope.app.server.http import http ImportError: No module named http -- Brian Sutherland Metropolis - "it's the first movie with a robot. And she's a woman. And she's EVIL!!" ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope3 tarball build/test run log
Brian Sutherland wrote: ... >>What are you trying to accomplish with this test? > > > This is the result of building and testing the tarball/multiple > tarballs. I started this because zope3 was breaking my schooltool > nightly tarball build too often. > > Practically all of my commits over the last months have been fixing > tarball setup breakage caught by this test. Great! ... Yes, building and testing tarballs. What does this mean? What tar balls? Do you mean releases? Another interesting idea is testing old bodies of code against newer Zope 3 versions. For backwards compatibility. For example, schoolbell, released with Zope 3.1 fails its tests with Zope3.2. I think this is a great idea. We do this internally. Of course, it doesn't make sense to send schoolbell test failures to the Zope 3 list. It does often make sense to raise breakage issues in the collector, or on the list. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope3 tarball build/test run log
On Wed, Jan 04, 2006 at 07:08:59AM -0500, Jim Fulton wrote: > Brian, > > What are you trying to accomplish with this test? This is the result of building and testing the tarball/multiple tarballs. I started this because zope3 was breaking my schooltool nightly tarball build too often. Practically all of my commits over the last months have been fixing tarball setup breakage caught by this test. I wanted others to help as well;) > I think buildbot does a better > job. If there is a function you'd like to suggest for our emerging buildbot > setup, > I'd like to hear it. Yes, building and testing tarballs. Another interesting idea is testing old bodies of code against newer Zope 3 versions. For backwards compatibility. For example, schoolbell, released with Zope 3.1 fails its tests with Zope3.2. > A message like this, with no useful information might as well be spam. I agree, and have stopped forwarding these messages until I can be certain they will be more useful. Even before you sent this mail;) -- Brian Sutherland Metropolis - "it's the first movie with a robot. And she's a woman. And she's EVIL!!" ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope3 tarball build/test run log
Brian,
What are you trying to accomplish with this test? I think buildbot does a
better
job. If there is a function you'd like to suggest for our emerging buildbot
setup,
I'd like to hear it.
A message like this, with no useful information might as well be spam.
Jim
Zope 3 tarball build/test script wrote:
Traceback (most recent call last):
File "/home/jinty/releases/release-assistent.py", line 260, in ?
main(sys.argv)
File "/home/jinty/releases/release-assistent.py", line 257, in main
builder.run()
File "/home/jinty/releases/release-assistent.py", line 169, in run
self.buildReleases()
File "/home/jinty/releases/release-assistent.py", line 177, in buildReleases
self.buildRelease()
File "/home/jinty/releases/release-assistent.py", line 226, in buildRelease
self.runner.runMany(self.release['test_command'])
File "/home/jinty/releases/release-assistent.py", line 157, in runMany
self.run(cmd)
File "/home/jinty/releases/release-assistent.py", line 152, in run
raise CommandException('%s failed!' % cmd)
__main__.CommandException: cd tst && bin/zopetest failed!
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/jim%40zope.com
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Zope3 tarball build/test run log
This bug is fixed on the 3.2 branch. See my checkin yesterday.
The fix will be in the next release and will make it to the trunk soon.
Jim
Brian Sutherland wrote:
On Mon, Jan 02, 2006 at 02:30:07PM +0100, Zope 3 tarball build/test script
wrote:
Traceback (most recent call last):
File "/home/jinty/releases/release-assistent.py", line 260, in ?
main(sys.argv)
File "/home/jinty/releases/release-assistent.py", line 257, in main
builder.run()
File "/home/jinty/releases/release-assistent.py", line 169, in run
self.buildReleases()
File "/home/jinty/releases/release-assistent.py", line 177, in buildReleases
self.buildRelease()
File "/home/jinty/releases/release-assistent.py", line 226, in buildRelease
self.runner.runMany(self.release['test_command'])
File "/home/jinty/releases/release-assistent.py", line 157, in runMany
self.run(cmd)
File "/home/jinty/releases/release-assistent.py", line 152, in run
raise CommandException('%s failed!' % cmd)
__main__.CommandException: cd tst && bin/zopetest failed!
Apparently zopetest prints nothing out on STDERR when tests fail, here
is the interesting part of the log:
DEBUG: Running unit tests:
DEBUG:
DEBUG:
DEBUG: Failure in test
/home/jinty/releases/Zope3/tst/lib/python/zope/testing/testrunner-coverage.txt
DEBUG: Failed doctest test for testrunner-coverage.txt
DEBUG: File
"/home/jinty/releases/Zope3/tst/lib/python/zope/testing/testrunner-coverage.txt",
line 0
DEBUG:
DEBUG: --
DEBUG: File
"/home/jinty/releases/Zope3/tst/lib/python/zope/testing/testrunner-coverage.txt",
line 20, in testrunner-coverage.txt
DEBUG: Failed example:
DEBUG: testrunner.run(defaults)
DEBUG: Expected:
DEBUG: Running unit tests:
DEBUG: Ran 192 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer1 tests:
DEBUG: Set up samplelayers.Layer1 in N.NNN seconds.
DEBUG: Ran 9 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer11 tests:
DEBUG: Set up samplelayers.Layer11 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer111 tests:
DEBUG: Set up samplelayers.Layerx in N.NNN seconds.
DEBUG: Set up samplelayers.Layer111 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer112 tests:
DEBUG: Tear down samplelayers.Layer111 in N.NNN seconds.
DEBUG: Set up samplelayers.Layer112 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer12 tests:
DEBUG: Tear down samplelayers.Layer112 in N.NNN seconds.
DEBUG: Tear down samplelayers.Layerx in N.NNN seconds.
DEBUG: Tear down samplelayers.Layer11 in N.NNN seconds.
DEBUG: Set up samplelayers.Layer12 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer121 tests:
DEBUG: Set up samplelayers.Layer121 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer122 tests:
DEBUG: Tear down samplelayers.Layer121 in N.NNN seconds.
DEBUG: Set up samplelayers.Layer122 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Tearing down left over layers:
DEBUG: Tear down samplelayers.Layer122 in N.NNN seconds.
DEBUG: Tear down samplelayers.Layer12 in N.NNN seconds.
DEBUG: Tear down samplelayers.Layer1 in N.NNN seconds.
DEBUG: Total: 405 tests, 0 failures, 0 errors
DEBUG: lines cov% module (path)
DEBUG: testrunner-ex/sample1/sample11/sampletests.py)
DEBUG: testrunner-ex/sample1/sample13/sampletests.py)
DEBUG: testrunner-ex/sample1/sampletests/test1.py)
DEBUG: testrunner-ex/sample1/sampletests/test11.py)
DEBUG: testrunner-ex/sample1/sampletests/test111.py)
DEBUG: testrunner-ex/sample1/sampletests/test112.py)
DEBUG: testrunner-ex/sample1/sampletests/test12.py)
DEBUG: testrunner-ex/sample1/sampletests/test121.py)
DEBUG: testrunner-ex/sample1/sampletests/test122.py)
DEBUG: testrunner-ex/sample1/sampletests/test_one.py)
DEBUG: testrunner-ex/sample1/sampletestsf.py)
DEBUG: testrunner-ex/sample2/sample21/sampletests.py)
DEBUG: testrunner-ex/sample2/sampletests/test_1.py)
DEBUG: testrunner-ex/sample2/sampletests/testone.py)
DEBUG: testrunner-ex/sample3/sampletests.py)
DEBUG: testrunner-ex/samplelayers.py)
DEBUG: testrunner-ex/sampletests/test1.py)
DEBUG: testrunner-ex/sampletests/test11.py)
DEBUG: testrunner-ex/sampletests/test111.py)
DEBUG: testrunner-ex/sampletests/test112.py)
DEBUG: testrunner-ex/sampletests/test12.py)
DEBUG: testrunner-ex/sampletests/test121.py)
DEBUG: testrunner-ex/sampletests/test122.py)
DEBUG: testrunner-ex/sampletests/test_one.py)
DEBUG: testrunner-ex/sampletestsf.py)
DEBUG: False
DEBUG: Got:
DEBUG: Running unit tests:
DEBUG: Ran 192 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer1 tests:
DEBUG: Set up s
Re: [Zope3-dev] Zope3 tarball build/test run log
On Mon, Jan 02, 2006 at 02:30:07PM +0100, Zope 3 tarball build/test script
wrote:
> Traceback (most recent call last):
> File "/home/jinty/releases/release-assistent.py", line 260, in ?
> main(sys.argv)
> File "/home/jinty/releases/release-assistent.py", line 257, in main
> builder.run()
> File "/home/jinty/releases/release-assistent.py", line 169, in run
> self.buildReleases()
> File "/home/jinty/releases/release-assistent.py", line 177, in buildReleases
> self.buildRelease()
> File "/home/jinty/releases/release-assistent.py", line 226, in buildRelease
> self.runner.runMany(self.release['test_command'])
> File "/home/jinty/releases/release-assistent.py", line 157, in runMany
> self.run(cmd)
> File "/home/jinty/releases/release-assistent.py", line 152, in run
> raise CommandException('%s failed!' % cmd)
> __main__.CommandException: cd tst && bin/zopetest failed!
Apparently zopetest prints nothing out on STDERR when tests fail, here
is the interesting part of the log:
DEBUG: Running unit tests:
DEBUG:
DEBUG:
DEBUG: Failure in test
/home/jinty/releases/Zope3/tst/lib/python/zope/testing/testrunner-coverage.txt
DEBUG: Failed doctest test for testrunner-coverage.txt
DEBUG: File
"/home/jinty/releases/Zope3/tst/lib/python/zope/testing/testrunner-coverage.txt",
line 0
DEBUG:
DEBUG: --
DEBUG: File
"/home/jinty/releases/Zope3/tst/lib/python/zope/testing/testrunner-coverage.txt",
line 20, in testrunner-coverage.txt
DEBUG: Failed example:
DEBUG: testrunner.run(defaults)
DEBUG: Expected:
DEBUG: Running unit tests:
DEBUG: Ran 192 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer1 tests:
DEBUG: Set up samplelayers.Layer1 in N.NNN seconds.
DEBUG: Ran 9 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer11 tests:
DEBUG: Set up samplelayers.Layer11 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer111 tests:
DEBUG: Set up samplelayers.Layerx in N.NNN seconds.
DEBUG: Set up samplelayers.Layer111 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer112 tests:
DEBUG: Tear down samplelayers.Layer111 in N.NNN seconds.
DEBUG: Set up samplelayers.Layer112 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer12 tests:
DEBUG: Tear down samplelayers.Layer112 in N.NNN seconds.
DEBUG: Tear down samplelayers.Layerx in N.NNN seconds.
DEBUG: Tear down samplelayers.Layer11 in N.NNN seconds.
DEBUG: Set up samplelayers.Layer12 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer121 tests:
DEBUG: Set up samplelayers.Layer121 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer122 tests:
DEBUG: Tear down samplelayers.Layer121 in N.NNN seconds.
DEBUG: Set up samplelayers.Layer122 in N.NNN seconds.
DEBUG: Ran 34 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Tearing down left over layers:
DEBUG: Tear down samplelayers.Layer122 in N.NNN seconds.
DEBUG: Tear down samplelayers.Layer12 in N.NNN seconds.
DEBUG: Tear down samplelayers.Layer1 in N.NNN seconds.
DEBUG: Total: 405 tests, 0 failures, 0 errors
DEBUG: lines cov% module (path)
DEBUG: testrunner-ex/sample1/sample11/sampletests.py)
DEBUG: testrunner-ex/sample1/sample13/sampletests.py)
DEBUG: testrunner-ex/sample1/sampletests/test1.py)
DEBUG: testrunner-ex/sample1/sampletests/test11.py)
DEBUG: testrunner-ex/sample1/sampletests/test111.py)
DEBUG: testrunner-ex/sample1/sampletests/test112.py)
DEBUG: testrunner-ex/sample1/sampletests/test12.py)
DEBUG: testrunner-ex/sample1/sampletests/test121.py)
DEBUG: testrunner-ex/sample1/sampletests/test122.py)
DEBUG: testrunner-ex/sample1/sampletests/test_one.py)
DEBUG: testrunner-ex/sample1/sampletestsf.py)
DEBUG: testrunner-ex/sample2/sample21/sampletests.py)
DEBUG: testrunner-ex/sample2/sampletests/test_1.py)
DEBUG: testrunner-ex/sample2/sampletests/testone.py)
DEBUG: testrunner-ex/sample3/sampletests.py)
DEBUG: testrunner-ex/samplelayers.py)
DEBUG: testrunner-ex/sampletests/test1.py)
DEBUG: testrunner-ex/sampletests/test11.py)
DEBUG: testrunner-ex/sampletests/test111.py)
DEBUG: testrunner-ex/sampletests/test112.py)
DEBUG: testrunner-ex/sampletests/test12.py)
DEBUG: testrunner-ex/sampletests/test121.py)
DEBUG: testrunner-ex/sampletests/test122.py)
DEBUG: testrunner-ex/sampletests/test_one.py)
DEBUG: testrunner-ex/sampletestsf.py)
DEBUG: False
DEBUG: Got:
DEBUG: Running unit tests:
DEBUG: Ran 192 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelayers.Layer1 tests:
DEBUG: Set up samplelayers.Layer1 in N.NNN seconds.
DEBUG: Ran 9 tests with 0 failures and 0 errors in N.NNN seconds.
DEBUG: Running samplelay
