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

2015-09-04 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #56 was successful. --- Scheduled 1144 tests in total. https://build.spring.io/browse/SGF-NAG-56/ -- This me

Re: GEODE-218: Dunit Fork Every 1

2015-09-04 Thread Catherine Johnson
+1 Thanks!!! > On Sep 4, 2015, at 3:17 PM, Anthony Baker wrote: > > BTW, I modified the “Geode in 5 min” wiki page to include build instructions > for skipping tests. I’ll do the same for README.md unless I hear any > objections. > > Anthony > > >> On Sep 4, 2015, at 12:33 PM, Anthony Baker

Re: GEODE-218: Dunit Fork Every 1

2015-09-04 Thread Anthony Baker
BTW, I modified the “Geode in 5 min” wiki page to include build instructions for skipping tests. I’ll do the same for README.md unless I hear any objections. Anthony > On Sep 4, 2015, at 12:33 PM, Anthony Baker wrote: > > Another note: these timings are from server-class workstations. On a

gemfire-core:integrationTest failures on Windows

2015-09-04 Thread Kirk Lund
The following is the results of running gemfire-core:integrationTest on Windows. There are 164 failures and it looks like all of the HDFS tests fail on Windows. Are these tests supposed to be passing on Windows? Should I file a JIRA? Should they be ignored on Windows? Do they require Linux? Test

Re: Review Request 38135: make pdx logging info level

2015-09-04 Thread anilkumar gingade
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38135/#review97813 --- Ship it! Ship It! - anilkumar gingade On Sept. 4, 2015, 8:50 p.m

Re: Review Request 38135: make pdx logging info level

2015-09-04 Thread Kirk Lund
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38135/#review97812 --- Ship it! Ship It! gemfire-core/src/main/java/com/gemstone/gemfire

Review Request 38135: make pdx logging info level

2015-09-04 Thread Darrel Schneider
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38135/ --- Review request for geode and Kirk Lund. Bugs: GEODE-311 https://issues.apac

Re: Review Request 38029: GEODE-306: support printing of off-heap compressed nodes

2015-09-04 Thread Kirk Lund
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38029/#review97796 --- Ship it! Ship It! - Kirk Lund On Sept. 1, 2015, 11:46 p.m., Darr

Re: Review Request 38133: Move AgentUtilJUnitTest into a package

2015-09-04 Thread Darrel Schneider
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38133/#review97794 --- Ship it! Ship It! - Darrel Schneider On Sept. 4, 2015, 12:36 p.m

Re: GEODE-218: Dunit Fork Every 1

2015-09-04 Thread Jacob Barrett
Can any of them be launched in parallel? This could cut down time significantly. Jacob Barrett  Manager  GemFire Advanced Customer Engineering (ACE)  Pivotal jbarr...@pivotal.io  503-533-3763 For immediate support please contact Pivotal Support at  http://support.pivotal.io/ On Fri, Sep 4, 2

Re: Review Request 38133: Move AgentUtilJUnitTest into a package

2015-09-04 Thread Kirk Lund
> On None, Kirk Lund wrote: > > Ship It! Ignore this. I meant to hit "Publish" instead of "Ship It!" (long week!) - Kirk --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38133/#review97786 ---

Review Request 38133: Move AgentUtilJUnitTest into a package

2015-09-04 Thread Kirk Lund
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/38133/ --- Review request for geode and Darrel Schneider. Bugs: GEODE-309 https://issu

Re: GEODE-218: Dunit Fork Every 1

2015-09-04 Thread Anthony Baker
Another note: these timings are from server-class workstations. On a laptop the overall test length (without the change) can run 18+ hours. Anthony > On Sep 4, 2015, at 12:21 PM, Kirk Lund wrote: > > +1 > > I like the idea of switching to fork=1 for a few months to focus on > stabilizing a

Re: GEODE-218: Dunit Fork Every 1

2015-09-04 Thread Kirk Lund
+1 I like the idea of switching to fork=1 for a few months to focus on stabilizing any dunit tests that fail without potential test pollution causes. These failures are mostly like ones that involve race conditions. Once we fix these, then we could change back to fork=30. On Fri, Sep 4, 2015 at

GEODE-218: Dunit Fork Every 1

2015-09-04 Thread Mark Bretl
I see that Kirk made an update to the issue and wanted to follow up on the Dev list for discussion. I also ran a build on the open side with the dunit fork = 1. The total time of the build was: 9 hrs 58 mins 33.662 secs. The last Geode build took: 6 hr 21 min

Build failed in Jenkins: Geode-nightly #205

2015-09-04 Thread Apache Jenkins Server
See Changes: [upthewaterspout] GEODE-307: Clear DiskStoreObserver after each test -- [...truncated 2722 lines...] at com.gemstone.gemfire.internal.redis.RegionProvider.getOrCreateRegion(Reg