www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gav <ipv6g...@gmail.com>
Subject Re: IBM JDK, JAVA_HOME is not defined correctly on ubuntu-5 and ubuntu-6
Date Tue, 28 Jun 2016 22:21:10 GMT
I'll take a look shortly

Gav...

On Wed, Jun 29, 2016 at 12:58 AM, Alex Harui <aharui@adobe.com> wrote:

> I'm not an expert, but can't you set these properties in your build
> configuration?
>
> -Alex
>
> On 6/28/16, 3:40 AM, "Keith W" <keith.wall@gmail.com> wrote:
>
> >Hi Builds,
> >
> >Would anyone be able to take a look at this please?
> >
> >Kind regards Keith Wall.
> >
> >On 23 June 2016 at 09:25, Keith W <keith.wall@gmail.com> wrote:
> >> Hello Builds,
> >>
> >> Could someone take a look at this please?  I don't see any open INFRA
> >> issue tracking this problem.
> >>
> >> Thanks in advance, Keith Wall.
> >>
> >>
> >>
> >> On 21 June 2016 at 10:19, Keith W <keith.wall@gmail.com> wrote:
> >>> Hello Builds,
> >>>
> >>> We, Apache Qpid, keep seeing the following problem on a job configured
> >>> to use the "IBM 1.7 64-bit (on Ubuntu only)". I am seeing the problem
> >>> on ubuntu-5 and ubuntu-6.
> >>>
> >>> An example failure is here:
> >>>
> >>>
> >>>
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-IBM
> >>>JDK1.7/1599/console
> >>>
> >>> and the text of the failure in copied below.
> >>>
> >>> If someone could take a look, that would be appreciated.
> >>>
> >>> Kind regards, Keith Wall.
> >>>
> >>>
> >>>
> >>>
> >>> [locks-and-latches] Have all the locks, build can start
> >>> [Qpid-Java-Java-Test-IBMJDK1.7] $
> >>> /home/jenkins/tools/maven/apache-maven-3.0.4/bin/mvn -f ./pom.xml
> >>> "-Dprofile.specific.excludes=JavaTransientExcludes Java010Excludes
> >>> IBMJDKExcludes"
> >>>
> >>>-Dtest.overridden.properties=./test-profiles/apache-ci.test.overridden.p
> >>>roperties
> >>> clean verify -Pjava-mms.0-10 -fae
> >>> Error: JAVA_HOME is not defined correctly.
> >>>   We cannot execute /home/jenkins/tools/java/ibm-1.7-64/bin/java
> >>> Build step 'Invoke top-level Maven targets' marked build as failure
> >>> [locks-and-latches] Releasing all the locks
> >>> [locks-and-latches] All the locks released
> >>> Archiving artifacts
> >>> Recording test results
> >>> ERROR: Step ?Publish JUnit test result report? failed: No test report
> >>> files were found. Configuration error?
> >>> Sending e-mails to: notifications@qpid.apache.org
> >>> Finished: FAILURE
>
>


-- 
Gav...

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message