Source: zookeeper Version: 3.4.9-2 Severity: serious Tags: stretch sid User: [email protected] Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386
Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > # Run core Java test suite against zookeeper > ant -Dversion=3.4.9-2 -DlastRevision=-1 test-core-java > Buildfile: /<<PKGBUILDDIR>>/build.xml > > init: > > ivy-download: > [get] Getting: > http://repo2.maven.org/maven2/org/apache/ivy/ivy/2.4.0/ivy-2.4.0.jar > [get] To: /<<PKGBUILDDIR>>/src/java/lib/ivy-2.4.0.jar > > ivy-taskdef: > > ivy-init: > > ivy-retrieve: > [ivy:retrieve] :: Apache Ivy 2.4.0 - 20141213170938 :: > http://ant.apache.org/ivy/ :: > [ivy:retrieve] :: loading settings :: file = /<<PKGBUILDDIR>>/ivysettings.xml > [ivy:retrieve] :: resolving dependencies :: > org.apache.zookeeper#zookeeper;3.4.9-2 > [ivy:retrieve] confs: [default] > > BUILD FAILED > /<<PKGBUILDDIR>>/build.xml:364: impossible to resolve dependencies: > java.io.FileNotFoundException: > /home/user42/.ant/cache/resolved-org.apache.zookeeper-zookeeper-3.4.9-2.xml > (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at > org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorUpdater.update(XmlModuleDescriptorUpdater.java:135) > at > org.apache.ivy.plugins.parser.xml.XmlModuleDescriptorParser.toIvyFile(XmlModuleDescriptorParser.java:160) > at > org.apache.ivy.core.module.descriptor.DefaultModuleDescriptor.toIvyFile(DefaultModuleDescriptor.java:561) > at > org.apache.ivy.core.cache.DefaultResolutionCacheManager.saveResolvedModuleDescriptor(DefaultResolutionCacheManager.java:176) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:245) > at > org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:197) > at org.apache.ivy.Ivy.resolve(Ivy.java:508) > at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:330) > at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:271) > at > org.apache.ivy.ant.IvyPostResolveTask.ensureResolved(IvyPostResolveTask.java:228) > at > org.apache.ivy.ant.IvyPostResolveTask.prepareAndCheck(IvyPostResolveTask.java:179) > at org.apache.ivy.ant.IvyRetrieve.doExecute(IvyRetrieve.java:88) > at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:271) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) > at org.apache.tools.ant.Task.perform(Task.java:348) > at org.apache.tools.ant.Target.execute(Target.java:435) > at org.apache.tools.ant.Target.performTasks(Target.java:456) > at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405) > at org.apache.tools.ant.Project.executeTarget(Project.java:1376) > at > org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) > at org.apache.tools.ant.Project.executeTargets(Project.java:1260) > at org.apache.tools.ant.Main.runBuild(Main.java:857) > at org.apache.tools.ant.Main.startAnt(Main.java:236) > at org.apache.tools.ant.launch.Launcher.run(Launcher.java:287) > at org.apache.tools.ant.launch.Launcher.main(Launcher.java:113) > > Total time: 7 seconds > debian/rules:90: recipe for target 'override_dh_auto_test-indep' failed > make[1]: *** [override_dh_auto_test-indep] Error 1 The full build log is available from: http://aws-logs.debian.net/2017/04/18/zookeeper_3.4.9-2_testing-i386.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
