| *** sweh has quit IRC | 00:02 | |
| *** junkafarian has quit IRC | 00:21 | |
| *** dbfrombrc has quit IRC | 00:21 | |
| *** aaronv has joined #zope3-dev | 00:28 | |
| *** pcardune has quit IRC | 00:29 | |
| *** greenman has quit IRC | 00:29 | |
| *** benji has quit IRC | 00:33 | |
| J1m | srichter_, ayt? | 00:51 |
|---|---|---|
| srichter_ | J1m: yes | 00:52 |
| *** srichter_ is now known as srichter | 00:52 | |
| J1m | I'm trying to run the kgs tests. | 00:52 |
| J1m | using the trunk of zope.kgs | 00:52 |
| srichter | ok | 00:52 |
| srichter | yep | 00:52 |
| J1m | when I run bin/generate-buildout, it says it wants a package-cfg-path | 00:53 |
| srichter | really, that's strange | 00:53 |
| srichter | the buildout.cfg specifies default parameters | 00:53 |
| J1m | I don't think it needed that before. | 00:53 |
| srichter | no it does not | 00:53 |
| srichter | Roy Mathew got the tests to run this weekend | 00:53 |
| srichter | huh | 00:54 |
| srichter | how did you build? py25 bootstrap.py; ./bin/buildout -N | 00:54 |
| J1m | I used an existing Python 2.5 buildout to bootstrap it. | 00:55 |
| J1m | Then ran bin/buildout. | 00:55 |
| srichter | ok, that should still all work as you know | 00:55 |
| srichter | can you check the generated script whether it contains the arguments | 00:55 |
| * J1m tries running buildout again | 00:55 | |
| J1m | The main script in buildout.py definitely wants an argument. | 00:56 |
| J1m | I wonder if your checkout is yup to date. | 00:56 |
| srichter | let me try | 00:57 |
| srichter | yeah, I am all up-todate | 00:57 |
| srichter | look into buildout.cfg | 00:57 |
| srichter | the arguments should be listet there | 00:57 |
| srichter | oh | 00:57 |
| srichter | you need zope.release | 00:57 |
| srichter | :-) | 00:57 |
| srichter | KGS is just the software | 00:57 |
| srichter | zope.kgs that is | 00:57 |
| J1m | oh yeah | 00:57 |
| srichter | sorry | 00:58 |
| J1m | np, I should have remembered that, but your note said zope KGS. | 00:58 |
| srichter | the note said zope.release :-) | 00:59 |
| J1m | Oh yeah, in the body. | 00:59 |
| srichter | (note that I got 12 failures this afternoon because some package does not tear down correctly) | 00:59 |
| J1m | who reads the body? ;) | 01:00 |
| srichter | LOL | 01:00 |
| srichter | I remember that! | 01:00 |
| srichter | next time I put the entire message in the subject | 01:00 |
| Theuni1 | Doesn't matter. Just put it somewhere on the internet. ;) | 01:00 |
| srichter | J1m: btw, does zope.testing support running only tests of a particular layer? | 01:01 |
| Theuni1 | yes | 01:01 |
| Theuni1 | --layer | 01:01 |
| srichter | because 90% of the tests tun in the non-layer in 10% of the time | 01:01 |
| Theuni1 | (No, I'm not trying to be Jim) | 01:01 |
| srichter | cool | 01:01 |
| Theuni1 | there is no non-layer anymore | 01:01 |
| srichter | Theuni1: how is the layer called when I do not specify one? | 01:01 |
| Theuni1 | it runs all tests in all layers | 01:02 |
| Theuni1 | previously the unit-test layer was special but I refactored that about 15 months ago | 01:02 |
| Theuni1 | the -f and -u are only command line shims above the --layer argument | 01:02 |
| srichter | but I only want to run the tests that have no explicit layer specified | 01:02 |
| Theuni1 | then they're in the unit test layer | 01:02 |
| Theuni1 | as before | 01:02 |
| srichter | ok, so -u? | 01:03 |
| Theuni1 | yup | 01:03 |
| srichter | cool | 01:03 |
| Theuni1 | or using --layer and the really long name that is attached to that layer | 01:03 |
| srichter | I prefer -u :-) | 01:03 |
| Theuni1 | That's why I left it there ;) | 01:04 |
| srichter | having all these layers really slows down test running | 01:04 |
| Theuni1 | only depends on your layers and how much setup they perform | 01:04 |
| Theuni1 | it's not the layerism itself | 01:05 |
| srichter | oh, I know | 01:05 |
| Theuni1 | As long as you don't have about 50 billion layers | 01:05 |
| srichter | but most of them bring up a significant part of the app server | 01:05 |
| Theuni1 | yup | 01:05 |
| Theuni1 | If you do inheritance then some of them will be setup in a combined fashion. | 01:05 |
| Theuni1 | IIRC | 01:05 |
| srichter | running all the tests in the KGS takes 50 minutes and with the exception of the ZODB test my feeling is that 50% of the time is spent in layer setup | 01:06 |
| srichter | right | 01:06 |
| Theuni1 | but in general, count about 2 seconds for a layer when a new process needs to be spawned | 01:06 |
| srichter | except that packages do not do that | 01:06 |
| Theuni1 | Hmm. | 01:06 |
| Theuni1 | When I wrote the compattest thing I was able to get that time down by using sheer computing power. | 01:06 |
| Theuni1 | I can run the compattests in < 2 minutes | 01:06 |
| srichter | yep, you can, absolutely | 01:06 |
| srichter | for all 16k+ tests in less than 2 mins? | 01:07 |
| Theuni1 | I think that was the time i got | 01:07 |
| Theuni1 | ran on a 32gb 8 core machine with fast disks | 01:08 |
| srichter | wow, that's impressive | 01:08 |
| srichter | someone should sponsor a machine to me to do this sort of work | 01:08 |
| Theuni1 | ;) | 01:08 |
| srichter | that would drastically improve my efficiency | 01:08 |
| Theuni1 | Yeah, those babies are nice :) | 01:08 |
| srichter | and they are really not that expensive anymore wither | 01:09 |
| Theuni1 | Nope | 01:09 |
| Theuni1 | Can get them for less than 3k EUR | 01:09 |
| Theuni1 | If you build them yourself and don't need support contracts probably even cheaper. | 01:09 |
| * Theuni1 goes back to selecting a surround system | 01:09 | |
| srichter | Theuni1: yeah see you later; are you going to be around next Tuesday? | 01:10 |
| srichter | in Halle that is? | 01:10 |
| Theuni1 | It's in Halle. As I said: unfortunately I'm not around. I'll be in Helsinki at that time. | 01:10 |
| Theuni1 | But at least three of our people are expecting you. | 01:10 |
| Theuni1 | That would be Zagy, Wolfgang and Thomas. | 01:11 |
| srichter | cool, I'll send an E-mail out later this week outlining an agenda and exact times, but it will be on Tuesday | 01:11 |
| Theuni1 | fine with me ;) | 01:12 |
| *** J1m has quit IRC | 01:12 | |
| *** pcardune has joined #zope3-dev | 01:15 | |
| *** aaronv has quit IRC | 01:19 | |
| *** dbfrombrc has joined #zope3-dev | 01:23 | |
| *** Theuni1 has quit IRC | 01:24 | |
| *** dbfrombrc has quit IRC | 01:25 | |
| *** dbfrombrc has joined #zope3-dev | 01:25 | |
| *** Theuni1 has joined #zope3-dev | 01:27 | |
| *** aaronv has joined #zope3-dev | 01:29 | |
| *** junkafarian has joined #zope3-dev | 01:29 | |
| *** jamur2 has quit IRC | 01:33 | |
| *** jamur2 has joined #zope3-dev | 01:33 | |
| *** jamur2_ has joined #zope3-dev | 01:34 | |
| *** jamur2 has quit IRC | 01:37 | |
| *** allisterb_ has quit IRC | 01:37 | |
| *** allisterb has joined #zope3-dev | 01:39 | |
| *** yvl has quit IRC | 01:39 | |
| *** greenman has joined #zope3-dev | 01:43 | |
| *** romanofski has joined #zope3-dev | 01:44 | |
| *** jamur2_ has quit IRC | 01:50 | |
| *** jamur2 has joined #zope3-dev | 01:50 | |
| *** jamur2 has quit IRC | 01:51 | |
| *** allisterb_ has joined #zope3-dev | 01:53 | |
| *** drudi has quit IRC | 01:57 | |
| *** Theuni1 has quit IRC | 01:58 | |
| *** febb has quit IRC | 02:03 | |
| *** allisterb has quit IRC | 02:04 | |
| *** lurkymclurkleton has quit IRC | 02:06 | |
| *** dbfrombrc is now known as dbfrombrc|away | 02:18 | |
| *** aaronv has quit IRC | 02:24 | |
| *** nathany has quit IRC | 02:25 | |
| *** redir has quit IRC | 02:31 | |
| *** hazmat has joined #zope3-dev | 02:47 | |
| *** ChanServ sets mode: +o hazmat | 02:47 | |
| *** jhauser has quit IRC | 02:51 | |
| *** BjornT_ has quit IRC | 03:03 | |
| *** BjornT has joined #zope3-dev | 03:03 | |
| junkafarian | anyone know if there is an ellipsis option to set the default for running doctests through nose in setup.cfg? | 03:28 |
| *** junkafarian has quit IRC | 03:45 | |
| *** gary_poster has joined #zope3-dev | 03:45 | |
| *** redir has joined #zope3-dev | 03:50 | |
| *** pcardune has quit IRC | 03:52 | |
| *** skriv1 has joined #zope3-dev | 04:09 | |
| *** davisagli has left #zope3-dev | 04:09 | |
| *** skriv has quit IRC | 04:26 | |
| *** greenman has quit IRC | 04:55 | |
| *** drudi has joined #zope3-dev | 05:00 | |
| *** gary_poster has quit IRC | 05:01 | |
| *** alecm has quit IRC | 05:02 | |
| *** BjornT has quit IRC | 05:02 | |
| *** markusleist has joined #zope3-dev | 05:15 | |
| *** davisagli has joined #zope3-dev | 05:22 | |
| *** stub has joined #zope3-dev | 06:04 | |
| *** drudi has quit IRC | 06:06 | |
| *** pcardune has joined #zope3-dev | 06:07 | |
| *** pcardune has quit IRC | 06:10 | |
| *** afd__ has joined #zope3-dev | 06:16 | |
| *** alecm has joined #zope3-dev | 06:33 | |
| *** BjornT has joined #zope3-dev | 06:36 | |
| *** redir has quit IRC | 06:43 | |
| *** pcardune has joined #zope3-dev | 06:48 | |
| *** jpcw has quit IRC | 06:55 | |
| *** pcardune has quit IRC | 07:03 | |
| *** febb has joined #zope3-dev | 07:09 | |
| *** alecm has quit IRC | 07:18 | |
| *** greenman has joined #zope3-dev | 07:40 | |
| *** sunoano has quit IRC | 07:40 | |
| *** sunoano has joined #zope3-dev | 07:42 | |
| *** hdima has joined #zope3-dev | 08:17 | |
| *** hdima has quit IRC | 08:18 | |
| *** skriv1 has quit IRC | 08:18 | |
| *** Theuni1 has joined #zope3-dev | 08:22 | |
| *** JaRoel|4D has quit IRC | 08:25 | |
| *** jukart has joined #zope3-dev | 08:42 | |
| *** afd__ has quit IRC | 08:42 | |
| *** agroszer has joined #zope3-dev | 08:59 | |
| *** __mac__ has joined #zope3-dev | 09:05 | |
| *** febb has quit IRC | 09:23 | |
| *** JaRoel|4D has joined #zope3-dev | 09:23 | |
| *** yvl has joined #zope3-dev | 09:32 | |
| *** yvl has quit IRC | 09:34 | |
| *** kaeru has joined #zope3-dev | 09:34 | |
| *** linmyat has joined #zope3-dev | 09:50 | |
| *** goschtl has joined #zope3-dev | 10:01 | |
| *** jhauser has joined #zope3-dev | 10:07 | |
| *** iham has joined #zope3-dev | 10:09 | |
| *** __mac__ has quit IRC | 10:09 | |
| *** __mac__ has joined #zope3-dev | 10:10 | |
| *** sweh has joined #zope3-dev | 10:23 | |
| *** romanofski has quit IRC | 10:26 | |
| *** davisagli has left #zope3-dev | 10:35 | |
| *** iham has quit IRC | 10:40 | |
| *** junkafarian has joined #zope3-dev | 10:43 | |
| *** __mac__ has quit IRC | 10:48 | |
| *** ktwilight_ has joined #zope3-dev | 10:53 | |
| *** ktwilight has quit IRC | 10:55 | |
| *** ktwilight__ has joined #zope3-dev | 10:58 | |
| *** agroszer has quit IRC | 11:02 | |
| *** fcorrea has quit IRC | 11:02 | |
| *** mcdonc has quit IRC | 11:02 | |
| *** VladDrac has quit IRC | 11:02 | |
| *** agroszer has joined #zope3-dev | 11:02 | |
| *** fcorrea has joined #zope3-dev | 11:02 | |
| *** mcdonc has joined #zope3-dev | 11:02 | |
| *** VladDrac has joined #zope3-dev | 11:02 | |
| *** junkafarian_ has joined #zope3-dev | 11:07 | |
| *** vaab has joined #zope3-dev | 11:08 | |
| *** ignas has joined #zope3-dev | 11:09 | |
| vaab | hi everyone, I've found a bug in ZConfig and I have a patch, what is the best way to get it reviewed (and integrated) ? (I've already sent it on launchpad, but it seem not really alive) | 11:10 |
| *** ktwilight_ has quit IRC | 11:12 | |
| *** __mac__ has joined #zope3-dev | 11:14 | |
| *** iham has joined #zope3-dev | 11:14 | |
| *** romanofski has joined #zope3-dev | 11:16 | |
| *** pelle__ has joined #zope3-dev | 11:17 | |
| Theuni1 | vaab: launchpad is a reasonable place. if it languishes for long, you might consider posting a reference to the launchpad entry on the developer list. | 11:22 |
| *** pelle__ has quit IRC | 11:25 | |
| *** pelle__ has joined #zope3-dev | 11:26 | |
| *** junkafarian_ has quit IRC | 11:29 | |
| *** pelle__ has quit IRC | 11:29 | |
| *** greenman has quit IRC | 11:31 | |
| vaab | Theunil: thx for the tip | 11:37 |
| *** iham has quit IRC | 11:37 | |
| *** markusleist has left #zope3-dev | 11:47 | |
| *** markusleist has joined #zope3-dev | 11:48 | |
| *** jpcw has joined #zope3-dev | 11:57 | |
| *** kaeru has quit IRC | 12:21 | |
| Theuni1 | np | 12:27 |
| *** ccomb has joined #zope3-dev | 13:14 | |
| *** linmyat has quit IRC | 13:17 | |
| *** MJ has joined #zope3-dev | 13:21 | |
| *** pelle__ has joined #zope3-dev | 13:46 | |
| *** aaronv has joined #zope3-dev | 13:49 | |
| *** redir has joined #zope3-dev | 13:54 | |
| *** drudi has joined #zope3-dev | 14:03 | |
| *** junkafarian_ has joined #zope3-dev | 14:08 | |
| *** junkafarian_ has quit IRC | 14:09 | |
| *** drudi has quit IRC | 14:15 | |
| *** iham has joined #zope3-dev | 14:16 | |
| *** dunny has quit IRC | 14:21 | |
| *** iham has quit IRC | 14:27 | |
| *** projekt01 has joined #zope3-dev | 14:29 | |
| *** aaronv has quit IRC | 14:33 | |
| *** davisagli has joined #zope3-dev | 14:53 | |
| *** redir has quit IRC | 14:55 | |
| *** iham has joined #zope3-dev | 15:06 | |
| *** malthe is now known as malthe|away | 15:21 | |
| *** gary_poster has joined #zope3-dev | 15:29 | |
| *** drudi has joined #zope3-dev | 15:32 | |
| *** redir has joined #zope3-dev | 15:38 | |
| *** jamur2 has joined #zope3-dev | 15:41 | |
| *** sunoano has quit IRC | 15:41 | |
| *** jamur2 has quit IRC | 15:41 | |
| *** sunoano has joined #zope3-dev | 15:42 | |
| *** benji has joined #zope3-dev | 15:43 | |
| *** redir has quit IRC | 15:55 | |
| *** J1m has joined #zope3-dev | 15:59 | |
| *** redir has joined #zope3-dev | 16:00 | |
| *** redir has quit IRC | 16:01 | |
| *** romanofski has quit IRC | 16:02 | |
| *** jamur2 has joined #zope3-dev | 16:02 | |
| *** iham has quit IRC | 16:03 | |
| *** hexsprite has joined #zope3-dev | 16:04 | |
| *** lurkymclurkleton has joined #zope3-dev | 16:05 | |
| *** stub has quit IRC | 16:06 | |
| *** aaronv has joined #zope3-dev | 16:07 | |
| *** hexsprite has quit IRC | 16:09 | |
| *** Theuni1 has quit IRC | 16:12 | |
| *** Theuni2 has joined #zope3-dev | 16:12 | |
| *** __mac__ has quit IRC | 16:56 | |
| *** jdobrien has joined #zope3-dev | 17:09 | |
| jdobrien | can anyone point me to information using zope's get/query utilities for dependency injection....specifically I want to change the provider for unit tests | 17:10 |
| jdobrien | jdobrien, preferably without a monkey patch hack | 17:11 |
| *** ccomb has quit IRC | 17:18 | |
| srichter | jdobrien: in your test setup you simply need to do a zope.component.provideUtility() call with your testing component | 17:19 |
| *** sweh has quit IRC | 17:19 | |
| srichter | many packages do that | 17:19 |
| srichter | for example zope.keyreference | 17:19 |
| *** ccomb has joined #zope3-dev | 17:21 | |
| jdobrien | srichter, thanks...i guess it looked to easy :) | 17:21 |
| *** ktwilight__ has quit IRC | 17:38 | |
| *** ktwilight__ has joined #zope3-dev | 17:38 | |
| *** davisagli has quit IRC | 17:39 | |
| *** kaeru has joined #zope3-dev | 17:50 | |
| *** ktwilight__ has quit IRC | 17:53 | |
| *** drudi has quit IRC | 17:53 | |
| *** drudi has joined #zope3-dev | 17:53 | |
| *** redir has joined #zope3-dev | 17:56 | |
| *** ktwilight__ has joined #zope3-dev | 17:57 | |
| *** ktwilight__ has joined #zope3-dev | 17:58 | |
| *** projekt01 has quit IRC | 18:07 | |
| *** iham has joined #zope3-dev | 18:11 | |
| *** kursor has joined #zope3-dev | 18:19 | |
| *** iham has quit IRC | 18:20 | |
| *** skriv has joined #zope3-dev | 18:23 | |
| *** nathany has joined #zope3-dev | 18:30 | |
| J1m | srichter, ayt? | 18:33 |
| srichter | J1m: yeah | 18:33 |
| J1m | I'm getting lots of errors running tests of zope.release. | 18:33 |
| J1m | w python 2.5 on a 32-bit ubuntu machine | 18:34 |
| srichter | how many? | 18:34 |
| srichter | I get 12 right now due to the "provider" tales expression type not being registered | 18:34 |
| srichter | somehow some tearing down does not work right | 18:35 |
| J1m | 17 failures, 4 errors out of 16465 tests. | 18:35 |
| srichter | I have my suspicions, since something similar happens with the vocabulary registry | 18:37 |
| srichter | mmh, that's definitely more than I am seeing, though some tests might depend on an external script or so | 18:37 |
| srichter | let's start with the errors. which tests/packages cause them? | 18:37 |
| J1m | Tests with errors: | 18:37 |
| J1m | /home/jim/.buildout/eggs/lovely.recipe-1.0.0b5-py2.5.egg/lovely/recipe/egg/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/lovely.recipe-1.0.0b5-py2.5.egg/lovely/recipe/fs/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/lovely.recipe-1.0.0b5-py2.5.egg/lovely/recipe/i18n/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/lovely.recipe-1.0.0b5-py2.5.egg/lovely/recipe/importchecker/README.txt | 18:37 |
| J1m | Tests with failures: | 18:37 |
| J1m | /home/jim/.buildout/eggs/keas.profile-0.1.0-py2.5.egg/keas/profile/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/keas.unit-1.0.0-py2.5.egg/keas/unit/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/lovely.remotetask-0.4-py2.5.egg/lovely/remotetask/processor.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.coverage-1.1.3-py2.5.egg/z3c/coverage/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.formui-2.0.0-py2.5.egg/z3c/formui/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.macro-1.2.1-py2.5.egg/z3c/macro/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.macroviewlet-1.0.0-py2.5.egg/z3c/macroviewlet/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.menu.ready2go-0.6.0-py2.5.egg/z3c/menu/ready2go/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.menu.ready2go-0.6.0-py2.5.egg/z3c/menu/ready2go/zcml.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.pagelet-1.1.0-py2.5.egg/z3c/pagelet/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.recipe.egg-0.2-py2.5.egg/z3c/recipe/egg/tests/../setup.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/z3c.wizard-0.6.0-py2.5.egg/z3c/wizard/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/zc.loggermonitor-0.1-py2.5.egg/zc/loggermonitor/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/zc.recipe.testrunner-1.2.0-py2.5.egg/zc/recipe/testrunner/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/zc.recipe.testrunner-1.2.0-py2.5.egg/zc/recipe/testrunner/bugfixes.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/zope.contentprovider-3.5.0-py2.5.egg/zope/contentprovider/README.txt | 18:37 |
| J1m | /home/jim/.buildout/eggs/zope.viewlet-3.5.0-py2.5.egg/zope/viewlet/README.txt | 18:37 |
| J1m | Total: 16465 tests, 17 failures, 4 errors in 131 minutes 38.403 seconds. | 18:38 |
| J1m | :) | 18:38 |
| J1m | (benji hates me) | 18:38 |
| benji | my eyes! | 18:38 |
| * J1m tries running tests individually. | 18:38 | |
| benji | heh | 18:38 |
| srichter | J1m: ok, keas.unit is due to the fact that you do not have the units script installed; we should make those tests optional | 18:38 |
| J1m | why are keas tests in the zope.release tests? | 18:39 |
| srichter | J1m: zope.contentprovider, z3c.macroviewlet, z3c.menu.*, zope.viewlet are most likely all due to the missing provider registration | 18:39 |
| J1m | The lovely recipe tests fail for me even when run individually. | 18:39 |
| srichter | keas.unit is a svn.zope.org package | 18:39 |
| srichter | ok, we should take lovely.recipe out of the KGS then | 18:39 |
| J1m | I thought you had all of the tests passing. | 18:39 |
| J1m | why does it matter whether it is a zope.org package? | 18:40 |
| srichter | yeah, then I added some more, which switched some test orders around that broke things and I did not investigate yet | 18:40 |
| *** JaRoel|4D has quit IRC | 18:40 | |
| J1m | dang | 18:40 |
| srichter | pretty much all tests should pass individually | 18:41 |
| srichter | that's how I tested it | 18:41 |
| srichter | the full run just takes too long; though the "provider" problem is visible when running "-u" which takes only 5 mins on my machine | 18:41 |
| J1m | btw, I see no good reason to run the zodb tests. | 18:42 |
| srichter | right, I usually comment them out too :-) | 18:42 |
| srichter | we can just set them to tested=False | 18:42 |
| J1m | zc.recipe.testrunner tests fail for me. :( | 18:43 |
| *** jukart has quit IRC | 18:43 | |
| J1m | Error: Couldn't find a distribution for 'zope.exceptions'. | 18:43 |
| J1m | I wonder what the heck it;s doing. | 18:44 |
| srichter | ah, where? | 18:44 |
| srichter | this is probably due to the fact that zope.exception is not listed as a dependency in the setUp() | 18:44 |
| srichter | I had to fix that before in one of the recipes | 18:44 |
| J1m | README.txt line 150. | 18:44 |
| srichter | which package? | 18:44 |
| J1m | zc.recipe.testrunner | 18:45 |
| srichter | mmh, I thought I had fixed that | 18:45 |
| J1m | I get a failure for z3c.recipe.egg. | 18:46 |
| J1m | Somehow, I don't think we should be testing recipes here. | 18:46 |
| J1m | But it depends on what the goals are. :) | 18:47 |
| srichter | I rather test more, sub-KGSs can then be derived from it | 18:47 |
| J1m | My goal is to try to make sure the packages commonly used to build web applications actually work together. | 18:47 |
| J1m | We need people who modify core packages to run core tests. | 18:47 |
| J1m | These ancillary failures will discourage that. | 18:48 |
| srichter | My explicit goal is to be able to say: Mmh, that package is useful right now I just want to be able to use it | 18:48 |
| srichter | you have to define core | 18:48 |
| J1m | fair enough. | 18:48 |
| J1m | But we should do that. | 18:48 |
| srichter | I bet you that our commonly used packages vary a bit | 18:48 |
| srichter | I think though that it would be useful to write a script that allows you to extract sub-lists | 18:49 |
| srichter | for example for a definition of "core" | 18:49 |
| J1m | Right now, we, ZC, are in a tough spot. We need to update packages but it's hard finding a set that work together. | 18:49 |
| J1m | Some sort of KGS could help a lot. | 18:49 |
| srichter | I hear you | 18:49 |
| srichter | I was in the same spot too several times in the last few months | 18:50 |
| J1m | so I'm most concerned about the packages that actually interact. | 18:50 |
| srichter | I could not even start a new project because I could not find a working set | 18:50 |
| srichter | right, and those pacakges are all passing now | 18:50 |
| *** iham has joined #zope3-dev | 18:50 | |
| srichter | maybe we could make use of layers | 18:50 |
| *** goschtl has left #zope3-dev | 18:50 | |
| srichter | I mean levels | 18:50 |
| srichter | so the most basic tests run in level 1, then level 2, etc | 18:51 |
| srichter | this way we can tell core developers to only worry about level 1 or 2 and release managers worry about higher-levels | 18:51 |
| J1m | I suggest that: | 18:52 |
| J1m | 1. It would be easier to implement this as separate sets of tests. Changing test levels would be to invasive. Levels were a bad idea. | 18:53 |
| J1m | 2. We should automate running tests individually. | 18:53 |
| srichter | I thought Theuni had set up individual testing before | 18:54 |
| J1m | BTW, I don't necessarily have a problem with running application level tests to catch backward-compatibility breakage, as long as the application tests only due to library breakage. | 18:54 |
| J1m | He did, but I think the thing they came up with didn't have a way to lock down version. IOW, no known good set. | 18:55 |
| srichter | so what would be the best way to set up individual test runs that do not take forever to complete? | 18:55 |
| J1m | also, it was rather ad hoc. It was appropriate for a sprint, but not as a development check. | 18:55 |
| J1m | Too bad he's not around atm. | 18:56 |
| srichter | Theuni2: ping | 18:56 |
| J1m | Well, the thing that generates a test script now could generate set of scripts, or it could generate a master script that just invoked the script we have now. | 18:57 |
| J1m | It would take just as long unless the paster script ran the individual scripts in separate threads. | 18:58 |
| J1m | It might be cool to have an option in the test runner to automate this. | 18:58 |
| J1m | Perhaps something that puts the unit packages for a package in a separate layer. | 18:59 |
| srichter | unit pacakges? | 18:59 |
| srichter | there is already a layer for unit tests that gets invoked when setting "-u" | 18:59 |
| J1m | Then we could use the -j switch to run each test/layer in a separate subprocess. | 18:59 |
| srichter | right | 19:00 |
| J1m | right. Maybe that could be hacked to create multiple unit layers. | 19:00 |
| srichter | btw, I think we can reuse some z3c.recipe.compattest code to make this work | 19:00 |
| srichter | it basically executes every package in its own sub-process | 19:01 |
| J1m | That sounds good. | 19:01 |
| *** MJ has quit IRC | 19:01 | |
| srichter | so basically, we could generate a "test-<PACKAGE>" script for each pacakge in the KGS | 19:02 |
| J1m | That would be one way. | 19:02 |
| srichter | then use a master script to control the run | 19:02 |
| srichter | it would also allow you to run a package individually | 19:03 |
| J1m | Or we could arrange that the unit tests for each package end up in a different layer. | 19:03 |
| srichter | right | 19:03 |
| J1m | we already have that with test selection. | 19:03 |
| J1m | What would be nice is to have a "core" test script that just tests libraries commonly used to actually run zope apps. | 19:04 |
| srichter | if ./bin/test -m <PACKAGENAME> would work reliably, we just need to have an additional script | 19:04 |
| Theuni2 | srichter: pong | 19:04 |
| srichter | Theuni2: see discussion above | 19:04 |
| * Theuni2 reads | 19:04 | |
| J1m | srichter, you mean bin/test -s package_name, which works reliably for me. | 19:04 |
| srichter | J1m: I would implement that by having a script that can produce a sub-list of the large KGS | 19:05 |
| srichter | J1m: oh, I might have used the wrong option then | 19:05 |
| J1m | -m selects test modules. | 19:05 |
| J1m | But it accepts regexes, so can be used to select packages sometimes. | 19:06 |
| srichter | [srichter@localhost test]$ ./bin/test -vpc1 -s zc.recipe.testrunner | 19:06 |
| srichter | Running tests at level 1 | 19:06 |
| srichter | Total: 0 tests, 0 failures, 0 errors in 0.000 seconds. | 19:06 |
| Theuni2 | actually the compattests should support your usecase | 19:07 |
| J1m | It appears that the tests for zc.recipe.testrunner actually install things and may depend on what you have installed. | 19:07 |
| Theuni2 | I'm not sure it's obvious. I'll have to re-investigate. | 19:08 |
| J1m | srichter, although I don't actually care about zc.recipe.testrunner in this context. :) | 19:08 |
| srichter | yeah | 19:08 |
| Theuni2 | I'm on a run currently and I'm not sure what the actual question is after reading your discussion. | 19:08 |
| srichter | Theuni2: we just try to figure out the best way to run all tests, but running the tests of each package in its own process | 19:09 |
| srichter | Theuni2: looking at compattest, it looks as you are doing just that | 19:09 |
| J1m | IMO, I think we want to define a set of packages that are commonly used in a running zope(3) application. We need to make sure those packages work together. | 19:09 |
| Theuni2 | yeah, that's what the compat tests do and they also allow starting them in parallel. I think it should also be possible to specify versions. | 19:09 |
| J1m | That's the goal. :) | 19:09 |
| Theuni2 | right. the compattests are there so you can work on a package and have the tests of other packages which will be future consumers of your changes checked right away. | 19:10 |
| J1m | I think we need to be able to test these packages in a known configuration that we update only after passing the tests on a specific set of platforms. | 19:10 |
| srichter | right | 19:11 |
| Theuni2 | Even if I'm wrong and it currently might only support testing other packages trunks I think the compattest recipe can be modified in a simple manner to consume e.g. a version section. | 19:11 |
| J1m | where the platforms include: windows, linux, max, Python 2.6 | 19:11 |
| J1m | we need to make it as easy as people who work on these packages to do the right thing. | 19:12 |
| Theuni2 | jop | 19:12 |
| *** ignas has quit IRC | 19:12 | |
| Theuni2 | I need to leave now, though :) | 19:12 |
| srichter | Theuni2: see ya | 19:12 |
| J1m | I gotta go too. | 19:12 |
| J1m | Thanks for the great work srichter ! | 19:12 |
| srichter | J1m: note that the KGS software also support extensions, like buildout | 19:12 |
| srichter | so we could have several small ones, like for ZODB, Zope 3, zc.buildout and extras and then one large one that pulls them together | 19:13 |
| srichter | no problem; I wish I would not be the only one doing this relatively boring work ;-) | 19:14 |
| *** ktwilight__ has quit IRC | 19:23 | |
| *** jpcw has quit IRC | 19:32 | |
| *** jdobrien has quit IRC | 19:37 | |
| *** jdobrien has joined #zope3-dev | 19:41 | |
| *** jpcw has joined #zope3-dev | 19:50 | |
| *** alecm has joined #zope3-dev | 19:51 | |
| *** aaronv has quit IRC | 19:55 | |
| *** aaronv has joined #zope3-dev | 19:56 | |
| *** sweh has joined #zope3-dev | 20:03 | |
| *** redir has quit IRC | 20:09 | |
| *** redir has joined #zope3-dev | 20:12 | |
| *** pcardune has joined #zope3-dev | 20:20 | |
| *** jukart has joined #zope3-dev | 20:28 | |
| *** iham has quit IRC | 20:32 | |
| *** pcardune has quit IRC | 20:33 | |
| *** jukart has quit IRC | 20:43 | |
| *** kapil__ has joined #zope3-dev | 20:47 | |
| *** jukart has joined #zope3-dev | 21:02 | |
| *** sweh has quit IRC | 21:04 | |
| *** junkafarian has quit IRC | 21:07 | |
| *** aaronv has quit IRC | 21:13 | |
| *** aaronv has joined #zope3-dev | 21:14 | |
| *** junkafarian has joined #zope3-dev | 21:14 | |
| *** __mac__ has joined #zope3-dev | 21:15 | |
| *** Theuni2 has quit IRC | 21:18 | |
| *** Theuni1 has joined #zope3-dev | 21:18 | |
| *** kursor_ has joined #zope3-dev | 21:19 | |
| *** kursor has quit IRC | 21:19 | |
| *** Theuni1 has quit IRC | 21:24 | |
| *** ktwilight has joined #zope3-dev | 21:26 | |
| *** kursor_ has quit IRC | 21:31 | |
| *** kursor has joined #zope3-dev | 21:31 | |
| *** jukart has quit IRC | 21:46 | |
| *** sweh has joined #zope3-dev | 21:56 | |
| *** kursor has quit IRC | 21:57 | |
| *** ktwilight has quit IRC | 22:06 | |
| *** agroszer has quit IRC | 22:09 | |
| *** Theuni1 has joined #zope3-dev | 22:24 | |
| *** kapil__ has quit IRC | 22:28 | |
| *** __mac__ has quit IRC | 22:57 | |
| *** mintsauce has joined #zope3-dev | 23:00 | |
| mintsauce | I'm having problems with zope.app.renderer | 23:06 |
| *** dunny has joined #zope3-dev | 23:07 | |
| mintsauce | The exact error is: IOError: [Errno 2] No such file or directory: '/home/liveweb/site/eggs/zope.app.renderer-3.5.0-py2.4.egg/zope/app/renderer/meta.zml' | 23:07 |
| mintsauce | hah ... and pasting that, I've just noticed the problem | 23:08 |
| mintsauce | Nope, thought the mis-spelt zcml link (as zml) was the problem, but still get the same error | 23:09 |
| mintsauce | I note one of the latest updates to the package says 'Removed deprecated meta.zcml stuff and zpkg stuff.' | 23:09 |
| mintsauce | Removing the meta.zcml reference i now get | 23:15 |
| mintsauce | ConfigurationError: ('Invalid value for', 'package', 'ImportError: Module z3c has no global macro') | 23:15 |
| mintsauce | for: <include package="z3c.macro" file="meta.zcml" /> | 23:16 |
| *** dbfrombrc has joined #zope3-dev | 23:32 | |
| *** dbfrombrc has quit IRC | 23:33 | |
| *** junkafarian has quit IRC | 23:34 | |
| *** junkafarian has joined #zope3-dev | 23:37 | |
| *** jpcw has quit IRC | 23:40 | |
| *** malthe|away is now known as malthe | 23:42 | |
| *** sunoano has quit IRC | 23:43 | |
| *** ccomb has quit IRC | 23:43 | |
| *** ccomb has joined #zope3-dev | 23:44 | |
| *** sweh has quit IRC | 23:46 | |
| *** sunoano has joined #zope3-dev | 23:48 | |
| *** pcardune has joined #zope3-dev | 23:50 | |
| pcardune | anyone know why an OOBTree would enter into an inconsistent state where [tree[key] for key on tree.keys()] would yield a KeyError? | 23:53 |
| pcardune | Maybe Theuni1 or srichter know? | 23:53 |
| Theuni1 | ist that all the code that is there? | 23:53 |
| Theuni1 | you aren't modifying it while iterating? | 23:53 |
| Theuni1 | from a different thread? | 23:53 |
| pcardune | Theuni1: pretty sure I'm not modifying it from a different thread | 23:54 |
| Theuni1 | so presumably it's already inconsistent when the transaction starts? | 23:54 |
| pcardune | oh, no, modified before in that thread | 23:55 |
| pcardune | so potentially put into an inconsistent state in that thread | 23:56 |
| pcardune | Theuni1: one thing I did notice is a None key | 23:57 |
| Theuni1 | Wouldn't think that would make a problem. | 23:58 |
| Theuni1 | What are your other keys? | 23:58 |
| pcardune | Theuni1: all persistent objects | 23:58 |
| *** greenman has joined #zope3-dev | 23:59 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!