You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aurora.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2017/10/23 20:02:19 UTC
Build failed in Jenkins: Aurora #1858
See <https://builds.apache.org/job/Aurora/1858/display/redirect?page=changes>
Changes:
[david] Add sorting and filtering controls for TaskList
------------------------------------------
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-4 (ubuntu trusty) in workspace <https://builds.apache.org/job/Aurora/ws/>
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/aurora.git
> git init <https://builds.apache.org/job/Aurora/ws/> # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/aurora.git
> git --version # timeout=10
> git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url https://git-wip-us.apache.org/repos/asf/aurora.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://git-wip-us.apache.org/repos/asf/aurora.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/aurora.git
> git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 5b91150fd0668c23b178d80516427763764ac2d3 (origin/master)
Commit message: "Add sorting and filtering controls for TaskList"
> git config core.sparsecheckout # timeout=10
> git checkout -f 5b91150fd0668c23b178d80516427763764ac2d3
> git rev-list ec640117c273f51e26089cd83ba325be9e8a0e89 # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
[Aurora] $ /bin/bash -xe /tmp/jenkins2427407600627764864.sh
+ export HOME=<https://builds.apache.org/job/Aurora/ws/.home>
+ HOME=<https://builds.apache.org/job/Aurora/ws/.home>
++ awk '/^MemAvailable:/{print $2}' /proc/meminfo
+ available_mem_k=
+ echo
+ threshold_mem_k=4194304
+ (( threshold_mem_k > available_mem_k ))
+ echo 'Less than 4 GiB memory available. Bailing.'
Less than 4 GiB memory available. Bailing.
+ exit 1
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Jenkins build is back to normal : Aurora #1859
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Aurora/1859/display/redirect?page=changes>
Re: Build failed in Jenkins: Aurora #1858
Posted by Bill Farner <wf...@apache.org>.
I suppose the point is moot, since we have no control over available memory
being claimed after our build starts. Looks like the jenkins slaves are
configured with 2 executors for the most part. Next time we spot this,
let's try to determine the neighbor build; perhaps there's a common culprit
eating memory.
On Mon, Oct 30, 2017 at 12:21 PM, Stephan Erb <se...@apache.org> wrote:
> Actually there was never a discussion. I just enabled it as a test and
> then totally forgot about it because it worked surprisingly well.
>
> I believe we won't use more than 1-2 GB. I simply added the remaining 2
> as an additional safeguard when something else is launched on the
> Jenkins node shortly after we have passed the guard.
>
> On Tue, 2017-10-24 at 21:38 -0700, Bill Farner wrote:
> > Possibly rehashing an old discussion - does the build really require
> > 4 GB?
> >
> > On Mon, Oct 23, 2017 at 1:53 PM, Erb, Stephan <Stephan.Erb@blue-yonde
> > r.com>
> > wrote:
> >
> > > Ah, again a node with insufficient memory. I once added a mechanism
> > > to
> > > abort the build early rather than running and eventually failing in
> > > these
> > > cases. This was very helpful for the regular reviewbot but is not
> > > that
> > > helpful for the normal SCM-triggerd build.
> > >
> > > Can anyone think of a better way to handle this case here?
> > >
> > >
> > > On 23.10.17, 22:02, "Apache Jenkins Server" <jenkins@builds.apache.
> > > org>
> > > wrote:
> > >
> > > See <https://builds.apache.org/job/Aurora/1858/display/
> > > redirect?page=changes>
> > >
> > > Changes:
> > >
> > > [david] Add sorting and filtering controls for TaskList
> > >
> > > ------------------------------------------
> > > Started by an SCM change
> > > Started by an SCM change
> > > [EnvInject] - Loading node environment variables.
> > > Building remotely on ubuntu-4 (ubuntu trusty) in workspace <
> > > https://builds.apache.org/job/Aurora/ws/>;
> > > Wiping out workspace first.
> > > Cloning the remote Git repository
> > > Cloning repository https://git-wip-us.apache.org/repos/asf/auro
> > > ra.git
> > > > git init <https://builds.apache.org/job/Aurora/ws/> #
> > > timeout=10
> > > Fetching upstream changes from https://git-wip-us.apache.org/
> > > repos/asf/aurora.git
> > > > git --version # timeout=10
> > > > git fetch --tags --progress https://git-wip-us.apache.org/
> > > repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> > > > git config remote.origin.url https://git-wip-us.apache.org/
> > > repos/asf/aurora.git # timeout=10
> > > > git config --add remote.origin.fetch
> > > +refs/heads/*:refs/remotes/origin/*
> > > # timeout=10
> > > > git config remote.origin.url https://git-wip-us.apache.org/
> > > repos/asf/aurora.git # timeout=10
> > > Fetching upstream changes from https://git-wip-us.apache.org/
> > > repos/asf/aurora.git
> > > > git fetch --tags --progress https://git-wip-us.apache.org/
> > > repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> > > > git rev-parse origin/master^{commit} # timeout=10
> > > Checking out Revision 5b91150fd0668c23b178d80516427763764ac2d3
> > > (origin/master)
> > > Commit message: "Add sorting and filtering controls for
> > > TaskList"
> > > > git config core.sparsecheckout # timeout=10
> > > > git checkout -f 5b91150fd0668c23b178d80516427763764ac2d3
> > > > git rev-list ec640117c273f51e26089cd83ba325be9e8a0e89 #
> > > timeout=10
> > > Cleaning workspace
> > > > git rev-parse --verify HEAD # timeout=10
> > > Resetting working tree
> > > > git reset --hard # timeout=10
> > > > git clean -fdx # timeout=10
> > > [Aurora] $ /bin/bash -xe /tmp/jenkins2427407600627764864.sh
> > > + export HOME=<https://builds.apache.org/job/Aurora/ws/.home>
> > > + HOME=<https://builds.apache.org/job/Aurora/ws/.home>
> > > ++ awk '/^MemAvailable:/{print $2}' /proc/meminfo
> > > + available_mem_k=
> > > + echo
> > >
> > > + threshold_mem_k=4194304
> > > + (( threshold_mem_k > available_mem_k ))
> > > + echo 'Less than 4 GiB memory available. Bailing.'
> > > Less than 4 GiB memory available. Bailing.
> > > + exit 1
> > > Build step 'Execute shell' marked build as failure
> > > Recording test results
> > > ERROR: Step ?Publish JUnit test result report? failed: No test
> > > report
> > > files were found. Configuration error?
> > >
> > >
> > >
> > >
>
Re: Build failed in Jenkins: Aurora #1858
Posted by Stephan Erb <se...@apache.org>.
Actually there was never a discussion. I just enabled it as a test and
then totally forgot about it because it worked surprisingly well.
I believe we won't use more than 1-2 GB. I simply added the remaining 2
as an additional safeguard when something else is launched on the
Jenkins node shortly after we have passed the guard.
On Tue, 2017-10-24 at 21:38 -0700, Bill Farner wrote:
> Possibly rehashing an old discussion - does the build really require
> 4 GB?
>
> On Mon, Oct 23, 2017 at 1:53 PM, Erb, Stephan <Stephan.Erb@blue-yonde
> r.com>
> wrote:
>
> > Ah, again a node with insufficient memory. I once added a mechanism
> > to
> > abort the build early rather than running and eventually failing in
> > these
> > cases. This was very helpful for the regular reviewbot but is not
> > that
> > helpful for the normal SCM-triggerd build.
> >
> > Can anyone think of a better way to handle this case here?
> >
> >
> > On 23.10.17, 22:02, "Apache Jenkins Server" <jenkins@builds.apache.
> > org>
> > wrote:
> >
> > See <https://builds.apache.org/job/Aurora/1858/display/
> > redirect?page=changes>
> >
> > Changes:
> >
> > [david] Add sorting and filtering controls for TaskList
> >
> > ------------------------------------------
> > Started by an SCM change
> > Started by an SCM change
> > [EnvInject] - Loading node environment variables.
> > Building remotely on ubuntu-4 (ubuntu trusty) in workspace <
> > https://builds.apache.org/job/Aurora/ws/>;
> > Wiping out workspace first.
> > Cloning the remote Git repository
> > Cloning repository https://git-wip-us.apache.org/repos/asf/auro
> > ra.git
> > > git init <https://builds.apache.org/job/Aurora/ws/> #
> > timeout=10
> > Fetching upstream changes from https://git-wip-us.apache.org/
> > repos/asf/aurora.git
> > > git --version # timeout=10
> > > git fetch --tags --progress https://git-wip-us.apache.org/
> > repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> > > git config remote.origin.url https://git-wip-us.apache.org/
> > repos/asf/aurora.git # timeout=10
> > > git config --add remote.origin.fetch
> > +refs/heads/*:refs/remotes/origin/*
> > # timeout=10
> > > git config remote.origin.url https://git-wip-us.apache.org/
> > repos/asf/aurora.git # timeout=10
> > Fetching upstream changes from https://git-wip-us.apache.org/
> > repos/asf/aurora.git
> > > git fetch --tags --progress https://git-wip-us.apache.org/
> > repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> > > git rev-parse origin/master^{commit} # timeout=10
> > Checking out Revision 5b91150fd0668c23b178d80516427763764ac2d3
> > (origin/master)
> > Commit message: "Add sorting and filtering controls for
> > TaskList"
> > > git config core.sparsecheckout # timeout=10
> > > git checkout -f 5b91150fd0668c23b178d80516427763764ac2d3
> > > git rev-list ec640117c273f51e26089cd83ba325be9e8a0e89 #
> > timeout=10
> > Cleaning workspace
> > > git rev-parse --verify HEAD # timeout=10
> > Resetting working tree
> > > git reset --hard # timeout=10
> > > git clean -fdx # timeout=10
> > [Aurora] $ /bin/bash -xe /tmp/jenkins2427407600627764864.sh
> > + export HOME=<https://builds.apache.org/job/Aurora/ws/.home>
> > + HOME=<https://builds.apache.org/job/Aurora/ws/.home>
> > ++ awk '/^MemAvailable:/{print $2}' /proc/meminfo
> > + available_mem_k=
> > + echo
> >
> > + threshold_mem_k=4194304
> > + (( threshold_mem_k > available_mem_k ))
> > + echo 'Less than 4 GiB memory available. Bailing.'
> > Less than 4 GiB memory available. Bailing.
> > + exit 1
> > Build step 'Execute shell' marked build as failure
> > Recording test results
> > ERROR: Step ?Publish JUnit test result report? failed: No test
> > report
> > files were found. Configuration error?
> >
> >
> >
> >
Re: Build failed in Jenkins: Aurora #1858
Posted by Bill Farner <wf...@apache.org>.
Possibly rehashing an old discussion - does the build really require 4 GB?
On Mon, Oct 23, 2017 at 1:53 PM, Erb, Stephan <St...@blue-yonder.com>
wrote:
> Ah, again a node with insufficient memory. I once added a mechanism to
> abort the build early rather than running and eventually failing in these
> cases. This was very helpful for the regular reviewbot but is not that
> helpful for the normal SCM-triggerd build.
>
> Can anyone think of a better way to handle this case here?
>
>
> On 23.10.17, 22:02, "Apache Jenkins Server" <je...@builds.apache.org>
> wrote:
>
> See <https://builds.apache.org/job/Aurora/1858/display/
> redirect?page=changes>
>
> Changes:
>
> [david] Add sorting and filtering controls for TaskList
>
> ------------------------------------------
> Started by an SCM change
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on ubuntu-4 (ubuntu trusty) in workspace <
> https://builds.apache.org/job/Aurora/ws/>
> Wiping out workspace first.
> Cloning the remote Git repository
> Cloning repository https://git-wip-us.apache.org/repos/asf/aurora.git
> > git init <https://builds.apache.org/job/Aurora/ws/> # timeout=10
> Fetching upstream changes from https://git-wip-us.apache.org/
> repos/asf/aurora.git
> > git --version # timeout=10
> > git fetch --tags --progress https://git-wip-us.apache.org/
> repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> > git config remote.origin.url https://git-wip-us.apache.org/
> repos/asf/aurora.git # timeout=10
> > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
> # timeout=10
> > git config remote.origin.url https://git-wip-us.apache.org/
> repos/asf/aurora.git # timeout=10
> Fetching upstream changes from https://git-wip-us.apache.org/
> repos/asf/aurora.git
> > git fetch --tags --progress https://git-wip-us.apache.org/
> repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> > git rev-parse origin/master^{commit} # timeout=10
> Checking out Revision 5b91150fd0668c23b178d80516427763764ac2d3
> (origin/master)
> Commit message: "Add sorting and filtering controls for TaskList"
> > git config core.sparsecheckout # timeout=10
> > git checkout -f 5b91150fd0668c23b178d80516427763764ac2d3
> > git rev-list ec640117c273f51e26089cd83ba325be9e8a0e89 # timeout=10
> Cleaning workspace
> > git rev-parse --verify HEAD # timeout=10
> Resetting working tree
> > git reset --hard # timeout=10
> > git clean -fdx # timeout=10
> [Aurora] $ /bin/bash -xe /tmp/jenkins2427407600627764864.sh
> + export HOME=<https://builds.apache.org/job/Aurora/ws/.home>
> + HOME=<https://builds.apache.org/job/Aurora/ws/.home>
> ++ awk '/^MemAvailable:/{print $2}' /proc/meminfo
> + available_mem_k=
> + echo
>
> + threshold_mem_k=4194304
> + (( threshold_mem_k > available_mem_k ))
> + echo 'Less than 4 GiB memory available. Bailing.'
> Less than 4 GiB memory available. Bailing.
> + exit 1
> Build step 'Execute shell' marked build as failure
> Recording test results
> ERROR: Step ?Publish JUnit test result report? failed: No test report
> files were found. Configuration error?
>
>
>
>
Re: Build failed in Jenkins: Aurora #1858
Posted by "Erb, Stephan" <St...@blue-yonder.com>.
Ah, again a node with insufficient memory. I once added a mechanism to abort the build early rather than running and eventually failing in these cases. This was very helpful for the regular reviewbot but is not that helpful for the normal SCM-triggerd build.
Can anyone think of a better way to handle this case here?
On 23.10.17, 22:02, "Apache Jenkins Server" <je...@builds.apache.org> wrote:
See <https://builds.apache.org/job/Aurora/1858/display/redirect?page=changes>
Changes:
[david] Add sorting and filtering controls for TaskList
------------------------------------------
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-4 (ubuntu trusty) in workspace <https://builds.apache.org/job/Aurora/ws/>
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/aurora.git
> git init <https://builds.apache.org/job/Aurora/ws/> # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/aurora.git
> git --version # timeout=10
> git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url https://git-wip-us.apache.org/repos/asf/aurora.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://git-wip-us.apache.org/repos/asf/aurora.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/aurora.git
> git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/aurora.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 5b91150fd0668c23b178d80516427763764ac2d3 (origin/master)
Commit message: "Add sorting and filtering controls for TaskList"
> git config core.sparsecheckout # timeout=10
> git checkout -f 5b91150fd0668c23b178d80516427763764ac2d3
> git rev-list ec640117c273f51e26089cd83ba325be9e8a0e89 # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
[Aurora] $ /bin/bash -xe /tmp/jenkins2427407600627764864.sh
+ export HOME=<https://builds.apache.org/job/Aurora/ws/.home>
+ HOME=<https://builds.apache.org/job/Aurora/ws/.home>
++ awk '/^MemAvailable:/{print $2}' /proc/meminfo
+ available_mem_k=
+ echo
+ threshold_mem_k=4194304
+ (( threshold_mem_k > available_mem_k ))
+ echo 'Less than 4 GiB memory available. Bailing.'
Less than 4 GiB memory available. Bailing.
+ exit 1
Build step 'Execute shell' marked build as failure
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?