Re: Updating geode-native-build docker image

Committers can request access to the geode docker account to push new images. Note that any geode source or binaries in these images should *only* include releases that have been voted on and approved by the PMC (e.g. v1.9.0, v1.8.0, …). Can you send me your docker username? Anthony > On Au

Updating geode-native-build docker image

Hi Geode Devs! Geode Native merged https://github.com/apache/geode-native/pull/509 this morning since our docker image was using an old Geode version. What is the proper way to update docker hub ( https://hub.docker.com/r/apachegeode/geode-native-build) with the new image? Is that something comm

Re: [DISCUSS] Time to cut Geode 1.10.0?

There appears to be consensus that this is a critical fix. The following commits have been brought into support/1.10.0 as the critical fix for GEODE-7051 : git cherry-pick -x 413800bc16d05df6

Re: ./gradlew test no longer runs/reruns tests?

For more information/background on gradle and running tests, I suggest reading this blog post from the gradle team https://blog.gradle.org/stop-rerunning-tests -michael On Wed, Aug 7, 2019 at 11:58 AM Jacob Barrett wrote: > Gradle has, for as long as I can recall, always had this behavior for

Re: ./gradlew test no longer runs/reruns tests?

Gradle has, for as long as I can recall, always had this behavior for unit tests. The default in Gradle Test plugin is to not rerun tests unless the main sources have changed. For integration, distributed and acceptance tests we have changed that default to always run regardless of source change

Re: Unit tests are hanging?

Still trying to identify the cause of the unit test hangs.stay tuned. For other people who might not know this, the reason the entire CI job fails rather than the hanging test is because we don't have any global test-level timeouts, so a hanging test will run up until the Concourse timeout is r

Re: Unit tests are hanging?

Yeah, that test passed on my branch in unit tests and stress tests but for some reason is hanging after the merge to develop. I've pushed an @Ignore for the test that you should pick up. On 8/7/19 10:38 AM, Kirk Lund wrote: Yep, that's the same test I'm seeing in the callstacks of my dunit tgz

Re: Unit tests are hanging?

Yep, that's the same test I'm seeing in the callstacks of my dunit tgz from concourse... Started @ 2019-08-07 07:25:18.494 + 2019-08-07 07:51:25.252 + org.apache.geode.cache30.DistributedMulticastRegionDUnitTest testMulticastAfterReconnect Ended @ 2019-08-07 08:28:16.591 + Thanks for

Re: ./gradlew test no longer runs/reruns tests?

To re-run tests it looks like the property is “forceTest”, so ./gradlew test -PforceTest should do the trick. For diagnosing the javadocs, this might come in handy: A neat gradle trick I like to use to see which dependent tasks will get run is the “-m” flag. So something like "./gradlew -m buil

Re: ./gradlew test no longer runs/reruns tests?

I have another question about an apparent change in "build". It looks like javadoc is no longer running if I do a "./gradlew build". Even "./gradlew clean build" doesn't generate all javadocs. *"./gradlew clean build" (or just "build") results in:* /Users/klund/dev/gemfire/geode [640]$ find . -na

Re: Unit tests are hanging?

I think the reflection and PowerMock warnings here are probably a red herring. We pulled down the artifacts and found that the DUnit job is hanging due to stuck threads in a newer DUnit test. I am not sure why it isn't failing the test but rather failing the entire job. I believe Bruce Schuchart

Re: Unit tests are hanging?

That makes sense…I’m running 11 and I see them > On Aug 7, 2019, at 1:11 PM, Helena Bales wrote: > > Kirk, as Lynn said in slack, these warnings are showing up with JDK11. So > you'd probably see them locally if you used 11 instead of 8. > > On Wed, Aug 7, 2019, 10:05 AM Kirk Lund wrote: > >>

Re: ./gradlew test no longer runs/reruns tests?

We added a property to force test reruns specifically, but I can't remember it off hand. More generally, is a gradle option to rerun all tasks (but this takes longer) '--rerun-tasks'. On Wed, Aug 7, 2019, 10:09 Kirk Lund wrote: > I used to use "./gradlew test" to run or rerun unit tests but it n

Re: Unit tests are hanging?

Kirk, as Lynn said in slack, these warnings are showing up with JDK11. So you'd probably see them locally if you used 11 instead of 8. On Wed, Aug 7, 2019, 10:05 AM Kirk Lund wrote: > We previously decided to stop using PowerMock in any Geode tests and remove > it. Ryan and I created https://iss

./gradlew test no longer runs/reruns tests?

I used to use "./gradlew test" to run or rerun unit tests but it no longer works. It seems to just early out... maybe gradle thinks that the unit tests were already run so it doesn't need to rerun them. Is this intentional? I assume some gradle changes were made that changed this behavior.

Re: Unit tests are hanging?

We previously decided to stop using PowerMock in any Geode tests and remove it. Ryan and I created https://issues.apache.org/jira/browse/GEODE-6143 but it's languishing because it takes a lot of time to strip out PowerMock from a test. I don't get any PowerMock warnings locally when I run unit tes

Re: Unit tests are hanging?

I'm on CIO duty today. There have been some network issues over the last 24h and all of the hangs in the CIO dashboard corresponded with network failures. The jobs have been kicked off again, so hopefully we won't see this issues again for a while. Are you consistently seeing these hangs in the PR

Re: Unit tests are hanging?

Yea. I think it might be a red herring, because I am seeing those errors in every run, passing ones two…just double checked on https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK11/builds/948

Re: Unit tests are hanging?

I don't know if the PowerMock warnings are related but that's the only thing interesting in the output before "timeout exceeded". On Wed, Aug 7, 2019 at 9:43 AM Murtuza Boxwala wrote: > How down know these warnings are related to the builds hanging. When I > was on CIO duty a couple days ago, I

Re: Unit tests are hanging?

How down know these warnings are related to the builds hanging. When I was on CIO duty a couple days ago, I remember seeing this warning in a failing build, but then I looked back at passing builds on saw this as well. > On Aug 7, 2019, at 12:40 PM, Kirk Lund wrote: > > The build is broken in

Unit tests are hanging?

The build is broken in CI right now (for main CI and PRs). The UnitTest jobs are timing out so I assume there's a hang of some sort. The WARNINGs appear to be related to PowerMock and begins with "An illegal reflective access operation" in geode-assembly:test. I'm running unit tests locally and h

Re: Travis-ci & geode-native repo

We worked with Travis support to increase our timeout on the backend. As you can see from the Travis report it takes a long time to build. It doesn’t run any of the integration tests either. We use it as a litmus test on PRs mostly. There is a future goal to role the build into the same pipelin

Travis-ci & geode-native repo

Hi, I have a question about the CI of the Geode C++ client. I would like to set up Travis on a fork of the geode-native repo. I thought that the only requirements to do so was to grant permissions to the repo, but our travis tasks are failing due to the execution timeout is 50 minutes. I dont

Re: edit permissions on wiki

Thanks, all good now! On Fri, Aug 2, 2019 at 4:32 PM Kirk Lund wrote: > Oops. Try now. > > On Fri, Aug 2, 2019 at 12:52 PM Joris Melchior > wrote: > > > Don't seem to have edit permissions yet though ... > > > > On Fri, Aug 2, 2019 at 3:48 PM Joris Melchior > > wrote: > > > > > Thanks Kirk! >