Speaking about failing, I run into boost troubles again on my Suse machine
with "make test" at cpp. It's the "lib-some-arbitrary-name.a not found"
again. We really should do sth. about this.
$0,02
JensG
-----Ursprüngliche Nachricht-----
From: Jim King
Sent: Saturday, April 16, 2016 3:40 PM
To: dev@thrift.apache.org ; jsir...@apache.org
Subject: RE: Build Failures
Now it's failing a different way:
https://builds.apache.org/job/Thrift-precommit/425/
Merging refs/tags/changes/425
git rev-parse refs/tags/changes/425^{commit} # timeout=10
FATAL: Command "git rev-parse refs/tags/changes/425^{commit}" returned
status code 128:
stdout: refs/tags/changes/425^{commit}
stderr: fatal: ambiguous argument 'refs/tags/changes/425^{commit}': unknown
revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
hudson.plugins.git.GitException: Command "git rev-parse
refs/tags/changes/425^{commit}" returned status code 128:
stdout: refs/tags/changes/425^{commit}
stderr: fatal: ambiguous argument 'refs/tags/changes/425^{commit}': unknown
revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1693)
at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1669)
at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1665)
at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1307)
at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1319)
at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:677)
at hudson.plugins.git.GitAPI.revParse(GitAPI.java:316)
at sun.reflect.GeneratedMethodAccessor1936.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
-----Original Message-----
From: Jim King
Sent: Thursday, April 14, 2016 10:14 AM
To: 'dev@thrift.apache.org' <dev@thrift.apache.org>; 'jsir...@apache.org'
<jsir...@apache.org>
Subject: RE: Build Failures
I got one build through (which failed in "d" tests) and now it's stuck in
the same state, see:
https://builds.apache.org/job/Thrift-precommit/411/
FATAL: Could not checkout master with start point origin/master
hudson.plugins.git.GitException: Could not checkout master with start point
origin/master
at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$9.execute(CliGitAPIImpl.java:1962)
at
org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.checkoutBranch(AbstractGitAPIImpl.java:82)
at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkoutBranch(CliGitAPIImpl.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:608)
at
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583)
at
hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542)
at hudson.remoting.UserRequest.perform(UserRequest.java:120)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ......remote call to H10(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
at hudson.remoting.Channel.call(Channel.java:781)
at
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250)
at com.sun.proxy.$Proxy115.checkoutBranch(Unknown Source)
at
org.jenkinsci.plugins.gitclient.RemoteGitImpl.checkoutBranch(RemoteGitImpl.java:327)
at
com.cloudbees.jenkins.plugins.git.vmerge.BuildChooserImpl.getCandidateRevisions(BuildChooserImpl.java:78)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:951)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1054)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git checkout -b master
origin/master" returned status code 1:
stdout: lib/lua/TCompactProtocol.lua: needs merge
stderr: error: you need to resolve your current index first
It looks like the build environment is not forced clean at the beginning of
each build.
- Jim
-----Original Message-----
From: Jim King
Sent: Wednesday, April 13, 2016 10:34 PM
To: dev@thrift.apache.org; 'jsir...@apache.org' <jsir...@apache.org>
Subject: RE: Build Failures
The builds were failing claiming that a file was in the middle of being
merged and they were all failing early.
I think the build environment itself is compromised and there's nothing I
can do about that.
-----Original Message-----
From: John Sirois [mailto:jsir...@apache.org]
Sent: Wednesday, April 13, 2016 9:58 PM
To: dev@thrift.apache.org
Subject: Re: Build Failures
On Wed, Apr 13, 2016 at 7:54 PM, John Sirois <jsir...@apache.org> wrote:
On Wed, Apr 13, 2016 at 7:51 PM, Jim King <jim.k...@simplivity.com> wrote:
I’m still looking for answers on pull request build failures.
I have 2 or 3 PRs open right now and they’ve failed in the apache
precommit builds for strange reasons.
The apache internal builds seem to be failing.
I think the answer is the breaks need a fixer; hopefully you can find
time to help fix.
I say this because I started down a series of patches to the java
codegen/lib a while back and found a similar state - though on the
pull request builder (apache jenkins). I stopped my java stuff and
fixed that CI with the help of Aki and Jake reviewing and providing
guidance. I am not a thrift comitter.
I will say that its discouraging that that CI is now solid red too:
https://builds.apache.org/job/Thrift-precommit/
Part of the answer IMO is for committers to hold a hard line on accepting
any patch, or pushing their own, w/o full green CIs.
[image: Description: Description: simplivity-lg-xsmall]
James E. King, III
Architect
8 Technology Drive, 2nd Floor
Westborough, MA 01581-1756
Ph: 855-SVT-INFO
------------------------------
PRIVACY STATEMENT:
This message is a PRIVATE communication. This message and all
attachments are a private communication sent by SimpliVity and are
considered to be confidential or protected by privilege. If you are
not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or use of the information contained
in or attached to this message is strictly prohibited. Please notify
the sender of the delivery error by replying to this message, and then
delete it from your system.
For more information please visit http://www.simplivity.com
------------------------------
---------------------------------------------------------------------------------------
PRIVACY STATEMENT:
This message is a PRIVATE communication. This message and all attachments
are a private communication sent by SimpliVity and are considered to be
confidential or protected by privilege. If you are not the intended
recipient, you are hereby notified that any disclosure, copying,
distribution or use of the information contained in or attached to this
message is strictly prohibited. Please notify the sender of the delivery
error by replying to this message, and then delete it from your system.
---------------------------------------------------------------------------------------
