Geode unit tests completed in 'release-1.5.0/DistributedTest' with non-zero exit code

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/DistributedTest/builds/3

Re: Debugging dunit in intellij now fails?

Yeah, I was executing "pkill -9 java" to make sure I didn't have any Java processes running. I didn't check to see if non-Java processes might be using that port. I'll check on that soon... On Tue, Mar 6, 2018 at 1:20 PM, Jared Stewart wrote: > That looks like you have already have a process run

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

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

Re: Debugging dunit in intellij now fails?

That looks like you have already have a process running on the port that the debugger is trying to connect on. I'd try to netstat -an and kill any process bound to that port. On Tue, Mar 6, 2018 at 1:06 PM, Kirk Lund wrote: > Anyone else see this when attempting to use intellij debugger on dun

Debugging dunit in intellij now fails?

Anyone else see this when attempting to use intellij debugger on dunit?? [locator] ERROR: transport error 202: bind failed: Address already in use [locator] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) [locator] JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No trans

Re: Next release: 1.5.0

I also noticed that there are several outdated dependency versions yet... AssertJ is at *3.9.1; *Geode is at 3.8.0 Commons Lang is at *3.7;* Geode is at 2.6 JSON Path is at *2.4.0*; Geode is at 2.2.0 Log4j is at *2.10.0*; Geode is at 2.8.2 Mockito is at *2.15.0*; Geode is at 2.8.9 Netty is at *4.

Re: Next release: 1.5.0

Looks like there are some things broken related to serialization filtering as well on the release branch: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/DistributedTest/builds/2

Re: Next release: 1.5.0

I don't think this should wait since it affects downstream artifacts (already)... Pivotal GemFire -> PCC. As I stated, I am will have the changes prepared a few hours. This is pretty low risk from Apache Geode's side but is imperative for Spring/PCC users. On Tue, Mar 6, 2018 at 8:40 AM, Alexand

Re: Next release: 1.5.0

John, how much of an issue would it be if the change was added one month from now? On Tue, Mar 6, 2018 at 8:36 AM, John Blum wrote: > I have 1 addition (planning to submit a PR for review) for the 1.5 release > that is imperative for *Spring Data for Apache Geode*, and specifically, > client-sid

Re: Next release: 1.5.0

I have 1 addition (planning to submit a PR for review) for the 1.5 release that is imperative for *Spring Data for Apache Geode*, and specifically, client-side Cluster Configuration Push [1]. Details to follow soon; will file a ticket in JIRA. -j [1] https://docs.spring.io/spring-data/geode/doc

Geode unit tests 'release-1.5.0/FlakyTest' took too long to execute

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/FlakyTest/builds/1

Geode unit tests 'release-1.5.0/DistributedTest' took too long to execute

Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.5.0/jobs/DistributedTest/builds/1