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

2017-12-20 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/42

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

2017-12-20 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/41

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

2017-12-20 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #772 was successful. --- Scheduled 2326 tests in total. https://build.spring.io/browse/SGF-NAG-772/ -- This

Re: Discussion: Native PDX Reader/Writer std::string

2017-12-20 Thread Jacob Barrett
I agree that if we could develop a version of optional that could be typedefed to C++17 optional in the future that could be an interesting win. I still hesitate to do this as the general use API though since it promotes the idea of null strings still. My current leaning is to only provide option 1

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

2017-12-20 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/58

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

2017-12-20 Thread apachegeodeci
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/AcceptanceTest/builds/68

Re: [DISCUSS]: Handling of SDTOUT/STDERR and Signals

2017-12-20 Thread Kirk Lund
Sorry, my info on redirecting of stdout and stderr was stale (circa GemFire 7.0). Now that the code base is an Apache project, I believe redirecting of stdout and stderr no longer occurs. However, it does shut off the Log4j2 ConsoleAppender to stdout when the LogWriterAppender is activated and turn

Re: Discussion: Native PDX Reader/Writer std::string

2017-12-20 Thread David Kimura
Given that C++17 is feature-complete, it seems prudent to adopt those patterns as much as possible. My fear with #4 is that we're introducing a special case API that users become accustomed to and then unwilling to later switch to std::optional. And then we'd end up supporting multiple ways to do

Re: [DISCUSS]: Handling of SDTOUT/STDERR and Signals

2017-12-20 Thread Jens Deppe
Hi Juan, Thanks for the detailed analysis. I did some digging too and cannot see why the QUIT signal might be getting lost. I'll do some more investigation... Just for reference, you can still use the 'jstack' tool to get thread dumps although they just show on the terminal where you run the com

Re: [DISCUSS]: Handling of SDTOUT/STDERR and Signals

2017-12-20 Thread Juan José Ramos
Hello again, Regarding my last question from the original email (unformatted jetty logging when enabling --*redirect-output*), it looks like the offending library within the *geode-pulse.war* is *commons-logging-x.x.jar.* The library is configured as *providedCompile* in *build.gradle* and, by def