You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sentry.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2018/07/23 17:12:55 UTC
Sentry-jdk-1.8 - Build # 80 - Still Failing
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #80)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/80/ to view the results.
Sentry-jdk-1.8 - Build # 130 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #130)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/130/ to view the results.
Sentry-jdk-1.8 - Build # 129 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #129)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/129/ to view the results.
Sentry-jdk-1.8 - Build # 128 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #128)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/128/ to view the results.
Sentry-jdk-1.8 - Build # 127 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #127)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/127/ to view the results.
Sentry-jdk-1.8 - Build # 126 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #126)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/126/ to view the results.
Sentry-jdk-1.8 - Build # 125 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #125)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/125/ to view the results.
Sentry-jdk-1.8 - Build # 124 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #124)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/124/ to view the results.
Sentry-jdk-1.8 - Build # 123 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #123)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/123/ to view the results.
Sentry-jdk-1.8 - Build # 122 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #122)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/122/ to view the results.
Sentry-jdk-1.8 - Build # 121 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #121)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/121/ to view the results.
Sentry-jdk-1.8 - Build # 120 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #120)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/120/ to view the results.
Sentry-jdk-1.8 - Build # 119 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #119)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/119/ to view the results.
Sentry-jdk-1.8 - Build # 118 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #118)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/118/ to view the results.
Sentry-jdk-1.8 - Build # 117 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #117)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/117/ to view the results.
Sentry-jdk-1.8 - Build # 116 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #116)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/116/ to view the results.
Sentry-jdk-1.8 - Build # 115 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #115)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/115/ to view the results.
Sentry-jdk-1.8 - Build # 114 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #114)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/114/ to view the results.
Sentry-jdk-1.8 - Build # 113 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #113)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/113/ to view the results.
Sentry-jdk-1.8 - Build # 112 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #112)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/112/ to view the results.
Sentry-jdk-1.8 - Build # 111 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #111)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/111/ to view the results.
Re: Sentry-jdk-1.8 - Build # 110 - Still Failing
Posted by Kalyan Kumar Kalvagadda <kk...@cloudera.com.INVALID>.
Thanks lina for following it up. I some how missed you messages.
On Fri, Jul 27, 2018 at 10:32 AM Na Li <li...@cloudera.com> wrote:
> Colm,
>
> I have filed INFRA-16822, and Chris Lambertus has responded to the
> latest error " The "class not found" problem seems to have cropped up
> after our jenkins migration, and requires restarting the slave, which I
> have now done for H17. Please try again, and let me know if you run into
> other slaves that have that problem so I can restart them too. "
>
> Since then there is no build error. Let's wait for several more days to
> see if there are more builds and if they fail.
>
> Do you know what triggers the build at
> https://builds.apache.org/job/Sentry-jdk-1.8/?
>
> Thanks,
>
> Lina
>
> On Fri, Jul 27, 2018 at 3:39 AM, Colm O hEigeartaigh <co...@apache.org>
> wrote:
>
>> I recommend filing a JIRA with INFRA - or update the previous JIRA if it's
>> still open.
>>
>> Colm.
>>
>> On Thu, Jul 26, 2018 at 4:32 PM, Na Li <li...@cloudera.com> wrote:
>>
>> > Colm,
>> >
>> > Thanks for your update! Your change helped, but we still have build
>> issue.
>> > We need to figure out next step to fix the build issue with
>> "java.lang.NoClassDefFoundError:
>> > hudson.model.Computer".
>> >
>> > 1) Before your change, the exception callstack is at
>> > https://builds.apache.org/job/Sentry-jdk-1.8/126/console
>> >
>> > Started by an SCM change
>> > [EnvInject] - Loading node environment variables.
>> > Building remotely on H17 <https://builds.apache.org/computer/H17>
>> (Hadoop xenial) in workspace
>> /home/jenkins/jenkins-slave/workspace/Sentry-jdk-1.8
>> > > git rev-parse --is-inside-work-tree # timeout=10
>> > Fetching changes from the remote Git repository
>> > > git config remote.origin.url
>> https://git-wip-us.apache.org/repos/asf/sentry.git # timeout=10
>> > Fetching upstream changes from
>> https://git-wip-us.apache.org/repos/asf/sentry.git
>> > > git --version # timeout=10
>> > > git fetch --tags --progress
>> https://git-wip-us.apache.org/repos/asf/sentry.git
>> +refs/heads/*:refs/remotes/origin/*
>> > ERROR: Error fetching remote repo 'origin'
>> > hudson.plugins.git.GitException: Failed to fetch from
>> https://git-wip-us.apache.org/repos/asf/sentry.git
>> > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888)
>> > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155)
>> > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
>> > at hudson.scm.SCM.checkout(SCM.java:504)
>> > at
>> hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
>> > at
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
>> > at
>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
>> > at
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
>> > at hudson.model.Run.execute(Run.java:1794)
>> > at
>> hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
>> > at
>> hudson.model.ResourceController.execute(ResourceController.java:97)
>> > at hudson.model.Executor.run(Executor.java:429)
>> > Caused by: hudson.plugins.git.GitException: Command "git fetch --tags
>> --progress https://git-wip-us.apache.org/repos/asf/sentry.git
>> +refs/heads/*:refs/remotes/origin/*" returned status code 128:
>> > stdout:
>> >
>> >
>> >
>> > 2) After your change at build 129, the callstack is at
>> > https://builds.apache.org/job/Sentry-jdk-1.8/130/console.
>> >
>> > Cloning the remote Git repository
>> > Cloning repository https://git-wip-us.apache.org/repos/asf/sentry.git
>> > > git init /home/jenkins/jenkins-slave/workspace/Sentry-jdk-1.8 #
>> timeout=10
>> > Fetching upstream changes from
>> https://git-wip-us.apache.org/repos/asf/sentry.git
>> > > git --version # timeout=10
>> > > git fetch --tags --progress
>> https://git-wip-us.apache.org/repos/asf/sentry.git
>> +refs/heads/*:refs/remotes/origin/*
>> > > git config remote.origin.url
>> https://git-wip-us.apache.org/repos/asf/sentry.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/sentry.git # timeout=10
>> > Fetching upstream changes from
>> https://git-wip-us.apache.org/repos/asf/sentry.git
>> > > git fetch --tags --progress
>> https://git-wip-us.apache.org/repos/asf/sentry.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 3dab053e18b4197e97f4a654e2707cb1eb673047
>> (refs/remotes/origin/master)
>> > > git config core.sparsecheckout # timeout=10
>> > > git checkout -f 3dab053e18b4197e97f4a654e2707cb1eb673047
>> > Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to H17
>> > at
>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
>> > at
>> hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
>> > at hudson.remoting.Channel.call(Channel.java:955)
>> > at
>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
>> > at com.sun.proxy.$Proxy117.withRepository(Unknown Source)
>> > at
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)
>> > at
>> hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271)
>> > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)
>> > at hudson.scm.SCM.checkout(SCM.java:504)
>> > at
>> hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
>> > at
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
>> > at
>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
>> > at
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
>> > at hudson.model.Run.execute(Run.java:1794)
>> > at
>> hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
>> > at
>> hudson.model.ResourceController.execute(ResourceController.java:97)
>> > at hudson.model.Executor.run(Executor.java:429)
>> > java.lang.NoClassDefFoundError: hudson.model.Computer
>> > at
>> org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29)
>> > at
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72)
>> > at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
>> > at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> > at java.lang.reflect.Method.invoke(Method.java:498)
>> > at
>> hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929)
>> > at
>> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903)
>> > at
>> hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855)
>> > at hudson.remoting.UserRequest.perform(UserRequest.java:212)
>> > at hudson.remoting.UserRequest.perform(UserRequest.java:54)
>> > at hudson.remoting.Request$2.run(Request.java:369)
>> > at
>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>> > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> > at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> > at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> > at java.lang.Thread.run(Thread.java:748)
>> > Caused: java.io.IOException: Remote call on H17 failed
>> > at hudson.remoting.Channel.call(Channel.java:961)
>> > at
>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
>> > at com.sun.proxy.$Proxy117.withRepository(Unknown Source)
>> > at
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)
>> > at
>> hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271)
>> > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)
>> > at hudson.scm.SCM.checkout(SCM.java:504)
>> > at
>> hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
>> > at
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
>> > at
>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
>> > at
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
>> > at hudson.model.Run.execute(Run.java:1794)
>> > at
>> hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
>> > at
>> hudson.model.ResourceController.execute(ResourceController.java:97)
>> > at hudson.model.Executor.run(Executor.java:429)
>> >
>> >
>> > Thanks,
>> >
>> > Lina
>> >
>> > On Thu, Jul 26, 2018 at 4:05 AM, Colm O hEigeartaigh <
>> coheigea@apache.org>
>> > wrote:
>> >
>> >> Hi Lina,
>> >>
>> >> I made the change for both the JDK8 build and the staging build, so
>> let's
>> >> see if that makes a difference.
>> >>
>> >> Colm.
>> >>
>> >> On Thu, Jul 26, 2018 at 7:11 AM, Na Li <li...@cloudera.com.invalid>
>> >> wrote:
>> >>
>> >> > Kalyan,
>> >> >
>> >> > to solve the sentry upstream build issue, do you have access to
>> "Please
>> >> > enable 'Delete workspace before build starts' in your build
>> >> configuration."
>> >> > as mentioned in INFRA-16822?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Lina
>> >> >
>> >> > On Wed, Jul 25, 2018 at 11:48 PM, Na Li <li...@cloudera.com>
>> wrote:
>> >> >
>> >> > > Kalyan,
>> >> > >
>> >> > > The build still fails. I found this link https://stackoverflow.
>> >> > > com/questions/21277806/fatal-early-eof-fatal-index-pack-failed. It
>> is
>> >> > > possible that git ran out of memory. I have filed
>> >> https://issues.apache
>> >> > .
>> >> > > org/jira/browse/INFRA-16822
>> >> > >
>> >> > > Do you know if there are other things we can do to bring the build
>> >> back
>> >> > to
>> >> > > green? like change git command on how to get remote repo?
>> >> > >
>> >> > > Thanks,
>> >> > >
>> >> > > Lina
>> >> > >
>> >> > >
>> >> > >
>> >> > > On Wed, Jul 25, 2018 at 11:26 PM, Apache Jenkins Server <
>> >> > > jenkins@builds.apache.org> wrote:
>> >> > >
>> >> > >> The Apache Jenkins build system has built Sentry-jdk-1.8 (build
>> #110)
>> >> > >>
>> >> > >> Status: Still Failing
>> >> > >>
>> >> > >> Check console output at https://builds.apache.org/job/
>> >> > Sentry-jdk-1.8/110/
>> >> > >> to view the results.
>> >> > >
>> >> > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Colm O hEigeartaigh
>> >>
>> >> Talend Community Coder
>> >> http://coders.talend.com
>> >>
>> >
>> >
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>
Re: Sentry-jdk-1.8 - Build # 110 - Still Failing
Posted by Na Li <li...@cloudera.com.INVALID>.
Colm,
I have filed INFRA-16822, and Chris Lambertus has responded to the latest
error " The "class not found" problem seems to have cropped up after our
jenkins migration, and requires restarting the slave, which I have now done
for H17. Please try again, and let me know if you run into other slaves
that have that problem so I can restart them too. "
Since then there is no build error. Let's wait for several more days to see
if there are more builds and if they fail.
Do you know what triggers the build at
https://builds.apache.org/job/Sentry-jdk-1.8/?
Thanks,
Lina
On Fri, Jul 27, 2018 at 3:39 AM, Colm O hEigeartaigh <co...@apache.org>
wrote:
> I recommend filing a JIRA with INFRA - or update the previous JIRA if it's
> still open.
>
> Colm.
>
> On Thu, Jul 26, 2018 at 4:32 PM, Na Li <li...@cloudera.com> wrote:
>
> > Colm,
> >
> > Thanks for your update! Your change helped, but we still have build
> issue.
> > We need to figure out next step to fix the build issue with "java.lang.
> NoClassDefFoundError:
> > hudson.model.Computer".
> >
> > 1) Before your change, the exception callstack is at
> > https://builds.apache.org/job/Sentry-jdk-1.8/126/console
> >
> > Started by an SCM change
> > [EnvInject] - Loading node environment variables.
> > Building remotely on H17 <https://builds.apache.org/computer/H17>
> (Hadoop xenial) in workspace /home/jenkins/jenkins-slave/
> workspace/Sentry-jdk-1.8
> > > git rev-parse --is-inside-work-tree # timeout=10
> > Fetching changes from the remote Git repository
> > > git config remote.origin.url https://git-wip-us.apache.org/
> repos/asf/sentry.git # timeout=10
> > Fetching upstream changes from https://git-wip-us.apache.org/
> repos/asf/sentry.git
> > > git --version # timeout=10
> > > git fetch --tags --progress https://git-wip-us.apache.org/
> repos/asf/sentry.git +refs/heads/*:refs/remotes/origin/*
> > ERROR: Error fetching remote repo 'origin'
> > hudson.plugins.git.GitException: Failed to fetch from
> https://git-wip-us.apache.org/repos/asf/sentry.git
> > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888)
> > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155)
> > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
> > at hudson.scm.SCM.checkout(SCM.java:504)
> > at hudson.model.AbstractProject.checkout(AbstractProject.java:
> 1208)
> > at hudson.model.AbstractBuild$AbstractBuildExecution.
> defaultCheckout(AbstractBuild.java:574)
> > at jenkins.scm.SCMCheckoutStrategy.checkout(
> SCMCheckoutStrategy.java:86)
> > at hudson.model.AbstractBuild$AbstractBuildExecution.run(
> AbstractBuild.java:499)
> > at hudson.model.Run.execute(Run.java:1794)
> > at hudson.maven.MavenModuleSetBuild.run(
> MavenModuleSetBuild.java:543)
> > at hudson.model.ResourceController.execute(
> ResourceController.java:97)
> > at hudson.model.Executor.run(Executor.java:429)
> > Caused by: hudson.plugins.git.GitException: Command "git fetch --tags
> --progress https://git-wip-us.apache.org/repos/asf/sentry.git
> +refs/heads/*:refs/remotes/origin/*" returned status code 128:
> > stdout:
> >
> >
> >
> > 2) After your change at build 129, the callstack is at
> > https://builds.apache.org/job/Sentry-jdk-1.8/130/console.
> >
> > Cloning the remote Git repository
> > Cloning repository https://git-wip-us.apache.org/repos/asf/sentry.git
> > > git init /home/jenkins/jenkins-slave/workspace/Sentry-jdk-1.8 #
> timeout=10
> > Fetching upstream changes from https://git-wip-us.apache.org/
> repos/asf/sentry.git
> > > git --version # timeout=10
> > > git fetch --tags --progress https://git-wip-us.apache.org/
> repos/asf/sentry.git +refs/heads/*:refs/remotes/origin/*
> > > git config remote.origin.url https://git-wip-us.apache.org/
> repos/asf/sentry.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/sentry.git # timeout=10
> > Fetching upstream changes from https://git-wip-us.apache.org/
> repos/asf/sentry.git
> > > git fetch --tags --progress https://git-wip-us.apache.org/
> repos/asf/sentry.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 3dab053e18b4197e97f4a654e2707cb1eb673047
> (refs/remotes/origin/master)
> > > git config core.sparsecheckout # timeout=10
> > > git checkout -f 3dab053e18b4197e97f4a654e2707cb1eb673047
> > Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to H17
> > at hudson.remoting.Channel.attachCallSiteStackTrace(
> Channel.java:1741)
> > at hudson.remoting.UserRequest$ExceptionResponse.retrieve(
> UserRequest.java:357)
> > at hudson.remoting.Channel.call(Channel.java:955)
> > at hudson.remoting.RemoteInvocationHandler.invoke(
> RemoteInvocationHandler.java:283)
> > at com.sun.proxy.$Proxy117.withRepository(Unknown Source)
> > at org.jenkinsci.plugins.gitclient.RemoteGitImpl.
> withRepository(RemoteGitImpl.java:235)
> > at hudson.plugins.git.GitSCM.printCommitMessageToLog(
> GitSCM.java:1271)
> > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)
> > at hudson.scm.SCM.checkout(SCM.java:504)
> > at hudson.model.AbstractProject.
> checkout(AbstractProject.java:1208)
> > at hudson.model.AbstractBuild$AbstractBuildExecution.
> defaultCheckout(AbstractBuild.java:574)
> > at jenkins.scm.SCMCheckoutStrategy.checkout(
> SCMCheckoutStrategy.java:86)
> > at hudson.model.AbstractBuild$AbstractBuildExecution.run(
> AbstractBuild.java:499)
> > at hudson.model.Run.execute(Run.java:1794)
> > at hudson.maven.MavenModuleSetBuild.run(
> MavenModuleSetBuild.java:543)
> > at hudson.model.ResourceController.execute(
> ResourceController.java:97)
> > at hudson.model.Executor.run(Executor.java:429)
> > java.lang.NoClassDefFoundError: hudson.model.Computer
> > at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.
> withRepository(AbstractGitAPIImpl.java:29)
> > at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.
> withRepository(CliGitAPIImpl.java:72)
> > at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:43)
> > at java.lang.reflect.Method.invoke(Method.java:498)
> > at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(
> RemoteInvocationHandler.java:929)
> > at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(
> RemoteInvocationHandler.java:903)
> > at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(
> RemoteInvocationHandler.java:855)
> > at hudson.remoting.UserRequest.perform(UserRequest.java:212)
> > at hudson.remoting.UserRequest.perform(UserRequest.java:54)
> > at hudson.remoting.Request$2.run(Request.java:369)
> > at hudson.remoting.InterceptingExecutorService$1.call(
> InterceptingExecutorService.java:72)
> > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> > at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> > at java.lang.Thread.run(Thread.java:748)
> > Caused: java.io.IOException: Remote call on H17 failed
> > at hudson.remoting.Channel.call(Channel.java:961)
> > at hudson.remoting.RemoteInvocationHandler.invoke(
> RemoteInvocationHandler.java:283)
> > at com.sun.proxy.$Proxy117.withRepository(Unknown Source)
> > at org.jenkinsci.plugins.gitclient.RemoteGitImpl.
> withRepository(RemoteGitImpl.java:235)
> > at hudson.plugins.git.GitSCM.printCommitMessageToLog(
> GitSCM.java:1271)
> > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)
> > at hudson.scm.SCM.checkout(SCM.java:504)
> > at hudson.model.AbstractProject.checkout(AbstractProject.java:
> 1208)
> > at hudson.model.AbstractBuild$AbstractBuildExecution.
> defaultCheckout(AbstractBuild.java:574)
> > at jenkins.scm.SCMCheckoutStrategy.checkout(
> SCMCheckoutStrategy.java:86)
> > at hudson.model.AbstractBuild$AbstractBuildExecution.run(
> AbstractBuild.java:499)
> > at hudson.model.Run.execute(Run.java:1794)
> > at hudson.maven.MavenModuleSetBuild.run(
> MavenModuleSetBuild.java:543)
> > at hudson.model.ResourceController.execute(
> ResourceController.java:97)
> > at hudson.model.Executor.run(Executor.java:429)
> >
> >
> > Thanks,
> >
> > Lina
> >
> > On Thu, Jul 26, 2018 at 4:05 AM, Colm O hEigeartaigh <
> coheigea@apache.org>
> > wrote:
> >
> >> Hi Lina,
> >>
> >> I made the change for both the JDK8 build and the staging build, so
> let's
> >> see if that makes a difference.
> >>
> >> Colm.
> >>
> >> On Thu, Jul 26, 2018 at 7:11 AM, Na Li <li...@cloudera.com.invalid>
> >> wrote:
> >>
> >> > Kalyan,
> >> >
> >> > to solve the sentry upstream build issue, do you have access to
> "Please
> >> > enable 'Delete workspace before build starts' in your build
> >> configuration."
> >> > as mentioned in INFRA-16822?
> >> >
> >> > Thanks,
> >> >
> >> > Lina
> >> >
> >> > On Wed, Jul 25, 2018 at 11:48 PM, Na Li <li...@cloudera.com> wrote:
> >> >
> >> > > Kalyan,
> >> > >
> >> > > The build still fails. I found this link https://stackoverflow.
> >> > > com/questions/21277806/fatal-early-eof-fatal-index-pack-failed. It
> is
> >> > > possible that git ran out of memory. I have filed
> >> https://issues.apache
> >> > .
> >> > > org/jira/browse/INFRA-16822
> >> > >
> >> > > Do you know if there are other things we can do to bring the build
> >> back
> >> > to
> >> > > green? like change git command on how to get remote repo?
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Lina
> >> > >
> >> > >
> >> > >
> >> > > On Wed, Jul 25, 2018 at 11:26 PM, Apache Jenkins Server <
> >> > > jenkins@builds.apache.org> wrote:
> >> > >
> >> > >> The Apache Jenkins build system has built Sentry-jdk-1.8 (build
> #110)
> >> > >>
> >> > >> Status: Still Failing
> >> > >>
> >> > >> Check console output at https://builds.apache.org/job/
> >> > Sentry-jdk-1.8/110/
> >> > >> to view the results.
> >> > >
> >> > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Colm O hEigeartaigh
> >>
> >> Talend Community Coder
> >> http://coders.talend.com
> >>
> >
> >
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
Re: Sentry-jdk-1.8 - Build # 110 - Still Failing
Posted by Colm O hEigeartaigh <co...@apache.org>.
I recommend filing a JIRA with INFRA - or update the previous JIRA if it's
still open.
Colm.
On Thu, Jul 26, 2018 at 4:32 PM, Na Li <li...@cloudera.com> wrote:
> Colm,
>
> Thanks for your update! Your change helped, but we still have build issue.
> We need to figure out next step to fix the build issue with "java.lang.NoClassDefFoundError:
> hudson.model.Computer".
>
> 1) Before your change, the exception callstack is at
> https://builds.apache.org/job/Sentry-jdk-1.8/126/console
>
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on H17 <https://builds.apache.org/computer/H17> (Hadoop xenial) in workspace /home/jenkins/jenkins-slave/workspace/Sentry-jdk-1.8
> > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
> > git config remote.origin.url https://git-wip-us.apache.org/repos/asf/sentry.git # timeout=10
> Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/sentry.git
> > git --version # timeout=10
> > git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/sentry.git +refs/heads/*:refs/remotes/origin/*
> ERROR: Error fetching remote repo 'origin'
> hudson.plugins.git.GitException: Failed to fetch from https://git-wip-us.apache.org/repos/asf/sentry.git
> at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888)
> at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
> at hudson.scm.SCM.checkout(SCM.java:504)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
> at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
> at hudson.model.Run.execute(Run.java:1794)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
> at hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:429)
> Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/sentry.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
> stdout:
>
>
>
> 2) After your change at build 129, the callstack is at
> https://builds.apache.org/job/Sentry-jdk-1.8/130/console.
>
> Cloning the remote Git repository
> Cloning repository https://git-wip-us.apache.org/repos/asf/sentry.git
> > git init /home/jenkins/jenkins-slave/workspace/Sentry-jdk-1.8 # timeout=10
> Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/sentry.git
> > git --version # timeout=10
> > git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/sentry.git +refs/heads/*:refs/remotes/origin/*
> > git config remote.origin.url https://git-wip-us.apache.org/repos/asf/sentry.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/sentry.git # timeout=10
> Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/sentry.git
> > git fetch --tags --progress https://git-wip-us.apache.org/repos/asf/sentry.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 3dab053e18b4197e97f4a654e2707cb1eb673047 (refs/remotes/origin/master)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f 3dab053e18b4197e97f4a654e2707cb1eb673047
> Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to H17
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
> at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
> at hudson.remoting.Channel.call(Channel.java:955)
> at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
> at com.sun.proxy.$Proxy117.withRepository(Unknown Source)
> at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)
> at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)
> at hudson.scm.SCM.checkout(SCM.java:504)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
> at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
> at hudson.model.Run.execute(Run.java:1794)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
> at hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:429)
> java.lang.NoClassDefFoundError: hudson.model.Computer
> at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29)
> at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72)
> at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929)
> at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903)
> at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855)
> at hudson.remoting.UserRequest.perform(UserRequest.java:212)
> at hudson.remoting.UserRequest.perform(UserRequest.java:54)
> at hudson.remoting.Request$2.run(Request.java:369)
> at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Caused: java.io.IOException: Remote call on H17 failed
> at hudson.remoting.Channel.call(Channel.java:961)
> at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
> at com.sun.proxy.$Proxy117.withRepository(Unknown Source)
> at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)
> at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271)
> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)
> at hudson.scm.SCM.checkout(SCM.java:504)
> at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
> at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
> at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
> at hudson.model.Run.execute(Run.java:1794)
> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
> at hudson.model.ResourceController.execute(ResourceController.java:97)
> at hudson.model.Executor.run(Executor.java:429)
>
>
> Thanks,
>
> Lina
>
> On Thu, Jul 26, 2018 at 4:05 AM, Colm O hEigeartaigh <co...@apache.org>
> wrote:
>
>> Hi Lina,
>>
>> I made the change for both the JDK8 build and the staging build, so let's
>> see if that makes a difference.
>>
>> Colm.
>>
>> On Thu, Jul 26, 2018 at 7:11 AM, Na Li <li...@cloudera.com.invalid>
>> wrote:
>>
>> > Kalyan,
>> >
>> > to solve the sentry upstream build issue, do you have access to "Please
>> > enable 'Delete workspace before build starts' in your build
>> configuration."
>> > as mentioned in INFRA-16822?
>> >
>> > Thanks,
>> >
>> > Lina
>> >
>> > On Wed, Jul 25, 2018 at 11:48 PM, Na Li <li...@cloudera.com> wrote:
>> >
>> > > Kalyan,
>> > >
>> > > The build still fails. I found this link https://stackoverflow.
>> > > com/questions/21277806/fatal-early-eof-fatal-index-pack-failed. It is
>> > > possible that git ran out of memory. I have filed
>> https://issues.apache
>> > .
>> > > org/jira/browse/INFRA-16822
>> > >
>> > > Do you know if there are other things we can do to bring the build
>> back
>> > to
>> > > green? like change git command on how to get remote repo?
>> > >
>> > > Thanks,
>> > >
>> > > Lina
>> > >
>> > >
>> > >
>> > > On Wed, Jul 25, 2018 at 11:26 PM, Apache Jenkins Server <
>> > > jenkins@builds.apache.org> wrote:
>> > >
>> > >> The Apache Jenkins build system has built Sentry-jdk-1.8 (build #110)
>> > >>
>> > >> Status: Still Failing
>> > >>
>> > >> Check console output at https://builds.apache.org/job/
>> > Sentry-jdk-1.8/110/
>> > >> to view the results.
>> > >
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Sentry-jdk-1.8 - Build # 110 - Still Failing
Posted by Na Li <li...@cloudera.com.INVALID>.
Colm,
Thanks for your update! Your change helped, but we still have build issue.
We need to figure out next step to fix the build issue with
"java.lang.NoClassDefFoundError:
hudson.model.Computer".
1) Before your change, the exception callstack is at
https://builds.apache.org/job/Sentry-jdk-1.8/126/console
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on H17 <https://builds.apache.org/computer/H17>
(Hadoop xenial) in workspace
/home/jenkins/jenkins-slave/workspace/Sentry-jdk-1.8
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url
https://git-wip-us.apache.org/repos/asf/sentry.git # timeout=10
Fetching upstream changes from
https://git-wip-us.apache.org/repos/asf/sentry.git
> git --version # timeout=10
> git fetch --tags --progress
https://git-wip-us.apache.org/repos/asf/sentry.git
+refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from
https://git-wip-us.apache.org/repos/asf/sentry.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:888)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1155)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
at hudson.scm.SCM.checkout(SCM.java:504)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1794)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags
--progress https://git-wip-us.apache.org/repos/asf/sentry.git
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout:
2) After your change at build 129, the callstack is at
https://builds.apache.org/job/Sentry-jdk-1.8/130/console.
Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/sentry.git
> git init /home/jenkins/jenkins-slave/workspace/Sentry-jdk-1.8 # timeout=10
Fetching upstream changes from
https://git-wip-us.apache.org/repos/asf/sentry.git
> git --version # timeout=10
> git fetch --tags --progress
https://git-wip-us.apache.org/repos/asf/sentry.git
+refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url
https://git-wip-us.apache.org/repos/asf/sentry.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/sentry.git # timeout=10
Fetching upstream changes from
https://git-wip-us.apache.org/repos/asf/sentry.git
> git fetch --tags --progress
https://git-wip-us.apache.org/repos/asf/sentry.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 3dab053e18b4197e97f4a654e2707cb1eb673047
(refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 3dab053e18b4197e97f4a654e2707cb1eb673047
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to H17
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
at hudson.remoting.Channel.call(Channel.java:955)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
at com.sun.proxy.$Proxy117.withRepository(Unknown Source)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)
at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)
at hudson.scm.SCM.checkout(SCM.java:504)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1794)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
java.lang.NoClassDefFoundError: hudson.model.Computer
at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72)
at sun.reflect.GeneratedMethodAccessor149.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903)
at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused: java.io.IOException: Remote call on H17 failed
at hudson.remoting.Channel.call(Channel.java:961)
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
at com.sun.proxy.$Proxy117.withRepository(Unknown Source)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)
at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)
at hudson.scm.SCM.checkout(SCM.java:504)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1794)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Thanks,
Lina
On Thu, Jul 26, 2018 at 4:05 AM, Colm O hEigeartaigh <co...@apache.org>
wrote:
> Hi Lina,
>
> I made the change for both the JDK8 build and the staging build, so let's
> see if that makes a difference.
>
> Colm.
>
> On Thu, Jul 26, 2018 at 7:11 AM, Na Li <li...@cloudera.com.invalid>
> wrote:
>
> > Kalyan,
> >
> > to solve the sentry upstream build issue, do you have access to "Please
> > enable 'Delete workspace before build starts' in your build
> configuration."
> > as mentioned in INFRA-16822?
> >
> > Thanks,
> >
> > Lina
> >
> > On Wed, Jul 25, 2018 at 11:48 PM, Na Li <li...@cloudera.com> wrote:
> >
> > > Kalyan,
> > >
> > > The build still fails. I found this link https://stackoverflow.
> > > com/questions/21277806/fatal-early-eof-fatal-index-pack-failed. It is
> > > possible that git ran out of memory. I have filed
> https://issues.apache
> > .
> > > org/jira/browse/INFRA-16822
> > >
> > > Do you know if there are other things we can do to bring the build back
> > to
> > > green? like change git command on how to get remote repo?
> > >
> > > Thanks,
> > >
> > > Lina
> > >
> > >
> > >
> > > On Wed, Jul 25, 2018 at 11:26 PM, Apache Jenkins Server <
> > > jenkins@builds.apache.org> wrote:
> > >
> > >> The Apache Jenkins build system has built Sentry-jdk-1.8 (build #110)
> > >>
> > >> Status: Still Failing
> > >>
> > >> Check console output at https://builds.apache.org/job/
> > Sentry-jdk-1.8/110/
> > >> to view the results.
> > >
> > >
> > >
> >
>
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
Re: Sentry-jdk-1.8 - Build # 110 - Still Failing
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi Lina,
I made the change for both the JDK8 build and the staging build, so let's
see if that makes a difference.
Colm.
On Thu, Jul 26, 2018 at 7:11 AM, Na Li <li...@cloudera.com.invalid> wrote:
> Kalyan,
>
> to solve the sentry upstream build issue, do you have access to "Please
> enable 'Delete workspace before build starts' in your build configuration."
> as mentioned in INFRA-16822?
>
> Thanks,
>
> Lina
>
> On Wed, Jul 25, 2018 at 11:48 PM, Na Li <li...@cloudera.com> wrote:
>
> > Kalyan,
> >
> > The build still fails. I found this link https://stackoverflow.
> > com/questions/21277806/fatal-early-eof-fatal-index-pack-failed. It is
> > possible that git ran out of memory. I have filed https://issues.apache
> .
> > org/jira/browse/INFRA-16822
> >
> > Do you know if there are other things we can do to bring the build back
> to
> > green? like change git command on how to get remote repo?
> >
> > Thanks,
> >
> > Lina
> >
> >
> >
> > On Wed, Jul 25, 2018 at 11:26 PM, Apache Jenkins Server <
> > jenkins@builds.apache.org> wrote:
> >
> >> The Apache Jenkins build system has built Sentry-jdk-1.8 (build #110)
> >>
> >> Status: Still Failing
> >>
> >> Check console output at https://builds.apache.org/job/
> Sentry-jdk-1.8/110/
> >> to view the results.
> >
> >
> >
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Sentry-jdk-1.8 - Build # 110 - Still Failing
Posted by Na Li <li...@cloudera.com.INVALID>.
Kalyan,
to solve the sentry upstream build issue, do you have access to "Please
enable 'Delete workspace before build starts' in your build configuration."
as mentioned in INFRA-16822?
Thanks,
Lina
On Wed, Jul 25, 2018 at 11:48 PM, Na Li <li...@cloudera.com> wrote:
> Kalyan,
>
> The build still fails. I found this link https://stackoverflow.
> com/questions/21277806/fatal-early-eof-fatal-index-pack-failed. It is
> possible that git ran out of memory. I have filed https://issues.apache.
> org/jira/browse/INFRA-16822
>
> Do you know if there are other things we can do to bring the build back to
> green? like change git command on how to get remote repo?
>
> Thanks,
>
> Lina
>
>
>
> On Wed, Jul 25, 2018 at 11:26 PM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
>> The Apache Jenkins build system has built Sentry-jdk-1.8 (build #110)
>>
>> Status: Still Failing
>>
>> Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/110/
>> to view the results.
>
>
>
Re: Sentry-jdk-1.8 - Build # 110 - Still Failing
Posted by Na Li <li...@cloudera.com.INVALID>.
Kalyan,
The build still fails. I found this link
https://stackoverflow.com/questions/21277806/fatal-early-eof-fatal-index-pack-failed.
It is possible that git ran out of memory. I have filed
https://issues.apache.org/jira/browse/INFRA-16822
Do you know if there are other things we can do to bring the build back to
green? like change git command on how to get remote repo?
Thanks,
Lina
On Wed, Jul 25, 2018 at 11:26 PM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> The Apache Jenkins build system has built Sentry-jdk-1.8 (build #110)
>
> Status: Still Failing
>
> Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/110/
> to view the results.
Sentry-jdk-1.8 - Build # 110 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #110)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/110/ to view the results.
Sentry-jdk-1.8 - Build # 109 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #109)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/109/ to view the results.
Sentry-jdk-1.8 - Build # 108 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #108)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/108/ to view the results.
Sentry-jdk-1.8 - Build # 107 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #107)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/107/ to view the results.
Sentry-jdk-1.8 - Build # 106 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #106)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/106/ to view the results.
Sentry-jdk-1.8 - Build # 105 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #105)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/105/ to view the results.
Sentry-jdk-1.8 - Build # 104 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #104)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/104/ to view the results.
Sentry-jdk-1.8 - Build # 103 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #103)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/103/ to view the results.
Sentry-jdk-1.8 - Build # 102 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #102)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/102/ to view the results.
Sentry-jdk-1.8 - Build # 101 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #101)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/101/ to view the results.
Sentry-jdk-1.8 - Build # 100 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #100)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/100/ to view the results.
Sentry-jdk-1.8 - Build # 99 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #99)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/99/ to view the results.
Sentry-jdk-1.8 - Build # 98 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #98)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/98/ to view the results.
Sentry-jdk-1.8 - Build # 97 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #97)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/97/ to view the results.
Sentry-jdk-1.8 - Build # 96 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #96)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/96/ to view the results.
Sentry-jdk-1.8 - Build # 95 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #95)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/95/ to view the results.
Sentry-jdk-1.8 - Build # 94 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #94)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/94/ to view the results.
Sentry-jdk-1.8 - Build # 93 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #93)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/93/ to view the results.
Sentry-jdk-1.8 - Build # 92 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #92)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/92/ to view the results.
Sentry-jdk-1.8 - Build # 91 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #91)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/91/ to view the results.
Sentry-jdk-1.8 - Build # 90 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #90)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/90/ to view the results.
Sentry-jdk-1.8 - Build # 89 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #89)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/89/ to view the results.
Sentry-jdk-1.8 - Build # 88 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #88)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/88/ to view the results.
Sentry-jdk-1.8 - Build # 87 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #87)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/87/ to view the results.
Sentry-jdk-1.8 - Build # 86 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #86)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/86/ to view the results.
Sentry-jdk-1.8 - Build # 85 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #85)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/85/ to view the results.
Sentry-jdk-1.8 - Build # 84 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #84)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/84/ to view the results.
Sentry-jdk-1.8 - Build # 83 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #83)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/83/ to view the results.
Sentry-jdk-1.8 - Build # 82 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #82)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/82/ to view the results.
Sentry-jdk-1.8 - Build # 81 - Still Failing
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Sentry-jdk-1.8 (build #81)
Status: Still Failing
Check console output at https://builds.apache.org/job/Sentry-jdk-1.8/81/ to view the results.