[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly
[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436594#comment-17436594 ] Geode Integration commented on GEODE-8644: -- Seen in [distributed-test-openjdk8 #2407|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2407] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0632/test-results/distributedTest/1635581264/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0632/test-artifacts/1635581264/distributedtestfiles-openjdk8-1.15.0-build.0632.tgz]. > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > intermittently fails when queues drain too slowly > --- > > Key: GEODE-8644 > URL: https://issues.apache.org/jira/browse/GEODE-8644 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > Labels: pull-request-available > > Currently the test > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > relies on a 2 second delay to allow for queues to finish draining after > finishing the put operation. If queues take longer than 2 seconds to drain > the test will fail. We should change the test to wait for the queues to be > empty with a long timeout in case the queues never fully drain. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-8644) SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() intermittently fails when queues drain too slowly
[ https://issues.apache.org/jira/browse/GEODE-8644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436595#comment-17436595 ] Geode Integration commented on GEODE-8644: -- Seen in [distributed-test-openjdk8 #2408|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2408] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0632/test-results/distributedTest/1635581764/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0632/test-artifacts/1635581764/distributedtestfiles-openjdk8-1.15.0-build.0632.tgz]. > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > intermittently fails when queues drain too slowly > --- > > Key: GEODE-8644 > URL: https://issues.apache.org/jira/browse/GEODE-8644 > Project: Geode > Issue Type: Bug >Affects Versions: 1.15.0 >Reporter: Benjamin P Ross >Assignee: Benjamin P Ross >Priority: Major > Labels: pull-request-available > > Currently the test > SerialGatewaySenderQueueDUnitTest.unprocessedTokensMapShouldDrainCompletely() > relies on a 2 second delay to allow for queues to finish draining after > finishing the put operation. If queues take longer than 2 seconds to drain > the test will fail. We should change the test to wait for the queues to be > empty with a long timeout in case the queues never fully drain. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7474) NetSearchMessagingDUnitTest.testNetSearchFailoverFromReplicate
[
https://issues.apache.org/jira/browse/GEODE-7474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436597#comment-17436597
]
Geode Integration commented on GEODE-7474:
--
Seen in [distributed-test-openjdk8
#2496|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/distributed-test-openjdk8/builds/2496]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0632/test-results/distributedTest/1635659058/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-mass-test-run/1.15.0-build.0632/test-artifacts/1635659058/distributedtestfiles-openjdk8-1.15.0-build.0632.tgz].
> NetSearchMessagingDUnitTest.testNetSearchFailoverFromReplicate
> --
>
> Key: GEODE-7474
> URL: https://issues.apache.org/jira/browse/GEODE-7474
> Project: Geode
> Issue Type: Bug
> Components: tests
>Affects Versions: 1.11.0
>Reporter: Mark Hanson
>Assignee: Mark Hanson
>Priority: Major
> Labels: flaky
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/mhansonp-mhanson-mass-test-ru-main/jobs/DistributedTestOpenJDK8/builds/1665]
>
> {noformat}
> org.apache.geode.internal.cache.NetSearchMessagingDUnitTest >
> testNetSearchFailoverFromReplicate FAILED
> 19:13:08java.lang.AssertionError: Suspicious strings were written to the
> log during this run.
> 19:13:08Fix the strings or use IgnoredException.addIgnoredException to
> ignore.
> 19:13:08
> ---
> 19:13:08Found suspect string in log4j at line 2385
> 19:13:08
> 19:13:08[fatal 2019/11/18 03:13:06.977 GMT thread 2> tid=207] Uncaught exception in thread Thread[Geode Failure
> Detection thread 2,5,RMI Runtime]
> 19:13:08java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor$$Lambda$226/1317859019@1274aba9
> rejected from java.util.concurrent.ThreadPoolExecutor@100274c7[Shutting
> down, pool size = 3, active threads = 3, queued tasks = 0, completed tasks =
> 7]
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:1295)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.processMessage(GMSHealthMonitor.java:1232)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.sendSuspectRequest(GMSHealthMonitor.java:1478)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.initiateSuspicion(GMSHealthMonitor.java:477)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.lambda$checkMember$0(GMSHealthMonitor.java:461)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> 19:13:08 at java.lang.Thread.run(Thread.java:748)
> 19:13:08
> 19:13:08
> ---
> 19:13:08Found suspect string in log4j at line 2399
> 19:13:08
> 19:13:08[fatal 2019/11/18 03:13:06.976 GMT thread 4> tid=226] Uncaught exception in thread Thread[Geode Failure
> Detection thread 4,5,RMI Runtime]
> 19:13:08java.util.concurrent.RejectedExecutionException: Task
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor$$Lambda$226/1317859019@143de298
> rejected from java.util.concurrent.ThreadPoolExecutor@100274c7[Shutting
> down, pool size = 3, active threads = 3, queued tasks = 0, completed tasks =
> 7]
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
> 19:13:08 at
> java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.checkIfAvailable(GMSHealthMonitor.java:1295)
> 19:13:08 at
> org.apache.geode.distributed.internal.membership.gms.fd.GMSHealthMonitor.processMessage(GMSHealthMonitor.java:1232)
> 19:13:08 at
> org.apach
[jira] [Commented] (GEODE-9741) Add Latest Toolchain (v142) to Visual Studio 2019 CI Pipeline
[ https://issues.apache.org/jira/browse/GEODE-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436633#comment-17436633 ] ASF GitHub Bot commented on GEODE-9741: --- mmartell opened a new pull request #888: URL: https://github.com/apache/geode-native/pull/888 Building with the new tools (v142) on Windows caused the Release build to fail due to ACE not picking up the specified tools from the cmake configuration. This PR solves this problem by setting environment variables by calling vcvarsall.bat with the correct tools version before configuring with cmake. Note: Once geode-native is no longer dependent on ACE, the call to vcvarsall.bat can be removed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add Latest Toolchain (v142) to Visual Studio 2019 CI Pipeline > - > > Key: GEODE-9741 > URL: https://issues.apache.org/jira/browse/GEODE-9741 > Project: Geode > Issue Type: New Feature > Components: native client >Reporter: Michael Martell >Priority: Major > Labels: pull-request-available > > Currently the VS 2019 builds use the old toolchain (v141). All tests pass > with v142, so just requires a small change to CI code, as well as adding the > v142 tools to the Windows images. -- This message was sent by Atlassian Jira (v8.3.4#803005)
