Build failed in Jenkins: Geode-nightly-flaky #166

See Changes: [github] GEODE-3778: mark tests flaky (#1004) [github] GEODE-3936: remove ThreadUtil (#998) [jdeppe] Add files necessary for Concourse CI infrastructure. (#1006) [jdeppe] Fix up branches. GEODE-

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

--- Spring Data GemFire > Nightly-ApacheGeode > #729 was successful. --- Scheduled 2189 tests in total. https://build.spring.io/browse/SGF-NAG-729/ -- This

Build failed in Jenkins: Geode-nightly #1002

See Changes: [github] GEODE-3778: mark tests flaky (#1004) [github] GEODE-3936: remove ThreadUtil (#998) [jdeppe] Add files necessary for Concourse CI infrastructure. (#1006) [jdeppe] Fix up branches. GEODE-3942

Re: [DISCUSS] Maximum duration that a class may contain a @Flaky

I think majority of the flaky test tags were put in one shot in one commit. So the timer will expire on all tests in one shot. Also we have stopped marking things flaky, if something fails in CI, we immediately try to fix it. If there is a flakiness element in the test, the test is immediately modi

Re: ':geode-client-protocol' could not be found in project ':geode-assembly'

Whilst working on the protobuf protocol, it was found that there was a common set of "client protocol" stuff that was not protobuf specific. Splitting out these common pieces of code, now allows for a cleaner, more targeted protobuf (serialization) specific implementation. It also provides a platfo

[DISCUSS] Maximum duration that a class may contain a @Flaky

Hello, all! I was considering doing some git archeology centered around identifying how long a any given test class containing a @Flaky has had that annotation. Ultimately, I think it would be good to add a test that would fail when any one test has been flaky for too long. I feel like many of

Re: ':geode-client-protocol' could not be found in project ':geode-assembly'

What is the difference between these two submodules: geode-protobuf geode-client-protocol ? Thanks, Anthony > On Nov 3, 2017, at 9:22 AM, Galen O'Sullivan wrote: > > It may be that we missed one of the places where a module gets linked in. > Where did you see this error? > > On Fri, Nov 3, 2

Re: ':geode-client-protocol' could not be found in project ':geode-assembly'

Can you show me the particular error? Does it persist? As far as I can remember, we haven't changed that module this week. On Fri, Nov 3, 2017 at 9:24 AM, Kirk Lund wrote: > Precheckin last night failed to compile. > > On Fri, Nov 3, 2017 at 9:22 AM, Galen O'Sullivan > wrote: > > > It may be th

Re: ':geode-client-protocol' could not be found in project ':geode-assembly'

Precheckin last night failed to compile. On Fri, Nov 3, 2017 at 9:22 AM, Galen O'Sullivan wrote: > It may be that we missed one of the places where a module gets linked in. > Where did you see this error? > > On Fri, Nov 3, 2017 at 9:20 AM, Kirk Lund wrote: > > > Anyone know why the build is fa

Re: ':geode-client-protocol' could not be found in project ':geode-assembly'

It may be that we missed one of the places where a module gets linked in. Where did you see this error? On Fri, Nov 3, 2017 at 9:20 AM, Kirk Lund wrote: > Anyone know why the build is failing in geode-assembly? > > * What went wrong: > A problem occurred evaluating project ':geode-assembly'. > >

':geode-client-protocol' could not be found in project ':geode-assembly'

Anyone know why the build is failing in geode-assembly? * What went wrong: A problem occurred evaluating project ':geode-assembly'. > Project with path ':geode-client-protocol' could not be found in project ':geode-assembly'.

RE: Monitor the neighbour JVM using neihbour's member-timeout

Thanks Bruce for suggestions, I will change the new variables from InternalDistributedMember to NetView and do changes related to backward compatibility. Now I know that there is another way that member can be removed from the view i.e if any member is sending a message and waits for ack-wait-t