You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pirk.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2016/07/21 02:56:16 UTC
Build failed in Jenkins: pirk #8
See <https://builds.apache.org/job/pirk/8/changes>
Changes:
[eawilliams] [trivial] -- Enhancements to build XML and Paillier class - closes
[eawilliams] [none] -- Replace multi if-else with switch stmts - closes
------------------------------------------
Started by an SCM change
[EnvInject] - Loading node environment variables.
JDK installation skipped: Unknown CPU architecture: ppc64le
Building remotely on ubuntu-ppc64le (ppc64le) in workspace <https://builds.apache.org/job/pirk/ws/>
JDK installation skipped: Unknown CPU architecture: ppc64le
JDK installation skipped: Unknown CPU architecture: ppc64le
Cloning the remote Git repository
Cloning repository git://git.apache.org/incubator-pirk.git/
> git init <https://builds.apache.org/job/pirk/ws/> # timeout=10
Fetching upstream changes from git://git.apache.org/incubator-pirk.git/
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress git://git.apache.org/incubator-pirk.git/ +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url git://git.apache.org/incubator-pirk.git/ # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url git://git.apache.org/incubator-pirk.git/ # timeout=10
Fetching upstream changes from git://git.apache.org/incubator-pirk.git/
> git -c core.askpass=true fetch --tags --progress git://git.apache.org/incubator-pirk.git/ +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 9f3eb4bebff6ef570ed9a840e3bed15f91e6b950 (refs/remotes/origin/master)
JDK installation skipped: Unknown CPU architecture: ppc64le
> git config core.sparsecheckout # timeout=10
> git checkout -f 9f3eb4bebff6ef570ed9a840e3bed15f91e6b950
> git rev-list 081494d4f676e5a65dbb9ec5324898cf80a585f0 # timeout=10
JDK installation skipped: Unknown CPU architecture: ppc64le
ERROR: Maven Home /home/jenkins/tools/maven/apache-maven-3.0.4 doesn’t exist
Re: Build failed in Jenkins: pirk #8
Posted by Ellison Anne Williams <ea...@gmail.com>.
This is OBE at this point, but I triggered a build manually yesterday
afternoon and everything ran through without issue.
Since Jenkins is already set up (and works well most of the time), I don't
see any need to disable it and completely switch over to Travis.
On Thu, Jul 21, 2016 at 11:16 AM, Suneel Marthi <sm...@apache.org> wrote:
> I have seen this happen occasionally on other projects too, in large part
> its caused by multiple builds from different projects queued up on a server
> and forking multiple jvms to execute unit tests and integration tests and
> crashing.
>
> I bet it would work now if u trigger a manual build.
>
> For a project like Pirk Travis is a good option, I have seen Jenkins being
> more reliable than Travis for large scale integration tests involving
> MapReduce, Kafka and the big data friends.
>
> But Pirk is plain java for the most part, and shuld be good with Travis.
>
> On Thu, Jul 21, 2016 at 11:08 AM, Tim Ellison <t....@gmail.com>
> wrote:
>
> > On 21/07/16 03:56, Apache Jenkins Server wrote:
> > > See <https://builds.apache.org/job/pirk/8/changes>
> > >
> > > Changes:
> > >
> > > [eawilliams] [trivial] -- Enhancements to build XML and Paillier class
> -
> > closes
> > >
> > > [eawilliams] [none] -- Replace multi if-else with switch stmts - closes
> > >
> > > ------------------------------------------
> > > Started by an SCM change
> > > [EnvInject] - Loading node environment variables.
> > > JDK installation skipped: Unknown CPU architecture: ppc64le
> > > Building remotely on ubuntu-ppc64le (ppc64le) in workspace <
> > https://builds.apache.org/job/pirk/ws/>
> > > JDK installation skipped: Unknown CPU architecture: ppc64le
> > > JDK installation skipped: Unknown CPU architecture: ppc64le
> >
> > It looks like we were scheduled onto a poorly configured Jenkins node
> > causing this build break.
> >
> > Either we take it up with the build list, or work around it by tying our
> > job to a known-good node. Travis seems to be faster, so I haven't been
> > too fussed by this note.
> >
> > Anyone want to tackle this?
> > Tim
> >
>
Re: Build failed in Jenkins: pirk #8
Posted by Suneel Marthi <sm...@apache.org>.
I have seen this happen occasionally on other projects too, in large part
its caused by multiple builds from different projects queued up on a server
and forking multiple jvms to execute unit tests and integration tests and
crashing.
I bet it would work now if u trigger a manual build.
For a project like Pirk Travis is a good option, I have seen Jenkins being
more reliable than Travis for large scale integration tests involving
MapReduce, Kafka and the big data friends.
But Pirk is plain java for the most part, and shuld be good with Travis.
On Thu, Jul 21, 2016 at 11:08 AM, Tim Ellison <t....@gmail.com> wrote:
> On 21/07/16 03:56, Apache Jenkins Server wrote:
> > See <https://builds.apache.org/job/pirk/8/changes>
> >
> > Changes:
> >
> > [eawilliams] [trivial] -- Enhancements to build XML and Paillier class -
> closes
> >
> > [eawilliams] [none] -- Replace multi if-else with switch stmts - closes
> >
> > ------------------------------------------
> > Started by an SCM change
> > [EnvInject] - Loading node environment variables.
> > JDK installation skipped: Unknown CPU architecture: ppc64le
> > Building remotely on ubuntu-ppc64le (ppc64le) in workspace <
> https://builds.apache.org/job/pirk/ws/>
> > JDK installation skipped: Unknown CPU architecture: ppc64le
> > JDK installation skipped: Unknown CPU architecture: ppc64le
>
> It looks like we were scheduled onto a poorly configured Jenkins node
> causing this build break.
>
> Either we take it up with the build list, or work around it by tying our
> job to a known-good node. Travis seems to be faster, so I haven't been
> too fussed by this note.
>
> Anyone want to tackle this?
> Tim
>
Re: Build failed in Jenkins: pirk #8
Posted by Tim Ellison <t....@gmail.com>.
On 21/07/16 03:56, Apache Jenkins Server wrote:
> See <https://builds.apache.org/job/pirk/8/changes>
>
> Changes:
>
> [eawilliams] [trivial] -- Enhancements to build XML and Paillier class - closes
>
> [eawilliams] [none] -- Replace multi if-else with switch stmts - closes
>
> ------------------------------------------
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> JDK installation skipped: Unknown CPU architecture: ppc64le
> Building remotely on ubuntu-ppc64le (ppc64le) in workspace <https://builds.apache.org/job/pirk/ws/>
> JDK installation skipped: Unknown CPU architecture: ppc64le
> JDK installation skipped: Unknown CPU architecture: ppc64le
It looks like we were scheduled onto a poorly configured Jenkins node
causing this build break.
Either we take it up with the build list, or work around it by tying our
job to a known-good node. Travis seems to be faster, so I haven't been
too fussed by this note.
Anyone want to tackle this?
Tim
Jenkins build is back to normal : pirk #9
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/pirk/9/changes>