Re: Updating geode-native-build docker image

[Anthony Baker]

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 Aug 7, 2019, at 3:47 PM, Michael Oleske  wrote:
> 
> 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 committers should be able to do?  Or is there an
> automated build that updates docker hub?
> 
> Thanks!
> -michael

Updating geode-native-build docker image

[Michael Oleske]

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 committers should be able to do?  Or is there an
automated build that updates docker hub?

Thanks!
-michael

Re: [DISCUSS] Time to cut Geode 1.10.0?

[Owen Nichols]

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 413800bc16d05df689a2af5c30797f180aad6088 

git cherry-pick -x e1b61cdcaf38966bbb732b0b3db5223f2cc4f5e4 


GEODE-7051  has been marked 
as 'resolved in' 1.10.0.

-Owen

> On Aug 6, 2019, at 1:39 PM, Bruce Schuchardt  wrote:
> 
> +1
> 
> On 8/6/19 1:33 PM, Nabarun Nag wrote:
>> +1 on getting the Fix [Upgrade
>> log4j from 2.11.1 to 2.12.0 and mark log4j-core as an optional dependency
>> in the geode-core pom.] in.
>> 
>> 
>> Spring Data for Apache Geode has been removed from Spring Initializr
>> because of the issue with  log4j dependencies, also IntelliJ doesn't list
>> it as a NoSQL dependency. I would prefer that it is resolved in this
>> release and not wait for 3-4 months.
>> 
>> Regards
>> Naba
>> 
>> 
>> 
>> On Tue, Aug 6, 2019 at 1:00 PM Owen Nichols  wrote:
>> 
>>> Hi Kirk, thank you for bringing your concern.
>>> 
>>> Yes, release/1.10.0 was created last week <
>>> https://lists.apache.org/thread.html/4d4388ccab1170d94b8b6d204efe9197a4d3ddc2d25cbb6e6cecee0d@%3Cdev.geode.apache.org%3E>
>>> as planned.  Our current process <
>>> https://lists.apache.org/thread.html/d36a63c3794d13506ecad3d52a2aca938dcf0f8509b61860bbbc50cd@%3Cdev.geode.apache.org%3E>
>>> dictates a time-based schedule to cut release branches.  Once cut, the
>>> “critical fixes” rule allows critical fixes to be brought to the release
>>> branch by proposal on the dev list.
>>> 
>>> Currently the 1.10.0 release pipeline <
>>> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-release-1-10-0-main>
>>> is all green.  If there is consensus from the Geode community that this
>>> log4j change satisfies the “critical fixes” rule, Dick or I will be happy
>>> to bring it to the 1.10.0 release branch.
>>> 
>>> -Owen
>>> 
 On Aug 6, 2019, at 12:49 PM, Kirk Lund  wrote:
 
 Did we already cut the 1.10 branch?
 
 I'd like to find out if it's possible to get a change into 1.10: Upgrade
 log4j from 2.11.1 to 2.12.0 and mark log4j-core as an optional dependency
 in the geode-core pom.
 
 Getting this change into 1.10 will make things much easier for Spring
>>> Boot
 Data Geode. When using Geode with Spring Boot, log4j-core has to be
 manually excluded so that logback can be used instead. The change to
>>> log4j
 2.12.0 will also help as they have already have some dependency on 2.12.0
 (probably log4j-to-slf4j). I can find out more precise details if needed.
 
 On Wed, Jul 31, 2019 at 9:35 AM Dick Cavender  wrote:
 
> In preparation for cutting the release branch have we confirmed that
> Geode's LICENSE and NOTICE file been confirmed to accurately reflect
>>> what
> is being shipped for v1.10?
> 
> From Apache: http://www.apache.org/dev/licensing-howto.html
> *"*The LICENSE and NOTICE files must exactly represent the contents of
>>> the
> distribution they reside in."
> 
> Ideally this is kept up to date during development as the dependencies
> change or are added but this often is missed and needs to be reconciled
>>> on
> develop before we cut a release branch.
> 
> -Dick
> 
> 
> 
> 
> 
> On Tue, Jul 30, 2019 at 6:04 PM Owen Nichols 
>>> wrote:
>> From that email:
>> 
>> To make this work, it's important to be strict
>> about cutting the release branch on the set date and only allow
>>> critical
>> fixes after the release has been cut. Once we start compromising on
>>> this,
>> we go down a slippery slope that ultimately leads to not getting the
>> predictability benefits described here.
>> 
>> We are perilously close to the "slippery slope”:
>> * Geode 1.8.0 was announced on Dec 12 — almost 8 months ago
>> * Geode 1.9.0 was announced on Apr 25 — putting us about 5 weeks late
>> already on cutting the 1.10 branch
>> 
>> It seems like the community reaction to branching from the SHA
>>> initially
>> proposed is “woah, not quite yet”.
>> 
>> To get last-minute stuff in (or out) and get back on track, I propose
>> setting a strict CUT date for the 1.10 branch at 3PM PDT Thursday
>>> August
> 1.
>> -Owen
>> 
>> 
>>> On Jul 30, 2019, at 5:31 PM, Alexander Murmann 
>> wrote:
>>> Hi Karen,
>>> 
>>> Here is the previous discussion that was very positively received:
>>> 
>>> https://lists.apache.org/thread.html/d36a63c3794d13506ecad3d52a2aca938dcf0f8509b61860bbbc50cd@%3Cdev.geode.apache.org%3E
>>> However, 

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

[Michael Oleske]

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 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
> changes.
>
> > On Aug 7, 2019, at 10:08 AM, Kirk Lund  wrote:
> >
> > 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: ./gradlew test no longer runs/reruns tests?

[Jacob Barrett]

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 changes.

> On Aug 7, 2019, at 10:08 AM, Kirk Lund  wrote:
> 
> 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?

[Ryan McMahon]

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 reached.  I wrote a story to explore adding test level timeouts
so we can get actual feedback in the CI about which test is hanging without
waiting for the whole job to timeout, downloading artifacts, looking at the
stack dumps, etc etc.  I think we could have some reasonable global upper
limit (30 minutes?) for any test.  We could always tune that as needed.
https://issues.apache.org/jira/projects/GEODE/issues/GEODE-7057?filter=allopenissues

Ryan

On Wed, Aug 7, 2019 at 11:21 AM Bruce Schuchardt 
wrote:

> 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
> 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 digging into it!
> >
> > On Wed, Aug 7, 2019 at 10:16 AM Ryan McMahon 
> wrote:
> >
> >> 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 is going to dig into this a bit.  Analysis from Lynn
> >> Hughes-Godfrey:
> >>
> >> So, I downloaded
> >>
> >>
> >>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/961
> >>
> >> to
> >>
> >>
> >>
> /Users/lhughesgodfrey/Downloads/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0010/geode-core/build/distributedTest
> >>
> >> In that callstacks directory, you'll see dunit-hangs.txt ... and this
> >> test has been running for over an hour ...
> >>
> >> ```
> >>
> >> Started @ 2019-08-07 07:54:10.272 +
> >>
> >> 2019-08-07 08:22:25.440 +
> >> org.apache.geode.cache30.DistributedMulticastRegionDUnitTest
> >> testMulticastAfterReconnect
> >>
> >> Ended @ 2019-08-07 08:58:50.243 +
> >>
> >> ```
> >>
> >> When I look at the callstacks (at the top level), I see this:
> >>
> >> ```
> >>
> >> "Pooled Waiting Message Processor 1" #213 daemon prio=5 os_prio=0
> >> tid=0x7fc738024000 nid=0x488 waiting for monitor entry
> >> [0x7fc7ec5f7000]
> >>
> >> java.lang.Thread.State: BLOCKED (on object monitor)
> >>
> >>  at
> >>
> org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.startEventProcessing(GMSMembershipManager.java:1179)
> >>
> >>  - waiting to lock <0xe03a75e0> (a java.lang.Object)
> >>
> >>  at
> >>
> org.apache.geode.distributed.internal.ClusterDistributionManager.readyForMessages(ClusterDistributionManager.java:1152)
> >>
> >>  at
> >>
> org.apache.geode.distributed.internal.ClusterDistributionManager.lambda$startThreads$10(ClusterDistributionManager.java:1129)
> >>
> >>  at
> >>
> org.apache.geode.distributed.internal.ClusterDistributionManager$$Lambda$87/1408912936.run(Unknown
> >> Source)
> >>
> >>  at
> >>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> >>
> >>  at
> >>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> >>
> >>  at
> >>
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:961)
> >>
> >>  at
> >>
> org.apache.geode.distributed.internal.ClusterDistributionManager.doWaitingThread(ClusterDistributionManager.java:851)
> >>
> >>  at
> >>
> org.apache.geode.distributed.internal.ClusterDistributionManager$$Lambda$53/274751999.invoke(Unknown
> >> Source)
> >>
> >>  at
> >>
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
> >>
> >>  at
> >>
> org.apache.geode.internal.logging.LoggingThreadFactory$$Lambda$49/1824093464.run(Unknown
> >> Source)
> >>
> >>  at java.lang.Thread.run(Thread.java:748)
> >>
> >> Locked ownable synchronizers:
> >>
> >>  - <0xe03a7660> (a
> >> java.util.concurrent.ThreadPoolExecutor$Worker)
> >>
> >> ```
> >>
> >> This thread holds the lock:
> >>
> >> ```
> >>
> >> "ReconnectThread" #193 prio=5 os_prio=0 tid=0x7fc7cc219000
> >> nid=0x46a waiting on condition [0x7fc78bdfb000]
> >>
> >> java.lang.Thread.State: TIMED_WAITING (sleeping)
> >>
> >>  at 

Re: Unit tests are hanging?

[Bruce Schuchardt]

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 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 digging into it!

On Wed, Aug 7, 2019 at 10:16 AM Ryan McMahon  wrote:


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 is going to dig into this a bit.  Analysis from Lynn
Hughes-Godfrey:

So, I downloaded


https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/961

to


/Users/lhughesgodfrey/Downloads/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0010/geode-core/build/distributedTest

In that callstacks directory, you'll see dunit-hangs.txt ... and this
test has been running for over an hour ...

```

Started @ 2019-08-07 07:54:10.272 +

2019-08-07 08:22:25.440 +
org.apache.geode.cache30.DistributedMulticastRegionDUnitTest
testMulticastAfterReconnect

Ended @ 2019-08-07 08:58:50.243 +

```

When I look at the callstacks (at the top level), I see this:

```

"Pooled Waiting Message Processor 1" #213 daemon prio=5 os_prio=0
tid=0x7fc738024000 nid=0x488 waiting for monitor entry
[0x7fc7ec5f7000]

java.lang.Thread.State: BLOCKED (on object monitor)

 at
org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.startEventProcessing(GMSMembershipManager.java:1179)

 - waiting to lock <0xe03a75e0> (a java.lang.Object)

 at
org.apache.geode.distributed.internal.ClusterDistributionManager.readyForMessages(ClusterDistributionManager.java:1152)

 at
org.apache.geode.distributed.internal.ClusterDistributionManager.lambda$startThreads$10(ClusterDistributionManager.java:1129)

 at
org.apache.geode.distributed.internal.ClusterDistributionManager$$Lambda$87/1408912936.run(Unknown
Source)

 at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

 at
org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:961)

 at
org.apache.geode.distributed.internal.ClusterDistributionManager.doWaitingThread(ClusterDistributionManager.java:851)

 at
org.apache.geode.distributed.internal.ClusterDistributionManager$$Lambda$53/274751999.invoke(Unknown
Source)

 at
org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)

 at
org.apache.geode.internal.logging.LoggingThreadFactory$$Lambda$49/1824093464.run(Unknown
Source)

 at java.lang.Thread.run(Thread.java:748)

Locked ownable synchronizers:

 - <0xe03a7660> (a
java.util.concurrent.ThreadPoolExecutor$Worker)

```

This thread holds the lock:

```

"ReconnectThread" #193 prio=5 os_prio=0 tid=0x7fc7cc219000
nid=0x46a waiting on condition [0x7fc78bdfb000]

java.lang.Thread.State: TIMED_WAITING (sleeping)

 at java.lang.Thread.sleep(Native Method)

 at
org.apache.geode.internal.tcp.Connection.createSender(Connection.java:959)

 at
org.apache.geode.internal.tcp.ConnectionTable.handleNewPendingConnection(ConnectionTable.java:297)

 at
org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:408)

 at
org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:593)

 at
org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:825)

 at
org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:537)

 at
org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:326)

 at
org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:241)

 at
org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:596)

 at
org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1558)

 at
org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.send(GMSMembershipManager.java:1739)

 at
org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2849)

 at

Re: Unit tests are hanging?

[Kirk Lund]

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 digging into it!

On Wed, Aug 7, 2019 at 10:16 AM Ryan McMahon  wrote:

> 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 is going to dig into this a bit.  Analysis from Lynn
> Hughes-Godfrey:
>
> So, I downloaded
>
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/961
>
> to
>
>
> /Users/lhughesgodfrey/Downloads/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0010/geode-core/build/distributedTest
>
> In that callstacks directory, you'll see dunit-hangs.txt ... and this
> test has been running for over an hour ...
>
> ```
>
> Started @ 2019-08-07 07:54:10.272 +
>
> 2019-08-07 08:22:25.440 +
> org.apache.geode.cache30.DistributedMulticastRegionDUnitTest
> testMulticastAfterReconnect
>
> Ended @ 2019-08-07 08:58:50.243 +
>
> ```
>
> When I look at the callstacks (at the top level), I see this:
>
> ```
>
> "Pooled Waiting Message Processor 1" #213 daemon prio=5 os_prio=0
> tid=0x7fc738024000 nid=0x488 waiting for monitor entry
> [0x7fc7ec5f7000]
>
>java.lang.Thread.State: BLOCKED (on object monitor)
>
> at
> org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.startEventProcessing(GMSMembershipManager.java:1179)
>
> - waiting to lock <0xe03a75e0> (a java.lang.Object)
>
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.readyForMessages(ClusterDistributionManager.java:1152)
>
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.lambda$startThreads$10(ClusterDistributionManager.java:1129)
>
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$$Lambda$87/1408912936.run(Unknown
> Source)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:961)
>
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.doWaitingThread(ClusterDistributionManager.java:851)
>
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager$$Lambda$53/274751999.invoke(Unknown
> Source)
>
> at
> org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)
>
> at
> org.apache.geode.internal.logging.LoggingThreadFactory$$Lambda$49/1824093464.run(Unknown
> Source)
>
> at java.lang.Thread.run(Thread.java:748)
>
>Locked ownable synchronizers:
>
> - <0xe03a7660> (a
> java.util.concurrent.ThreadPoolExecutor$Worker)
>
> ```
>
> This thread holds the lock:
>
> ```
>
> "ReconnectThread" #193 prio=5 os_prio=0 tid=0x7fc7cc219000
> nid=0x46a waiting on condition [0x7fc78bdfb000]
>
>java.lang.Thread.State: TIMED_WAITING (sleeping)
>
> at java.lang.Thread.sleep(Native Method)
>
> at
> org.apache.geode.internal.tcp.Connection.createSender(Connection.java:959)
>
> at
> org.apache.geode.internal.tcp.ConnectionTable.handleNewPendingConnection(ConnectionTable.java:297)
>
> at
> org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:408)
>
> at
> org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:593)
>
> at
> org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:825)
>
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:537)
>
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:326)
>
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:241)
>
> at
> org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:596)
>
> at
> org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1558)
>
> at
> org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.send(GMSMembershipManager.java:1739)
>
> at
> org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2849)
>
> at
> 

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

[Murtuza Boxwala]

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 build" will show all the tasks that will run 
without actually running them.

> On Aug 7, 2019, at 1:19 PM, Kirk Lund  wrote:
> 
> 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 . -name
> "javadocs"
> ./geode-assembly/build/javadocs
> /Users/klund/dev/gemfire/geode [641]$ find . -name
> "javadoc"
> ./geode-old-versions/1.9.0/build/apache-geode-1.9.0/javadoc
> ./geode-old-versions/1.3.0/build/apache-geode-1.3.0/javadoc
> ./geode-old-versions/1.7.0/build/apache-geode-1.7.0/javadoc
> ./geode-old-versions/1.4.0/build/apache-geode-1.4.0/javadoc
> ./geode-old-versions/1.5.0/build/apache-geode-1.5.0/javadoc
> ./geode-old-versions/1.2.0/build/apache-geode-1.2.0/javadoc
> ./geode-old-versions/1.8.0/build/apache-geode-1.8.0/javadoc
> ./geode-old-versions/1.6.0/build/apache-geode-1.6.0/javadoc
> ./geode-assembly/build/install/apache-geode/javadoc
> 
> *"./gradlew javadoc" results in:*
> 
> /Users/klund/dev/geode3 [576]$ find . -name
> "javadocs"
> ./geode-assembly/build/javadocs
> /Users/klund/dev/geode3 [577]$ find . -name
> "javadoc"
> ./geode-pulse/geode-pulse-test/build/javadoc
> ./geode-pulse/geode-pulse-test/build/tmp/javadoc
> ./geode-junit/build/javadoc
> ./geode-junit/build/tmp/javadoc
> ./geode-concurrency-test/build/javadoc
> ./geode-concurrency-test/build/tmp/javadoc
> ./geode-lucene/geode-lucene-test/build/javadoc
> ./geode-lucene/geode-lucene-test/build/tmp/javadoc
> ./geode-lucene/build/javadoc
> ./geode-lucene/build/tmp/javadoc
> ./geode-redis/build/javadoc
> ./geode-redis/build/tmp/javadoc
> ./geode-json/build/javadoc
> ./geode-json/build/tmp/javadoc
> ./geode-old-versions/1.9.0/build/apache-geode-1.9.0/javadoc
> ./geode-old-versions/1.3.0/build/apache-geode-1.3.0/javadoc
> ./geode-old-versions/1.7.0/build/apache-geode-1.7.0/javadoc
> ./geode-old-versions/1.4.0/build/apache-geode-1.4.0/javadoc
> ./geode-old-versions/1.5.0/build/apache-geode-1.5.0/javadoc
> ./geode-old-versions/1.2.0/build/apache-geode-1.2.0/javadoc
> ./geode-old-versions/1.8.0/build/apache-geode-1.8.0/javadoc
> ./geode-old-versions/1.6.0/build/apache-geode-1.6.0/javadoc
> ./geode-memcached/build/javadoc
> ./geode-memcached/build/tmp/javadoc
> ./geode-assembly/build/install/apache-geode/javadoc
> ./geode-assembly/geode-assembly-test/build/javadoc
> ./geode-assembly/geode-assembly-test/build/tmp/javadoc
> ./extensions/geode-modules-session/build/javadoc
> ./extensions/geode-modules-session/build/tmp/javadoc
> ./extensions/session-testing-war/build/javadoc
> ./extensions/session-testing-war/build/tmp/javadoc
> ./extensions/geode-modules-test/build/javadoc
> ./extensions/geode-modules-test/build/tmp/javadoc
> ./extensions/geode-modules-tomcat8/build/javadoc
> ./extensions/geode-modules-tomcat8/build/tmp/javadoc
> ./extensions/geode-modules-tomcat7/build/javadoc
> ./extensions/geode-modules-tomcat7/build/tmp/javadoc
> ./extensions/geode-modules-tomcat9/build/javadoc
> ./extensions/geode-modules-tomcat9/build/tmp/javadoc
> ./extensions/geode-modules/build/javadoc
> ./extensions/geode-modules/build/tmp/javadoc
> ./geode-management/build/javadoc
> ./geode-management/build/tmp/javadoc
> ./geode-rebalancer/build/javadoc
> ./geode-rebalancer/build/tmp/javadoc
> ./geode-dunit/build/javadoc
> ./geode-dunit/build/tmp/javadoc
> ./geode-core/build/javadoc
> ./geode-core/build/tmp/javadoc
> ./static-analysis/pmd-rules/build/javadoc
> ./static-analysis/pmd-rules/build/tmp/javadoc
> ./geode-protobuf/build/javadoc
> ./geode-protobuf/build/tmp/javadoc
> ./geode-common/build/javadoc
> ./geode-common/build/tmp/javadoc
> ./geode-experimental-driver/build/javadoc
> ./geode-experimental-driver/build/tmp/javadoc
> ./geode-connectors/build/javadoc
> ./geode-connectors/build/tmp/javadoc
> ./geode-old-client-support/build/javadoc
> ./geode-old-client-support/build/tmp/javadoc
> 
> On Wed, Aug 7, 2019 at 10:13 AM Robert Houghton 
> wrote:
> 
>> 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 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: ./gradlew test no longer runs/reruns tests?

[Kirk Lund]

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 . -name
"javadocs"
./geode-assembly/build/javadocs
/Users/klund/dev/gemfire/geode [641]$ find . -name
"javadoc"
./geode-old-versions/1.9.0/build/apache-geode-1.9.0/javadoc
./geode-old-versions/1.3.0/build/apache-geode-1.3.0/javadoc
./geode-old-versions/1.7.0/build/apache-geode-1.7.0/javadoc
./geode-old-versions/1.4.0/build/apache-geode-1.4.0/javadoc
./geode-old-versions/1.5.0/build/apache-geode-1.5.0/javadoc
./geode-old-versions/1.2.0/build/apache-geode-1.2.0/javadoc
./geode-old-versions/1.8.0/build/apache-geode-1.8.0/javadoc
./geode-old-versions/1.6.0/build/apache-geode-1.6.0/javadoc
./geode-assembly/build/install/apache-geode/javadoc

*"./gradlew javadoc" results in:*

/Users/klund/dev/geode3 [576]$ find . -name
"javadocs"
./geode-assembly/build/javadocs
/Users/klund/dev/geode3 [577]$ find . -name
"javadoc"
./geode-pulse/geode-pulse-test/build/javadoc
./geode-pulse/geode-pulse-test/build/tmp/javadoc
./geode-junit/build/javadoc
./geode-junit/build/tmp/javadoc
./geode-concurrency-test/build/javadoc
./geode-concurrency-test/build/tmp/javadoc
./geode-lucene/geode-lucene-test/build/javadoc
./geode-lucene/geode-lucene-test/build/tmp/javadoc
./geode-lucene/build/javadoc
./geode-lucene/build/tmp/javadoc
./geode-redis/build/javadoc
./geode-redis/build/tmp/javadoc
./geode-json/build/javadoc
./geode-json/build/tmp/javadoc
./geode-old-versions/1.9.0/build/apache-geode-1.9.0/javadoc
./geode-old-versions/1.3.0/build/apache-geode-1.3.0/javadoc
./geode-old-versions/1.7.0/build/apache-geode-1.7.0/javadoc
./geode-old-versions/1.4.0/build/apache-geode-1.4.0/javadoc
./geode-old-versions/1.5.0/build/apache-geode-1.5.0/javadoc
./geode-old-versions/1.2.0/build/apache-geode-1.2.0/javadoc
./geode-old-versions/1.8.0/build/apache-geode-1.8.0/javadoc
./geode-old-versions/1.6.0/build/apache-geode-1.6.0/javadoc
./geode-memcached/build/javadoc
./geode-memcached/build/tmp/javadoc
./geode-assembly/build/install/apache-geode/javadoc
./geode-assembly/geode-assembly-test/build/javadoc
./geode-assembly/geode-assembly-test/build/tmp/javadoc
./extensions/geode-modules-session/build/javadoc
./extensions/geode-modules-session/build/tmp/javadoc
./extensions/session-testing-war/build/javadoc
./extensions/session-testing-war/build/tmp/javadoc
./extensions/geode-modules-test/build/javadoc
./extensions/geode-modules-test/build/tmp/javadoc
./extensions/geode-modules-tomcat8/build/javadoc
./extensions/geode-modules-tomcat8/build/tmp/javadoc
./extensions/geode-modules-tomcat7/build/javadoc
./extensions/geode-modules-tomcat7/build/tmp/javadoc
./extensions/geode-modules-tomcat9/build/javadoc
./extensions/geode-modules-tomcat9/build/tmp/javadoc
./extensions/geode-modules/build/javadoc
./extensions/geode-modules/build/tmp/javadoc
./geode-management/build/javadoc
./geode-management/build/tmp/javadoc
./geode-rebalancer/build/javadoc
./geode-rebalancer/build/tmp/javadoc
./geode-dunit/build/javadoc
./geode-dunit/build/tmp/javadoc
./geode-core/build/javadoc
./geode-core/build/tmp/javadoc
./static-analysis/pmd-rules/build/javadoc
./static-analysis/pmd-rules/build/tmp/javadoc
./geode-protobuf/build/javadoc
./geode-protobuf/build/tmp/javadoc
./geode-common/build/javadoc
./geode-common/build/tmp/javadoc
./geode-experimental-driver/build/javadoc
./geode-experimental-driver/build/tmp/javadoc
./geode-connectors/build/javadoc
./geode-connectors/build/tmp/javadoc
./geode-old-client-support/build/javadoc
./geode-old-client-support/build/tmp/javadoc

On Wed, Aug 7, 2019 at 10:13 AM Robert Houghton 
wrote:

> 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 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?

[Ryan McMahon]

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 is going to dig into this a bit.  Analysis from Lynn
Hughes-Godfrey:

So, I downloaded

https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/961

to

/Users/lhughesgodfrey/Downloads/distributedtestfiles-OpenJDK8-1.11.0-SNAPSHOT.0010/geode-core/build/distributedTest

In that callstacks directory, you'll see dunit-hangs.txt ... and this
test has been running for over an hour ...

```

Started @ 2019-08-07 07:54:10.272 +

2019-08-07 08:22:25.440 +
org.apache.geode.cache30.DistributedMulticastRegionDUnitTest
testMulticastAfterReconnect

Ended @ 2019-08-07 08:58:50.243 +

```

When I look at the callstacks (at the top level), I see this:

```

"Pooled Waiting Message Processor 1" #213 daemon prio=5 os_prio=0
tid=0x7fc738024000 nid=0x488 waiting for monitor entry
[0x7fc7ec5f7000]

   java.lang.Thread.State: BLOCKED (on object monitor)

at 
org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.startEventProcessing(GMSMembershipManager.java:1179)

- waiting to lock <0xe03a75e0> (a java.lang.Object)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager.readyForMessages(ClusterDistributionManager.java:1152)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager.lambda$startThreads$10(ClusterDistributionManager.java:1129)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager$$Lambda$87/1408912936.run(Unknown
Source)

at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager.runUntilShutdown(ClusterDistributionManager.java:961)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager.doWaitingThread(ClusterDistributionManager.java:851)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager$$Lambda$53/274751999.invoke(Unknown
Source)

at 
org.apache.geode.internal.logging.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:121)

at 
org.apache.geode.internal.logging.LoggingThreadFactory$$Lambda$49/1824093464.run(Unknown
Source)

at java.lang.Thread.run(Thread.java:748)

   Locked ownable synchronizers:

- <0xe03a7660> (a
java.util.concurrent.ThreadPoolExecutor$Worker)

```

This thread holds the lock:

```

"ReconnectThread" #193 prio=5 os_prio=0 tid=0x7fc7cc219000
nid=0x46a waiting on condition [0x7fc78bdfb000]

   java.lang.Thread.State: TIMED_WAITING (sleeping)

at java.lang.Thread.sleep(Native Method)

at 
org.apache.geode.internal.tcp.Connection.createSender(Connection.java:959)

at 
org.apache.geode.internal.tcp.ConnectionTable.handleNewPendingConnection(ConnectionTable.java:297)

at 
org.apache.geode.internal.tcp.ConnectionTable.getSharedConnection(ConnectionTable.java:408)

at 
org.apache.geode.internal.tcp.ConnectionTable.get(ConnectionTable.java:593)

at 
org.apache.geode.internal.tcp.TCPConduit.getConnection(TCPConduit.java:825)

at 
org.apache.geode.distributed.internal.direct.DirectChannel.getConnections(DirectChannel.java:537)

at 
org.apache.geode.distributed.internal.direct.DirectChannel.sendToMany(DirectChannel.java:326)

at 
org.apache.geode.distributed.internal.direct.DirectChannel.sendToOne(DirectChannel.java:241)

at 
org.apache.geode.distributed.internal.direct.DirectChannel.send(DirectChannel.java:596)

at 
org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.directChannelSend(GMSMembershipManager.java:1558)

at 
org.apache.geode.distributed.internal.membership.adapter.GMSMembershipManager.send(GMSMembershipManager.java:1739)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager.sendViaMembershipManager(ClusterDistributionManager.java:2849)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager.sendOutgoing(ClusterDistributionManager.java:2776)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager.sendMessage(ClusterDistributionManager.java:2813)

at 
org.apache.geode.distributed.internal.ClusterDistributionManager.putOutgoing(ClusterDistributionManager.java:1523)

at 
org.apache.geode.distributed.internal.ReplyMessage.send(ReplyMessage.java:174)

at 
org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.sendReply(DistributedCacheOperation.java:1269)

at 

Re: Unit tests are hanging?

[Murtuza Boxwala]

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:
> 
>> 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 tests.
>> 
>> On Wed, Aug 7, 2019 at 9:50 AM Murtuza Boxwala 
>> wrote:
>> 
>>> 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
>>> <
>>> 
>> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK11/builds/948
 
>>> 
>>> If we don’t have any other ideas, though, it might be worth removing
>> them.
>>> 
>>> It is odd that you don’t see them locally. Let me see if I can get them
>> to
>>> show up…it might have something to do with the logging level.
>>> 
 On Aug 7, 2019, at 12:45 PM, Kirk Lund  wrote:
 
 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 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 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 haven't hit this yet, but maybe we
>> should consider disabling all PowerMock tests and increase priority
>> on
>> re-enabling them without PowerMock?
>> 
>>> Task :geode-assembly:test
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by
>> org.mockito.internal.util.reflection.AccessibilityChanger
>> 
> 
>>> 
>> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
>> to field java.io.File.path
>> WARNING: Please consider reporting this to the maintainers of
>> org.mockito.internal.util.reflection.AccessibilityChanger
>> WARNING: Use --illegal-access=warn to enable warnings of further
>>> illegal
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future
>>> release
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by
>> org.mockito.internal.util.reflection.AccessibilityChanger
>> 
> 
>>> 
>> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
>> to field java.io.File.path
>> WARNING: Please consider reporting this to the maintainers of
>> org.mockito.internal.util.reflection.AccessibilityChanger
>> WARNING: Use --illegal-access=warn to enable warnings of further
>>> illegal
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future
>>> release
>> 
>>> Task :geode-core:test
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by
>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
>> (file:/home/geode/geode/geode-core/build/classes/java/main/) to
>> method
>> java.lang.ThreadLocal.getMap(java.lang.Thread)
>> WARNING: Please consider reporting this to the maintainers of
>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
>> WARNING: Use --illegal-access=warn to enable warnings of further
>>> illegal
>> reflective access operations
>> WARNING: All illegal access operations will be denied in a future
>>> release
>> WARNING: An illegal reflective access operation has occurred
>> WARNING: Illegal reflective access by
>> org.mockito.internal.util.reflection.AccessibilityChanger
>> 
> 
>>> 
>> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
>> to field 

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

[Robert Houghton]

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 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?

[Helena Bales]

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://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 tests.
>
> On Wed, Aug 7, 2019 at 9:50 AM Murtuza Boxwala 
> wrote:
>
> > 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
> > <
> >
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK11/builds/948
> > >
> >
> > If we don’t have any other ideas, though, it might be worth removing
> them.
> >
> > It is odd that you don’t see them locally. Let me see if I can get them
> to
> > show up…it might have something to do with the logging level.
> >
> > > On Aug 7, 2019, at 12:45 PM, Kirk Lund  wrote:
> > >
> > > 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 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 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 haven't hit this yet, but maybe we
> > >>> should consider disabling all PowerMock tests and increase priority
> on
> > >>> re-enabling them without PowerMock?
> > >>>
> >  Task :geode-assembly:test
> > >>> WARNING: An illegal reflective access operation has occurred
> > >>> WARNING: Illegal reflective access by
> > >>> org.mockito.internal.util.reflection.AccessibilityChanger
> > >>>
> > >>
> >
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> > >>> to field java.io.File.path
> > >>> WARNING: Please consider reporting this to the maintainers of
> > >>> org.mockito.internal.util.reflection.AccessibilityChanger
> > >>> WARNING: Use --illegal-access=warn to enable warnings of further
> > illegal
> > >>> reflective access operations
> > >>> WARNING: All illegal access operations will be denied in a future
> > release
> > >>> WARNING: An illegal reflective access operation has occurred
> > >>> WARNING: Illegal reflective access by
> > >>> org.mockito.internal.util.reflection.AccessibilityChanger
> > >>>
> > >>
> >
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> > >>> to field java.io.File.path
> > >>> WARNING: Please consider reporting this to the maintainers of
> > >>> org.mockito.internal.util.reflection.AccessibilityChanger
> > >>> WARNING: Use --illegal-access=warn to enable warnings of further
> > illegal
> > >>> reflective access operations
> > >>> WARNING: All illegal access operations will be denied in a future
> > release
> > >>>
> >  Task :geode-core:test
> > >>> WARNING: An illegal reflective access operation has occurred
> > >>> WARNING: Illegal reflective access by
> > >>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> > >>> (file:/home/geode/geode/geode-core/build/classes/java/main/) to
> method
> > >>> java.lang.ThreadLocal.getMap(java.lang.Thread)
> > >>> WARNING: Please consider reporting this to the maintainers of
> > >>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> > >>> WARNING: Use --illegal-access=warn to enable warnings of further
> > illegal
> > >>> reflective access operations
> > >>> WARNING: All illegal access operations will be denied in a future
> > release
> > >>> WARNING: An illegal reflective access operation has occurred
> > >>> WARNING: Illegal reflective access by
> > >>> org.mockito.internal.util.reflection.AccessibilityChanger
> > >>>
> > >>
> >
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> > >>> to field java.util.Date.fastTime
> > >>> WARNING: Please consider reporting this to the maintainers of
> > >>> 

./gradlew test no longer runs/reruns tests?

[Kirk Lund]

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?

[Kirk Lund]

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 tests.

On Wed, Aug 7, 2019 at 9:50 AM Murtuza Boxwala  wrote:

> 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
> <
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK11/builds/948
> >
>
> If we don’t have any other ideas, though, it might be worth removing them.
>
> It is odd that you don’t see them locally. Let me see if I can get them to
> show up…it might have something to do with the logging level.
>
> > On Aug 7, 2019, at 12:45 PM, Kirk Lund  wrote:
> >
> > 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 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 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 haven't hit this yet, but maybe we
> >>> should consider disabling all PowerMock tests and increase priority on
> >>> re-enabling them without PowerMock?
> >>>
>  Task :geode-assembly:test
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>>
> >>
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> >>> to field java.io.File.path
> >>> WARNING: Please consider reporting this to the maintainers of
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>> WARNING: Use --illegal-access=warn to enable warnings of further
> illegal
> >>> reflective access operations
> >>> WARNING: All illegal access operations will be denied in a future
> release
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>>
> >>
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> >>> to field java.io.File.path
> >>> WARNING: Please consider reporting this to the maintainers of
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>> WARNING: Use --illegal-access=warn to enable warnings of further
> illegal
> >>> reflective access operations
> >>> WARNING: All illegal access operations will be denied in a future
> release
> >>>
>  Task :geode-core:test
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> >>> (file:/home/geode/geode/geode-core/build/classes/java/main/) to method
> >>> java.lang.ThreadLocal.getMap(java.lang.Thread)
> >>> WARNING: Please consider reporting this to the maintainers of
> >>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> >>> WARNING: Use --illegal-access=warn to enable warnings of further
> illegal
> >>> reflective access operations
> >>> WARNING: All illegal access operations will be denied in a future
> release
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>>
> >>
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> >>> to field java.util.Date.fastTime
> >>> WARNING: Please consider reporting this to the maintainers of
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>> WARNING: Use --illegal-access=warn to enable warnings of further
> illegal
> >>> reflective access operations
> >>> WARNING: All illegal access operations will be denied in a future
> release
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> 

Re: Unit tests are hanging?

[Helena Bales]

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 pipeline?

On Wed, Aug 7, 2019 at 9:50 AM Murtuza Boxwala  wrote:

> 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
> <
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UnitTestOpenJDK11/builds/948
> >
>
> If we don’t have any other ideas, though, it might be worth removing them.
>
> It is odd that you don’t see them locally. Let me see if I can get them to
> show up…it might have something to do with the logging level.
>
> > On Aug 7, 2019, at 12:45 PM, Kirk Lund  wrote:
> >
> > 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 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 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 haven't hit this yet, but maybe we
> >>> should consider disabling all PowerMock tests and increase priority on
> >>> re-enabling them without PowerMock?
> >>>
>  Task :geode-assembly:test
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>>
> >>
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> >>> to field java.io.File.path
> >>> WARNING: Please consider reporting this to the maintainers of
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>> WARNING: Use --illegal-access=warn to enable warnings of further
> illegal
> >>> reflective access operations
> >>> WARNING: All illegal access operations will be denied in a future
> release
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>>
> >>
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> >>> to field java.io.File.path
> >>> WARNING: Please consider reporting this to the maintainers of
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>> WARNING: Use --illegal-access=warn to enable warnings of further
> illegal
> >>> reflective access operations
> >>> WARNING: All illegal access operations will be denied in a future
> release
> >>>
>  Task :geode-core:test
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> >>> (file:/home/geode/geode/geode-core/build/classes/java/main/) to method
> >>> java.lang.ThreadLocal.getMap(java.lang.Thread)
> >>> WARNING: Please consider reporting this to the maintainers of
> >>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> >>> WARNING: Use --illegal-access=warn to enable warnings of further
> illegal
> >>> reflective access operations
> >>> WARNING: All illegal access operations will be denied in a future
> release
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>>
> >>
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> >>> to field java.util.Date.fastTime
> >>> WARNING: Please consider reporting this to the maintainers of
> >>> org.mockito.internal.util.reflection.AccessibilityChanger
> >>> WARNING: Use --illegal-access=warn to enable warnings of further
> illegal
> >>> reflective access operations
> >>> WARNING: All illegal access operations will be denied in a future
> release
> >>> WARNING: An illegal reflective access operation has occurred
> >>> WARNING: Illegal reflective access by
> >>> 

Re: Unit tests are hanging?

[Murtuza Boxwala]

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
 


If we don’t have any other ideas, though, it might be worth removing them.

It is odd that you don’t see them locally. Let me see if I can get them to show 
up…it might have something to do with the logging level.

> On Aug 7, 2019, at 12:45 PM, Kirk Lund  wrote:
> 
> 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 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 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 haven't hit this yet, but maybe we
>>> should consider disabling all PowerMock tests and increase priority on
>>> re-enabling them without PowerMock?
>>> 
 Task :geode-assembly:test
>>> WARNING: An illegal reflective access operation has occurred
>>> WARNING: Illegal reflective access by
>>> org.mockito.internal.util.reflection.AccessibilityChanger
>>> 
>> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
>>> to field java.io.File.path
>>> WARNING: Please consider reporting this to the maintainers of
>>> org.mockito.internal.util.reflection.AccessibilityChanger
>>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>>> reflective access operations
>>> WARNING: All illegal access operations will be denied in a future release
>>> WARNING: An illegal reflective access operation has occurred
>>> WARNING: Illegal reflective access by
>>> org.mockito.internal.util.reflection.AccessibilityChanger
>>> 
>> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
>>> to field java.io.File.path
>>> WARNING: Please consider reporting this to the maintainers of
>>> org.mockito.internal.util.reflection.AccessibilityChanger
>>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>>> reflective access operations
>>> WARNING: All illegal access operations will be denied in a future release
>>> 
 Task :geode-core:test
>>> WARNING: An illegal reflective access operation has occurred
>>> WARNING: Illegal reflective access by
>>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
>>> (file:/home/geode/geode/geode-core/build/classes/java/main/) to method
>>> java.lang.ThreadLocal.getMap(java.lang.Thread)
>>> WARNING: Please consider reporting this to the maintainers of
>>> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
>>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>>> reflective access operations
>>> WARNING: All illegal access operations will be denied in a future release
>>> WARNING: An illegal reflective access operation has occurred
>>> WARNING: Illegal reflective access by
>>> org.mockito.internal.util.reflection.AccessibilityChanger
>>> 
>> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
>>> to field java.util.Date.fastTime
>>> WARNING: Please consider reporting this to the maintainers of
>>> org.mockito.internal.util.reflection.AccessibilityChanger
>>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>>> reflective access operations
>>> WARNING: All illegal access operations will be denied in a future release
>>> WARNING: An illegal reflective access operation has occurred
>>> WARNING: Illegal reflective access by
>>> org.powermock.reflect.internal.WhiteboxImpl
>>> 
>> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.powermock/powermock-reflect/2.0.0-beta.5/4ea415348f15620783a1f26343d6732adfa86bc8/powermock-reflect-2.0.0-beta.5.jar)
>>> to method java.lang.Object.finalize()
>>> WARNING: Please consider reporting this to the maintainers of
>>> org.powermock.reflect.internal.WhiteboxImpl
>>> WARNING: Use --illegal-access=warn to enable warnings of further illegal
>>> reflective access operations
>>> WARNING: All illegal access operations will be denied in a future release

Re: Unit tests are hanging?

[Kirk Lund]

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 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 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 haven't hit this yet, but maybe we
> > should consider disabling all PowerMock tests and increase priority on
> > re-enabling them without PowerMock?
> >
> >> Task :geode-assembly:test
> > WARNING: An illegal reflective access operation has occurred
> > WARNING: Illegal reflective access by
> > org.mockito.internal.util.reflection.AccessibilityChanger
> >
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> > to field java.io.File.path
> > WARNING: Please consider reporting this to the maintainers of
> > org.mockito.internal.util.reflection.AccessibilityChanger
> > WARNING: Use --illegal-access=warn to enable warnings of further illegal
> > reflective access operations
> > WARNING: All illegal access operations will be denied in a future release
> > WARNING: An illegal reflective access operation has occurred
> > WARNING: Illegal reflective access by
> > org.mockito.internal.util.reflection.AccessibilityChanger
> >
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> > to field java.io.File.path
> > WARNING: Please consider reporting this to the maintainers of
> > org.mockito.internal.util.reflection.AccessibilityChanger
> > WARNING: Use --illegal-access=warn to enable warnings of further illegal
> > reflective access operations
> > WARNING: All illegal access operations will be denied in a future release
> >
> >> Task :geode-core:test
> > WARNING: An illegal reflective access operation has occurred
> > WARNING: Illegal reflective access by
> > org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> > (file:/home/geode/geode/geode-core/build/classes/java/main/) to method
> > java.lang.ThreadLocal.getMap(java.lang.Thread)
> > WARNING: Please consider reporting this to the maintainers of
> > org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> > WARNING: Use --illegal-access=warn to enable warnings of further illegal
> > reflective access operations
> > WARNING: All illegal access operations will be denied in a future release
> > WARNING: An illegal reflective access operation has occurred
> > WARNING: Illegal reflective access by
> > org.mockito.internal.util.reflection.AccessibilityChanger
> >
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> > to field java.util.Date.fastTime
> > WARNING: Please consider reporting this to the maintainers of
> > org.mockito.internal.util.reflection.AccessibilityChanger
> > WARNING: Use --illegal-access=warn to enable warnings of further illegal
> > reflective access operations
> > WARNING: All illegal access operations will be denied in a future release
> > WARNING: An illegal reflective access operation has occurred
> > WARNING: Illegal reflective access by
> > org.powermock.reflect.internal.WhiteboxImpl
> >
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.powermock/powermock-reflect/2.0.0-beta.5/4ea415348f15620783a1f26343d6732adfa86bc8/powermock-reflect-2.0.0-beta.5.jar)
> > to method java.lang.Object.finalize()
> > WARNING: Please consider reporting this to the maintainers of
> > org.powermock.reflect.internal.WhiteboxImpl
> > WARNING: Use --illegal-access=warn to enable warnings of further illegal
> > reflective access operations
> > WARNING: All illegal access operations will be denied in a future release
> > WARNING: An illegal reflective access operation has occurred
> > WARNING: Illegal reflective access by
> > org.junit.contrib.java.lang.system.EnvironmentVariables
> >
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/com.github.stefanbirkner/system-rules/1.19.0/d541c9a1cff0dda32e2436c74562e2e4aa6c88cd/system-rules-1.19.0.jar)
> > to field java.util.Collections$UnmodifiableMap.m
> > WARNING: Please consider reporting this to the maintainers of
> > org.junit.contrib.java.lang.system.EnvironmentVariables
> > WARNING: Use --illegal-access=warn to enable warnings of further illegal
> > reflective access operations
> > WARNING: All illegal 

Re: Unit tests are hanging?

[Murtuza Boxwala]

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 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 haven't hit this yet, but maybe we
> should consider disabling all PowerMock tests and increase priority on
> re-enabling them without PowerMock?
> 
>> Task :geode-assembly:test
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.mockito.internal.util.reflection.AccessibilityChanger
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> to field java.io.File.path
> WARNING: Please consider reporting this to the maintainers of
> org.mockito.internal.util.reflection.AccessibilityChanger
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.mockito.internal.util.reflection.AccessibilityChanger
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> to field java.io.File.path
> WARNING: Please consider reporting this to the maintainers of
> org.mockito.internal.util.reflection.AccessibilityChanger
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 
>> Task :geode-core:test
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> (file:/home/geode/geode/geode-core/build/classes/java/main/) to method
> java.lang.ThreadLocal.getMap(java.lang.Thread)
> WARNING: Please consider reporting this to the maintainers of
> org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.mockito.internal.util.reflection.AccessibilityChanger
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
> to field java.util.Date.fastTime
> WARNING: Please consider reporting this to the maintainers of
> org.mockito.internal.util.reflection.AccessibilityChanger
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.powermock.reflect.internal.WhiteboxImpl
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/org.powermock/powermock-reflect/2.0.0-beta.5/4ea415348f15620783a1f26343d6732adfa86bc8/powermock-reflect-2.0.0-beta.5.jar)
> to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of
> org.powermock.reflect.internal.WhiteboxImpl
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.junit.contrib.java.lang.system.EnvironmentVariables
> (file:/home/geode/.gradle/caches/modules-2/files-2.1/com.github.stefanbirkner/system-rules/1.19.0/d541c9a1cff0dda32e2436c74562e2e4aa6c88cd/system-rules-1.19.0.jar)
> to field java.util.Collections$UnmodifiableMap.m
> WARNING: Please consider reporting this to the maintainers of
> org.junit.contrib.java.lang.system.EnvironmentVariables
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 
> timeout exceeded

Unit tests are hanging?

[Kirk Lund]

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 haven't hit this yet, but maybe we
should consider disabling all PowerMock tests and increase priority on
re-enabling them without PowerMock?

> Task :geode-assembly:test
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.mockito.internal.util.reflection.AccessibilityChanger
(file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
to field java.io.File.path
WARNING: Please consider reporting this to the maintainers of
org.mockito.internal.util.reflection.AccessibilityChanger
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.mockito.internal.util.reflection.AccessibilityChanger
(file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
to field java.io.File.path
WARNING: Please consider reporting this to the maintainers of
org.mockito.internal.util.reflection.AccessibilityChanger
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release

> Task :geode-core:test
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
(file:/home/geode/geode/geode-core/build/classes/java/main/) to method
java.lang.ThreadLocal.getMap(java.lang.Thread)
WARNING: Please consider reporting this to the maintainers of
org.apache.geode.distributed.internal.deadlock.UnsafeThreadLocal
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.mockito.internal.util.reflection.AccessibilityChanger
(file:/home/geode/.gradle/caches/modules-2/files-2.1/org.mockito/mockito-core/2.23.0/497ddb32fd5d01f9dbe99a2ec790aeb931dff1b1/mockito-core-2.23.0.jar)
to field java.util.Date.fastTime
WARNING: Please consider reporting this to the maintainers of
org.mockito.internal.util.reflection.AccessibilityChanger
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.powermock.reflect.internal.WhiteboxImpl
(file:/home/geode/.gradle/caches/modules-2/files-2.1/org.powermock/powermock-reflect/2.0.0-beta.5/4ea415348f15620783a1f26343d6732adfa86bc8/powermock-reflect-2.0.0-beta.5.jar)
to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of
org.powermock.reflect.internal.WhiteboxImpl
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.junit.contrib.java.lang.system.EnvironmentVariables
(file:/home/geode/.gradle/caches/modules-2/files-2.1/com.github.stefanbirkner/system-rules/1.19.0/d541c9a1cff0dda32e2436c74562e2e4aa6c88cd/system-rules-1.19.0.jar)
to field java.util.Collections$UnmodifiableMap.m
WARNING: Please consider reporting this to the maintainers of
org.junit.contrib.java.lang.system.EnvironmentVariables
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release

timeout exceeded

Re: Travis-ci & geode-native repo

[Jacob Barrett]

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 pipeline as the java 
sources and do binary releases. If you would like to pick up that task it would 
allow you to run a full CI of your own too.

-jake



> On Aug 7, 2019, at 7:42 AM, Alberto Bustamante Reyes 
>  wrote:
> 
> 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 see in the travis.yaml any configuration about timeouts and I cannot 
> find any option to change that in Travis page. Could it be that geode-native 
> repo is not using the free version of Travis so it has a longer timeout? I 
> have seen that tasks takes aprox 1 hour and a half.
> 
> Thanks!
> 
> Alberto B.

Travis-ci & geode-native repo

[Alberto Bustamante Reyes]

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 see in the travis.yaml any configuration about timeouts and I cannot 
find any option to change that in Travis page. Could it be that geode-native 
repo is not using the free version of Travis so it has a longer timeout? I have 
seen that tasks takes aprox 1 hour and a half.

Thanks!

Alberto B.

Re: edit permissions on wiki

[Joris Melchior]

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!
> > >
> > > On Fri, Aug 2, 2019 at 12:16 PM Kirk Lund  wrote:
> > >
> > >> You should have permission now. Thanks!
> > >>
> > >> On Fri, Aug 2, 2019 at 7:32 AM Joris Melchior 
> > >> wrote:
> > >>
> > >> > Hi,
> > >> >
> > >> > Can someone provide me with edit permissions on the wiki?
> Specifically
> > >> the
> > >> > tree starting with this link
> > >> >
> > >> >
> > >>
> >
> https://cwiki.apache.org/confluence/display/GEODE/Cluster+Management+Service
> > >> >
> > >> > My user name is 'joris.melchior'.
> > >> >
> > >> > Thanks,
> > >> >
> > >> > --
> > >> > *Joris Melchior *
> > >> > CF Engineering
> > >> > Pivotal Toronto
> > >> > 416 877 5427
> > >> >
> > >> > “Programs must be written for people to read, and only incidentally
> > for
> > >> > machines to execute.” – *Hal Abelson*
> > >> > 
> > >> >
> > >>
> > >
> > >
> > > --
> > > *Joris Melchior *
> > > CF Engineering
> > > Pivotal Toronto
> > > 416 877 5427
> > >
> > > “Programs must be written for people to read, and only incidentally for
> > > machines to execute.” – *Hal Abelson*
> > > 
> > >
> >
> >
> > --
> > *Joris Melchior *
> > CF Engineering
> > Pivotal Toronto
> > 416 877 5427
> >
> > “Programs must be written for people to read, and only incidentally for
> > machines to execute.” – *Hal Abelson*
> > 
> >
>


-- 
*Joris Melchior *
CF Engineering
Pivotal Toronto
416 877 5427

“Programs must be written for people to read, and only incidentally for
machines to execute.” – *Hal Abelson*