On Friday 07 August 2009, Fabio Tranchitella wrote:
If somebody tells me how it is possible to get projects from the
controlled-packages.cfg using zope.kgs, I can modify the recipe code to
understand it. :)
I did not use the precise jargon; read project wherever I write about packages
in the
Hey,
Wolfgang Schnerring wrote:
[snip]
After we reach a consensus on how to do it (I'm in favor of the way
outlined above, of course ;-), I'd like to add a step-by-step
walkthrough of the day-to-day development of a package somewhere below
http://docs.zope.org/zopetoolkit/process/index.html,
Jim Fulton wrote:
(Note that I'm using more precise jargon: project rather than
package. In the Python world, the word package means a module
that is implemented as a directory rather than a file. A project is a
collection of software for which we create distributions. We should
generally be
Hey,
Wolfgang Schnerring wrote:
* Fabio Tranchitella kob...@kobold.it [2009-08-07 11:46]:
* 2009-08-07 11:42, Wolfgang Schnerring wrote:
http://svn.zope.org/*checkout*/zope.release/trunk/releases/controlled-packages.cfg
IMHO the KGS testing should be done using the controlled-packages.cfg
Hey Fabio,
Fabio Tranchitella wrote:
* 2009-08-07 11:42, Wolfgang Schnerring wrote:
[buildout]
develop = .
parts = whatever else you need compat
extends = http://url/to/kgs/versions.cfg
# assuming said versions.cfg uses a section called [versions]:
versions = versions
I've done
* Jim Fulton j...@zope.com [2009-08-02 18:34]:
2. Some of the tests only pass if run separately, due to test
interactions. Presumably, this means that other tests aren't cleaning
up after themselves. I think we need a standard automated way to run
each package's tests separately. I think
Hello Wolfgang,
* 2009-08-07 11:42, Wolfgang Schnerring wrote:
[buildout]
develop = .
parts = whatever else you need compat
extends = http://url/to/kgs/versions.cfg
# assuming said versions.cfg uses a section called [versions]:
versions = versions
I've done something similar in
Thanks Fabio and Wolfgang,
How to do you specify the projects to be tested? Does every project
in versions get tested? If so, how do you specify versions for
projects that you don't want to run tests for but do want to fix the
version of.
(Note that I'm using more precise jargon: project rather
Hello Jim,
* 2009-08-07 12:28, Jim Fulton wrote:
How to do you specify the projects to be tested? Does every project in
versions get tested? If so, how do you specify versions for projects that
you don't want to run tests for but do want to fix the version of.
In my recipe, it automatically
2009/8/7 Fabio Tranchitella kob...@kobold.it:
Hello Jim,
* 2009-08-07 12:28, Jim Fulton wrote:
How to do you specify the projects to be tested? Does every project in
versions get tested? If so, how do you specify versions for projects that
you don't want to run tests for but do want to fix
* Jim Fulton j...@zope.com [2009-08-07 06:01]:
How to do you specify the projects to be tested? Does every project
in versions get tested? If so, how do you specify versions for
projects that you don't want to run tests for but do want to fix the
version of.
With z3c.recipe.compattest, to
* Jim Fulton j...@zope.com [2009-08-07 12:39]:
2009/8/7 Fabio Tranchitella kob...@kobold.it:
* 2009-08-07 12:28, Jim Fulton wrote:
How to do you specify the projects to be tested? Does every project in
versions get tested? If so, how do you specify versions for projects that
you don't want
* Fabio Tranchitella kob...@kobold.it [2009-08-07 11:46]:
* 2009-08-07 11:42, Wolfgang Schnerring wrote:
http://svn.zope.org/*checkout*/zope.release/trunk/releases/controlled-packages.cfg
IMHO the KGS testing should be done using the controlled-packages.cfg and
not versions, because some
On Fri, Aug 7, 2009 at 6:52 AM, Wolfgang Schnerringw...@gocept.com wrote:
* Jim Fulton j...@zope.com [2009-08-07 06:01]:
How to do you specify the projects to be tested? Does every project
in versions get tested? If so, how do you specify versions for
projects that you don't want to run tests
Hey,
Stephan Richter wrote:
- Insufficient dependency lists.
I wish we were publishing z3c.recipe.depgraph results for all these
packages in a convenient place. I'm worried that fixing dependencies
introduced cycles again (that were of course really there).
That's not to complain about all
On Mon, Jul 27, 2009 at 4:43 PM, Stephan
Richtersrich...@cosmos.phy.tufts.edu wrote:
Hi everyone,
last week I worked on getting the KGS trunk located in zope.release to pass
without failures. (Python 2.5 on Linux, i686)
Thanks so much!
As we discussed on IRC, there are still some open issues
On Sun, Aug 2, 2009 at 6:34 PM, Jim Fultonj...@zope.com wrote:
2. Some of the tests only pass if run separately, due to test
interactions. Presumably, this means that other tests aren't cleaning
up after themselves. I think we need a standard automated way to run
each package's tests
On Mon, Jul 27, 2009 at 22:43, Stephan
Richtersrich...@cosmos.phy.tufts.edu wrote:
Hi everyone,
last week I worked on getting the KGS trunk located in zope.release to pass
without failures. (Python 2.5 on Linux, i686)
Thank you for the work! Not the same result on my buildbot (64 bits):
Tests
Hi everyone,
last week I worked on getting the KGS trunk located in zope.release to pass
without failures. (Python 2.5 on Linux, i686)
It is in the best interest of everyone to keep the trunk in a passing
condition. So please try hard to do that. I am certainly very tired of
spending many
19 matches
Mail list logo
