Re: Branches and trunk and CMFPLone and...

On 11/7/13, 1:31 PM, Lennart Regebro wrote:
> I fixed a thing on a branch of CMFPlone. Should I merge that to other
> branches, and in that case which ones?

Probably. What's the nature of the fix, and what branch did you start from?

> And is there some magic trick to setting up the development buildout?
> I did it according to the docs, but there is *a lot* of tests failing.
> I suspect that there is something slightly wrong, maybe I have the
> incorrect combination of trunk checkouts and pinned packages or
> something.
>
There are a lot of test isolation issues, so you can't just run bin/test 
and expect it to work. You can do one of the following:
1. Run tests for a single package, with bin/test -s 
dotted.path.to.package. This isn't thorough, but it's better than 
nothing and jenkins will run all the tests once you commit.
2. Run tests for all packages with bin/alltests, which runs each 
package's tests in a separate process (except for some groups configured 
in tests.cfg as being safe to run together). This takes about 45 minutes.

If those don't help, tell me what kind of failures you're seeing.

------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk