I talked to xmvn maintainer and it seems that xmvn uses asm 3 to analyze the code after the build.

This library do not support java8 syntax. I was asked to open a BZ for it [1]

Now we are thinking how to workaround the issue before the fix will be available.

Thanks,

Piotr

[1] https://bugzilla.redhat.com/1381883

On Wed, Oct 5, 2016 at 10:00 AM, Piotr Kliczewski <pkliczew@redhat.com> wrote:

Actually I saw f24 output, sorry. Still looking into it.

On Wed, Oct 5, 2016 at 9:58 AM, Piotr Kliczewski <pkliczew@redhat.com> wrote:

On Wed, Oct 5, 2016 at 9:58 AM, Piotr Kliczewski <pkliczew@redhat.com> wrote:

Sandro,

Thank you, changing java dept in spec to

BuildRequires: java-1.8.0-openjdk-devel >= 1:1.8.0

helped

On Wed, Oct 5, 2016 at 9:35 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

On Wed, Oct 5, 2016 at 9:34 AM, Piotr Kliczewski <pkliczew@redhat.com> wrote:

On Wed, Oct 5, 2016 at 9:01 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

make[1]: Leaving directory `/home/jenkins/workspace/vdsm-jsonrpc-java_master_check-patch-el7-x86_64/vdsm-jsonrpc-java/rpmbuild/BUILD/vdsm-jsonrpc-java-1.3.1_master'

+ xmvn-install -R .xmvn-reactor -n vdsm-jsonrpc-java -d /home/jenkins/workspace/vdsm-jsonrpc-java_master_check-patch-el7-x86_64/vdsm-jsonrpc-java/rpmbuild/BUILDROOT/vdsm-jsonrpc-java-1.3.1-master.el7.centos.x86_64

[INFO] ===============================================

[INFO] SOURCE ARTIFACT:

[INFO]     groupId: org.ovirt.vdsm-jsonrpc-java

[INFO]  artifactId: root

[INFO]   extension: pom

[INFO]  classifier: 

[INFO]     version: 1.3.1-SNAPSHOT

[INFO]  stereotype: pom

[INFO]   namespace: 

[INFO]        file: /home/jenkins/workspace/vdsm-jsonrpc-java_master_check-patch-el7-x86_64/vdsm-jsonrpc-java/rpmbuild/BUILD/vdsm-jsonrpc-java-1.3.1_master/pom.xml

[INFO] -----------------------------------------------

[INFO] TARGET ARTIFACT:

[INFO]     groupId: JPP/vdsm-jsonrpc-java

[INFO]  artifactId: root

[INFO]   extension: pom

[INFO]  classifier: 

[INFO]     version: SYSTEM

[INFO]  stereotype: pom

[INFO]   namespace: 

[INFO]        file: usr/share/maven-poms/JPP.vdsm-jsonrpc-java-root.pom

[INFO] ===============================================

java.lang.ArrayIndexOutOfBoundsException: 4648

at org.objectweb.asm.ClassReader.readClass(Unknown Source)

at org.objectweb.asm.ClassReader.accept(Unknown Source)

at org.objectweb.asm.ClassReader.accept(Unknown Source)

at org.fedoraproject.maven.installer.impl.DefaultInstaller.usesNativeCode(DefaultInstaller.java:545)

at org.fedoraproject.maven.installer.impl.DefaultInstaller.installArtifact(DefaultInstaller.java:574)

at org.fedoraproject.maven.installer.impl.DefaultInstaller.install(DefaultInstaller.java:758)

at org.fedoraproject.maven.tools.installer.InstallerCli.run(InstallerCli.java:174)

at org.fedoraproject.maven.tools.installer.InstallerCli.main(InstallerCli.java:187)

error: Bad exit status from /var/tmp/rpm-tmp.KMxx5N (%install)

RPM build errors:

    Bad exit status from /var/tmp/rpm-tmp.KMxx5N (%install)

Took 71 seconds

===================================

No idea about why this happen, never seen it in other builds. I can only guess that something in the generated pom file is not resolvable by the installer using JDK 1.7.

Maybe try with JDK 1.8 as in Fedora?

This issue started to occur when we moved from JDK 1.7 to 1.8. It would be good to add a bit of verbosity so maybe we would get more info about the failure.

That may be the clue. the EL7 build is using jdk 1.7 not 1.8.

 

 

On Tue, Oct 4, 2016 at 8:58 PM, Martin Perina <mperina@redhat.com> wrote:

Hi Sandro,

could you please take a look at the issue? Is this some bug in maven-local on EL7?

Thanks

Martin

On Fri, Sep 30, 2016 at 2:59 PM, Martin Perina <mperina@redhat.com> wrote:

On Fri, Sep 30, 2016 at 2:56 PM, Piotr Kliczewski <pkliczew@redhat.com> wrote:

Martin,

I restarted the build in the morning to see why it is failing.

Jsonrpc building looks good but later it fails with:

09:37:52 java.lang.ArrayIndexOutOfBoundsException: 24064
09:37:52 	at org.objectweb.asm.ClassReader.readClass(Unknown Source)
09:37:52 	at org.objectweb.asm.ClassReader.accept(Unknown Source)
09:37:52 	at org.objectweb.asm.ClassReader.accept(Unknown Source)
09:37:52 	at org.fedoraproject.maven.installer.impl.DefaultInstaller.usesNativeCode(DefaultInstaller.java:545)
09:37:52 	at org.fedoraproject.maven.installer.impl.DefaultInstaller.installArtifact(DefaultInstaller.java:574)
09:37:52 	at org.fedoraproject.maven.installer.impl.DefaultInstaller.install(DefaultInstaller.java:758)
09:37:52 	at org.fedoraproject.maven.tools.installer.InstallerCli.run(InstallerCli.java:174)
09:37:52 	at org.fedoraproject.maven.tools.installer.InstallerCli.main(InstallerCli.java:187)
09:37:52 error: Bad exit status from /var/tmp/rpm-tmp.kU3zTr (%install)

this issue started to occur with Ravi's patch. I think that is maybe related somehow to java8 changes.

Maybe there is a bug in mavenlocal. We need to investigate.

​I know :-) That's why I wanted someone from CI to take a look as they know much more about those build issues. And because Fedora build works, this is some specific EL7 issue ...
​

 

Thanks,

Piotr

On Fri, Sep 30, 2016 at 2:40 PM, Martin Perina <mperina@redhat.com> wrote:

Hi,

could you please take a look at EL7 build issue for patch [1]? Fedora build is OK, so I'm not sure what we missed that EL7 build is still failing ...

Thanks

Martin

[1] https://gerrit.ovirt.org/64481

--

Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

--

Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com