I can only speak for myself, but usually everything builds totally fine locally. Too often something on the build infrastructure goes wrong
Carsten > Hi, > > > According to jenkins 1 in 10 builds fail, and some times randomly. For > instance, [2] succeeded but [3] failed, due to [4], a patch to a README.md > > According to [1] its not been discussed. > How are others dealing with this ? (-Dmaven.test.skip=true or not bothering > to build all before committing) > > I assume only the test methodology is unreliable, and not the released > artifacts ? > Could the unreliable tests be moved to ITs ? > Could the the long running tests also be moved to ITs ? > > Best Regards > ian > > > > > 1 > http://markmail.org/search/?q=sling%20build%20stability#query:sling%20build%20stability%20list%3Aorg.apache.incubator.sling-dev+page:1+state:facets > 2 https://builds.apache.org/job/sling-trunk-1.7/4270/ > 3 https://builds.apache.org/job/sling-trunk-1.7/4271/ > 4 https://builds.apache.org/job/sling-trunk-1.7/4271/changes#detail0 > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
