age test has caused some CI build failures
> --
>
> Key: THRIFT-4155
> URL: https://issues.apache.org/jira/browse/THRIFT-4155
> Project: Thrift
> Issue Type: Bug
>
Github user asfgit closed the pull request at:
https://github.com/apache/thrift/pull/1429
---
GitHub user jeking3 opened a pull request:
https://github.com/apache/thrift/pull/1429
THRIFT-2913: fix random CI build failures in lib/rb test
'Thrift::ThreadPoolServer should serve inside a thread'
Client: rb
This closes #1429
You can merge this pull requ
The root cause is someone added "import context" code to golang/mock which
broke it against older go releases (older than 1.7).
I have a fix for it bundled into THRIFT-4351 where I call "go get" twice
with a sed in between to force it to import golang.org/x/net/context
instead.
https://github.com
James E. King, III created THRIFT-4155:
--
Summary: Unstable D language test has caused some CI build failures
Key: THRIFT-4155
URL: https://issues.apache.org/jira/browse/THRIFT-4155
Project
Many build jobs have been failing with this signature:
Building hspec-core-2.4.0...
Preprocessing library hspec-core-2.4.0...
[ 1 of 22] Compiling Paths_hspec_core ( dist/build/autogen/Paths_hspec_core.hs,
dist/build/Paths_hspec_core.o )
[ 2 of 22] Compiling Test.Hspec.Core.Timer ( src/Test/H
Hi Jim
I made a fix and tested locally:
https://github.com/bufferoverflow/thrift/commit/59794bf86a5e3c6f0b21ddce07df4058eaed8978
and create a MR if this is passing:
https://travis-ci.org/bufferoverflow/thrift/builds/192504121
cheers
roger
Quoting Jim King :
Progress is being hindered by ina
Progress is being hindered by inability to complete CI builds.
We need to fix this as the top priority. Nothing gets merged if CI builds fail.
Folks who are involved with the docker image support, please take a look at the
recent Travis CI failures.
Thanks.
[Description: Description: simplivity
ü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
https://issues.apache.org/jira/browse/THRIFT-3793
Even though it didn't pass all three CI builds (Apache Jenkins still broken,
Travis CI is still building), it passed the AppVeyor build which is the only
build it affected, so please consider merging this to fix all AppVeyor CI
builds.
[Descrip
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.
&
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
>>
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'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.
[Description: Description: simplivity-lg-xsmall]
James E. King, III
A
+1
Von: Aki Sukegawa
Gesendet: 09.04.2016 04:55
An: dev@thrift.apache.org
Betreff: Re: Travis CI - Build Failures
The failure you're experiencing is THRIFT-3768 that we merged 2 days ago.
It makes every JSON-buffered Go server cases flaky.
I'll revert it
The failure you're experiencing is THRIFT-3768 that we merged 2 days ago.
It makes every JSON-buffered Go server cases flaky.
I'll revert it soon.
As to "7days", it seemed to be caused by NPM dependency.
It somehow went away.
Other than Travis, make check is hanging for almost every build of Jenk
The list of open pull requests have all failed over the last few days.
The last successful build was 7 days ago. Things look unreliable.
This needs to be fixed up. What's the current status of this?
Is anybody working on stabilizing the Travis CI build??
[Description: Description: simplivity-lg-
The list of open pull requests have all failed over the last few days.
The last successful build was 5 days ago. Things look horribly unreliable.
This needs to be fixed up. What's the current status of this?
[Description: Description: simplivity-lg-xsmall]
James E. King, III
Architect
8 Technolo
Our jenkins sends failure mails on pull request build failures.
IMO the notification mail is for emergency such as master branch build
failures.
Another problem is that it does not trigger any build on commits, so
currently we don't have true integration tests.
Instead it is reporting "
(See
[https://builds.apache.org/job/Thrift-precommit/244/])
follow-up: THRIFT-3690 Work around docker image build failures on (nsuke:
[https://github.com/apache/thrift/commit/50bb860acd3ea200be5261335c5ccb1300bacfae])
* .travis.yml
> Work around docker image build failures on Tr
(See
[https://builds.apache.org/job/Thrift-precommit/237/])
THRIFT-3690 Work around docker image build failures on Travis-CI Client:
(nsuke:
[https://github.com/apache/thrift/commit/2c5ed27a25087f541312d35938056890c4784fc6])
* .travis.yml
* build/docker/scripts/autotools.sh
* build/docker/scripts/cmak
(See
[https://builds.apache.org/job/Thrift-precommit/217/])
THRIFT-3690 Work around docker image build failures on Travis-CI (nsuke:
[https://github.com/apache/thrift/commit/ace015470ad84b61982fedec8c59fd0de7602678])
* build/docker/scripts/autotools.sh
* build/docker/scripts/cmake.sh
* .travis.yml
* b
pull request at:
https://github.com/apache/thrift/pull/906
> Work around docker image build failures on Travis-CI
>
>
> Key: THRIFT-3690
> URL: https://issues.apache.org/jira/browse/THRIFT-3690
&g
(See
[https://builds.apache.org/job/Thrift-precommit/216/])
THRIFT-3690 Work around docker image build failures on Travis-CI (nsuke:
[https://github.com/apache/thrift/commit/ace015470ad84b61982fedec8c59fd0de7602678])
* .travis.yml
* build/docker/scripts/cmake.sh
* build/docker/scripts/autotools.sh
* b
uest:
https://github.com/apache/thrift/pull/906
THRIFT-3690 Work around docker image build failures on Travis-CI
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nsuke/thrift THRIFT-3690
Alternatively you can review and apply t
Aki Sukegawa created THRIFT-3690:
Summary: Work around docker image build failures on Travis-CI
Key: THRIFT-3690
URL: https://issues.apache.org/jira/browse/THRIFT-3690
Project: Thrift
Issue
[
https://issues.apache.org/jira/browse/THRIFT-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
danem closed THRIFT-3216.
-
Resolution: Fixed
Found out that I was missing flag to specify c++11
> Build Failures on OSX 10.1
app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/algorithm:862:1:
note:
'find' declared here
find(_InputIterator __first, _InputIterator __last, const _Tp& __value_)
^
1 error generated.
{quote}
> Build Failures on OSX 10.1
danem created THRIFT-3216:
-
Summary: Build Failures on OSX 10.10.3
Key: THRIFT-3216
URL: https://issues.apache.org/jira/browse/THRIFT-3216
Project: Thrift
Issue Type: Bug
Components: C
https://builds.apache.org/job/Thrift/1220/console
...
+ sloccount --duplicates --wide --details lib tutorial test
/tmp/hudson2264386917025520259.sh: line 3: sloccount: command not found
Build step 'Execute shell' marked build as failure
...
It appears `sloccount` is either missing from the sy
48 matches
Mail list logo
