ü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
rday, 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: Co
nvoke(Method.java:606)
-Original Message-
From: Jim King
Sent: Thursday, April 14, 2016 10:14 AM
To: 'dev@thrift.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 t
udson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
>>>> >> >> at
>>>> >> >>
>>>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
>>>> >> >&g
9)
>>> >> >> at hudson.model.Run.execute(Run.java:1738)
>>> >> >> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>>> >> >> at
>>> >> >> hudson.model.ResourceController.execute(ResourceController.java:9
t; at
>>>>> >> >>
>>>>> hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:951)
>>>>> >> >> at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1054)
>>>>> >> >> at huds
gt;> at
>>>> >> >>
>>>> >>
>>>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
>>>> >> >> at
>>>> >> >>
>>>> jenkins.scm.SCMCheckoutStrategy.checkout(SCM
gt; 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
>>>
t;
>> >> >> 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.
>> >> &
rge
>>>> >>
>>>> >> 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.
is odd that the git portion of these builds went sideways since the
> >> > Jenkins Job Config History auditing plugin shows the last change
> >> (before my
> >> > tweak last night) was 2016-02-16_02-09-39. I expect jenkins or its
> >> plugins
> >> &
eginning
>>> >> of each build.
>>> >>
>>> >
>>> > Ack - looking now.
>>> >
>>> > It is odd that the git portion of these builds went sideways since the
>>> > Jenkins Job Config History auditing plugin shows the last c
er.
>> >
>>
>> OK - that analysis was wrong, clearly there has been a change in the build
>> itself that modifies source code and this causes the issue.
>> I've enabled
>> with
>> the following description:
>>
>> Clean up the worksp
space before every checkout by deleting all untracked
> files and directories, including those which are specified in .gitignore.
> It also resets all *tracked* files to their versioned state. This ensures
> that the workspace is in the same state as if you cloned and checked out in
> a bra
--hard HEAD` to me, which
should do it. That should insulate CI from bad tests that modify checked in
repo state, but those tests shouldn't exist either.
COMMITTERS:
I'd like to reiterate to any committers out there that red CI must be a
hard bright line that is not crossed when accepting pa
16_02-09-39. I expect jenkins or its plugins
were updated by infra causing the previously working job config to not work
any longer.
> - Jim
>
> -Original Message-
> From: Jim King
> Sent: Wednesday, April 13, 2016 10:34 PM
> To: dev@thrift.apache.org; 'jsir...@apache.org'
im
-Original Message-
From: Jim King
Sent: Wednesday, April 13, 2016 10:34 PM
To: dev@thrift.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 th
> -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 wrote:
>
> >
> >
> > On Wed, Apr 13, 2
esday, 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 wrote:
>
>
> On Wed, Apr 13, 2016 at 7:51 PM, Jim King wrote:
>
>> I’m still looking for answers on pull request build failures.
>>
>> I
On Wed, Apr 13, 2016 at 7:57 PM, John Sirois wrote:
>
>
> On Wed, Apr 13, 2016 at 7:54 PM, John Sirois wrote:
>
>>
>>
>> On Wed, Apr 13, 2016 at 7:51 PM, Jim King
>> wrote:
>>
>>> I’m still looking for answers on pull request build failures.
>>>
>>> I have 2 or 3 PRs open right now and they’ve
On Wed, Apr 13, 2016 at 7:54 PM, John Sirois wrote:
>
>
> On Wed, Apr 13, 2016 at 7:51 PM, Jim King 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
On Wed, Apr 13, 2016 at 7:51 PM, Jim King 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 i
22 matches
Mail list logo
