Build failed in Jenkins: Geode-nightly #983

2017-10-13 Thread Apache Jenkins Server 
See 


Changes:

[kmiller] GEODE-3445 Document new gfsh connect option

[kmiller] GEODE-3445 Revise doc to specify 1-way authentication

[github] GEODE-3539: refactor CreateIndexCommand and add more tests (#915)

[bschuchardt] GEODE-3820 CI failure:

[sbawaskar] bumping the version to 1.4.0-SNAPSHOT

[kohlmu-pivotal] GEODE-3797: Removal of CorrelationId and MessageHeader from 
protobuf

[kirk.lund] GEODE-3825: upgrade to JUnitParams 1.1.0

[kirk.lund] GEODE-3792: add new test PartitionedRegionCloseDUnitTest

--
[...truncated 1.72 MB...]
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
at 
io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:233)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
at 
io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:435)
at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)
at 
io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:250)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
at 
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
at 
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926)
at 
io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:961)
at 
io.netty.channel.epoll.EpollDomainSocketChannel$EpollDomainUnsafe.epollInReady(EpollDomainSocketChannel.java:140)
at 
io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:386)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:302)
at 
io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:877)
at 
io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
at java.lang.Thread.run(Thread.java:748)
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such 
image: apachegeode/geode-build:latest"}
Error during callback
com.github.dockerjava.api.exception.NotFoundException: {"message":"No such 
image: apachegeode/geode-build:latest"}

at 
com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:103)
at 
com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:33)
at 
io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
at 
io.netty.handler.logging.LoggingHandler.channelRead(LoggingHandler.java:233)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372)
at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:358)
at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:350)
at 
io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:435)
at 
io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293)
at 
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267)

version for JIRA tickets?

2017-10-13 Thread Bruce Schuchardt 
I see that the build version has been bumped to 1.4.0 on develop but I 
don't see a 1.4.0 on JIRA & have a ticket to close today.

Re: version for JIRA tickets?

2017-10-13 Thread Anthony Baker 
Fixed!

https://issues.apache.org/jira/projects/GEODE/versions/12341842 


Anthony

> On Oct 13, 2017, at 8:16 AM, Bruce Schuchardt  wrote:
> 
> I see that the build version has been bumped to 1.4.0 on develop but I don't 
> see a 1.4.0 on JIRA & have a ticket to close today.
>

Re: version for JIRA tickets?

2017-10-13 Thread Bruce Schuchardt 

That was fast!  Thanks Anthony


On 10/13/17 8:24 AM, Anthony Baker wrote:

Fixed!

https://issues.apache.org/jira/projects/GEODE/versions/12341842 


Anthony


On Oct 13, 2017, at 8:16 AM, Bruce Schuchardt  wrote:

I see that the build version has been bumped to 1.4.0 on develop but I don't see a 
1.4.0 on JIRA & have a ticket to close today.

Jenkins build is back to normal : Geode-nightly-flaky #148

2017-10-13 Thread Apache Jenkins Server 
See

Re: version for JIRA tickets?

2017-10-13 Thread Kirk Lund 
I have a couple commits from yesterday (and maybe 1 from Wed) that I still
need to close the corresponding Jira ticket for. How do I determine if the
commit made it into 1.3 or will instead be in 1.4?

On Fri, Oct 13, 2017 at 8:35 AM, Bruce Schuchardt 
wrote:

> That was fast!  Thanks Anthony
>
>
>
> On 10/13/17 8:24 AM, Anthony Baker wrote:
>
>> Fixed!
>>
>> https://issues.apache.org/jira/projects/GEODE/versions/12341842 <
>> https://issues.apache.org/jira/projects/GEODE/versions/12341842>
>>
>> Anthony
>>
>> On Oct 13, 2017, at 8:16 AM, Bruce Schuchardt 
>>> wrote:
>>>
>>> I see that the build version has been bumped to 1.4.0 on develop but I
>>> don't see a 1.4.0 on JIRA & have a ticket to close today.
>>>
>>>
>>
>

Re: version for JIRA tickets?

2017-10-13 Thread Bruce Schuchardt 
Shall I bump the actual product version to 1.4.0?  Swapnil bumped the 
version that gradle knows about but didn't update Version.java



On 10/13/17 8:24 AM, Anthony Baker wrote:

Fixed!

https://issues.apache.org/jira/projects/GEODE/versions/12341842 


Anthony


On Oct 13, 2017, at 8:16 AM, Bruce Schuchardt  wrote:

I see that the build version has been bumped to 1.4.0 on develop but I don't see a 
1.4.0 on JIRA & have a ticket to close today.

Re: version for JIRA tickets?

2017-10-13 Thread Swapnil Bawaskar 
Yes, please do Bruce. Thanks!

On Fri, Oct 13, 2017 at 10:07 AM Bruce Schuchardt 
wrote:

> Shall I bump the actual product version to 1.4.0?  Swapnil bumped the
> version that gradle knows about but didn't update Version.java
>
>
> On 10/13/17 8:24 AM, Anthony Baker wrote:
> > Fixed!
> >
> > https://issues.apache.org/jira/projects/GEODE/versions/12341842 <
> https://issues.apache.org/jira/projects/GEODE/versions/12341842>
> >
> > Anthony
> >
> >> On Oct 13, 2017, at 8:16 AM, Bruce Schuchardt 
> wrote:
> >>
> >> I see that the build version has been bumped to 1.4.0 on develop but I
> don't see a 1.4.0 on JIRA & have a ticket to close today.
> >>
> >
>
>

Re: version for JIRA tickets?

2017-10-13 Thread Swapnil Bawaskar 
Kirk, you can checkout release/1.3.0 to verify.

On Fri, Oct 13, 2017 at 10:05 AM Kirk Lund  wrote:

> I have a couple commits from yesterday (and maybe 1 from Wed) that I still
> need to close the corresponding Jira ticket for. How do I determine if the
> commit made it into 1.3 or will instead be in 1.4?
>
> On Fri, Oct 13, 2017 at 8:35 AM, Bruce Schuchardt 
> wrote:
>
> > That was fast!  Thanks Anthony
> >
> >
> >
> > On 10/13/17 8:24 AM, Anthony Baker wrote:
> >
> >> Fixed!
> >>
> >> https://issues.apache.org/jira/projects/GEODE/versions/12341842 <
> >> https://issues.apache.org/jira/projects/GEODE/versions/12341842>
> >>
> >> Anthony
> >>
> >> On Oct 13, 2017, at 8:16 AM, Bruce Schuchardt 
> >>> wrote:
> >>>
> >>> I see that the build version has been bumped to 1.4.0 on develop but I
> >>> don't see a 1.4.0 on JIRA & have a ticket to close today.
> >>>
> >>>
> >>
> >
>

[VOTE] Apache Geode release - 1.3.0 RC2

2017-10-13 Thread Swapnil Bawaskar 
This is the second release candidate for Apache Geode, version 1.3.0. I
will send out a separate vote thread for geode-examples.
Thanks to all the community members for their contributions to this
release!

*** Please download, test and vote by Monday, October 16, 0800 hrs
US Pacific. ***

It fixes 376 issues. release notes can be found at:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420&version=12340669

Note that we are voting upon the source tags:  rel/v1.3.0.RC2
https://github.com/apache/geode/tree/rel/v1.3.0.RC2

Commit ID:
9e076738fc2ae40f95bd179b5c1624e664a28d61

Source and binary files:
 https://dist.apache.org/repos/dist/dev/geode/1.3.0.RC2

Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachegeode-1033

Geode's KEYS file containing PGP keys we use to sign the release:
 https://github.com/apache/geode/blob/develop/KEYS

Release Signed with Key: pub 4096R/18F902DB 2016-04-07
Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB

Re: [VOTE] Apache Geode release - 1.3.0 RC2

2017-10-13 Thread Swapnil Bawaskar 
I forgot to update the vote deadline. Please vote by Wednesday 10/18 by
8:00am PST.

Thanks!


On Fri, Oct 13, 2017 at 1:39 PM Swapnil Bawaskar 
wrote:

> This is the second release candidate for Apache Geode, version 1.3.0. I
> will send out a separate vote thread for geode-examples.
> Thanks to all the community members for their contributions to this
> release!
>
> *** Please download, test and vote by Monday, October 16, 0800 hrs
> US Pacific. ***
>
> It fixes 376 issues. release notes can be found at:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420&version=12340669
>
> Note that we are voting upon the source tags:  rel/v1.3.0.RC2
> https://github.com/apache/geode/tree/rel/v1.3.0.RC2
>
> Commit ID:
> 9e076738fc2ae40f95bd179b5c1624e664a28d61
>
> Source and binary files:
>  https://dist.apache.org/repos/dist/dev/geode/1.3.0.RC2
>
> Maven staging repo:
>  https://repository.apache.org/content/repositories/orgapachegeode-1033
>
> Geode's KEYS file containing PGP keys we use to sign the release:
>  https://github.com/apache/geode/blob/develop/KEYS
>
> Release Signed with Key: pub 4096R/18F902DB 2016-04-07
> Fingerprint: E1B1 ABE3 4753 E7BA 8097 4285 8F8F 2BCC 18F9 02DB
>

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #708 was SUCCESSFUL (with 2182 tests)

2017-10-13 Thread Spring CI 

---
Spring Data GemFire > Nightly-ApacheGeode > #708 was successful.
---
Scheduled
2184 tests in total.

https://build.spring.io/browse/SGF-NAG-708/





--
This message is automatically generated by Atlassian Bamboo