I just started the vote for the repoinit modules, so hopefully we'll be out of this snapshot mess soon
Regards Carsten Julian Sedding wrote > Hi Robert > > I think the test failures in oak-server did not come up because of the > modularised jenkins jobs we have now. > > The bundle's build seems to have run last after changes were applied > to it. However, a referenced SNAPSHOT dependency has evolved since and > made the tests fail. > > Any ideas how to catch this earlier? > > Regards > Julian > > PS: I have filed SLING-6260 for the failing oak-server ITs and committed a > fix. > > On Tue, Nov 8, 2016 at 10:07 PM, Robert Munteanu <[email protected]> wrote: >> Hi Alex. >> >> On Tue, 2016-11-08 at 20:01 +0000, Alexander Klimetschek wrote: >>> I have some trouble building Sling (all of it, it's been a while >>> since I tried that :) >>> >>> 1. It seems the Sling build requires Java 1.8 ("Apache Sling Testing >>> PaxExam" project failed with not all bundles loaded when I ran it >>> with a 1.7 JDK). A check/hint at the start of the build would be >>> great. >> >> Yes, some projects, mostly related to testing, pull in a launchpad >> version which requires Java 8. I'm not sure that the best fix is here. >> >> We could move all of them to a Java 8 profile, which might not be OK >> because you're missing projects without noticing. Or we could fail the >> reactor build altogether, which again is tricky since you might want to >> build a subset of the reactor using mvn -pl ... . >> >>> >>> 2. Then I get one project further to "Apache Sling JCR Oak Repository >>> Server" which fails as well during the test with not all bundles >>> loaded issues: >>> >>> Tests in error: >>> >>> LoginAdminBlacklistedIT.org.apache.sling.jcr.oak.server.it.LoginAdmin >>> BlacklistedIT » TestContainer >>> >>> LoginAdminWhitelistedIT.org.apache.sling.jcr.oak.server.it.LoginAdmin >>> WhitelistedIT » TestContainer >>> OakServerIT.org.apache.sling.jcr.oak.server.it.OakServerIT » >>> TestContainer The… >>> >>> I see this in the log: >>> >>> org.osgi.framework.BundleException: Unable to resolve >>> org.apache.sling.jcr.repoinit [79](R 79.0): missing requirement >>> [org.apache.sling.jcr.repoinit [79](R 79.0)] osgi.wiring.package; >>> (&(osgi.wiring.package=org.apache.sling.repoinit.parser.operations)(v >>> ersion>=3.0.0)(!(version>=4.0.0))) Unresolved requirements: >>> [[org.apache.sling.jcr.repoinit [79](R 79.0)] osgi.wiring.package; >>> (&(osgi.wiring.package=org.apache.sling.repoinit.parser.operations)(v >>> ersion>=3.0.0)(!(version>=4.0.0)))] >>> at >>> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:411 >>> 1) >>> at >>> org.apache.felix.framework.Felix.startBundle(Felix.java:2117) >>> at >>> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1371) >>> at >>> org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStart >>> LevelImpl.java:308) >>> at java.lang.Thread.run(Thread.java:745) >> >> ( I guess Julian already fixed it ) >> >>> >>> >>> 3. Still A LOT of projects to go in the build, so I am now going to >>> skip the tests :( >> >> We still have some flaky tests, see the dedicated Jenkins view at >> >> https://builds.apache.org/view/S-Z/view/Sling-Dashboard/ >> >> So you might still experience failures. >> >> FWIW, all SNAPSHOTs are deployed to repository.apache.org, so you >> should not need to build all of Sling - it's fine to build individual >> projects. >> >> Unless your goal is to build all of Sling, which is of course fine :-) >> >> Thanks, >> >> Robert > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
