[jira] [Commented] (GEODE-7916) Use modern Gradle syntax for build plugins
[
https://issues.apache.org/jira/browse/GEODE-7916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068363#comment-17068363
]
ASF subversion and git services commented on GEODE-7916:
Commit 2c26de89f1c78ddaab01531843826498b87f9eea in geode's branch
refs/heads/develop from Robert Houghton
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=2c26de8 ]
GEODE-7916: use updated gradle plugin declarations (#4856)
Also rev the versions of those plugins.
> Use modern Gradle syntax for build plugins
> --
>
> Key: GEODE-7916
> URL: https://issues.apache.org/jira/browse/GEODE-7916
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Robert Houghton
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Gradle best practices dictate to use {noformat}plugins {} {noformat} instead
> of {noformat}buildScript {}{noformat} to declare what plugins are required to
> build with Gradle.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7917) Problem forming SSL connection in multisite setup
[ https://issues.apache.org/jira/browse/GEODE-7917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Ivanac reassigned GEODE-7917: --- Assignee: Mario Ivanac > Problem forming SSL connection in multisite setup > - > > Key: GEODE-7917 > URL: https://issues.apache.org/jira/browse/GEODE-7917 > Project: Geode > Issue Type: Bug > Components: wan >Reporter: Mario Ivanac >Assignee: Mario Ivanac >Priority: Major > > We are installing two sites, with one locator in each site, and TLS enabled. > Problem appears when locators on both sides are started at same time. In that > case, on both locators, immediately after they are started, > IllegalStateException is caught, and connections are never reestablished. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7917) Problem forming SSL connection in multisite setup
Mario Ivanac created GEODE-7917: --- Summary: Problem forming SSL connection in multisite setup Key: GEODE-7917 URL: https://issues.apache.org/jira/browse/GEODE-7917 Project: Geode Issue Type: Bug Components: wan Reporter: Mario Ivanac We are installing two sites, with one locator in each site, and TLS enabled. Problem appears when locators on both sides are started at same time. In that case, on both locators, immediately after they are started, IllegalStateException is caught, and connections are never reestablished. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-6935) RegionExpirationIntegrationTest#increaseRegionTtl fails intermittently
[
https://issues.apache.org/jira/browse/GEODE-6935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans resolved GEODE-6935.
Resolution: Duplicate
> RegionExpirationIntegrationTest#increaseRegionTtl fails intermittently
> --
>
> Key: GEODE-6935
> URL: https://issues.apache.org/jira/browse/GEODE-6935
> Project: Geode
> Issue Type: Bug
>Reporter: Murtuza Boxwala
>Priority: Major
>
> The test relies on specific timings. If the AttributesMutator takes longer
> than expected, the region will be destroyed before its TTL is updated,
> resulting in the below:
> {code:java}
> org.apache.geode.cache.RegionExpirationIntegrationTest >
> increaseRegionTtl[NORMAL] FAILED
> java.lang.AssertionError:
> Expecting:
> <7L>
> to be greater than or equal to:
> <8L>
> at
> org.apache.geode.cache.RegionExpirationIntegrationTest.increaseRegionTtl(RegionExpirationIntegrationTest.java:88){code}
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK11/builds/104
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-6504) CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
[
https://issues.apache.org/jira/browse/GEODE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068838#comment-17068838
]
Donal Evans commented on GEODE-6504:
Reoccurred:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK8/builds/881
> CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
> -
>
> Key: GEODE-6504
> URL: https://issues.apache.org/jira/browse/GEODE-6504
> Project: Geode
> Issue Type: Bug
> Components: expiration
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Attachments: RegionExpirationIntegrationTest.log
>
>
> CI failure: see attached log.
>
> Failed on WindowsIntegrationTestOpenJDK11
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/272]
> {noformat}
> org.apache.geode.cache.RegionExpirationIntegrationTest >
> increaseRegionTtl[EMPTY] FAILED
> java.lang.AssertionError:
> Expecting:
> <7L>
> to be greater than or equal to:
> <8L>
> at
> org.apache.geode.cache.RegionExpirationIntegrationTest.increaseRegionTtl(RegionExpirationIntegrationTest.java:88)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7905) RedisDistDUnitTest failing intermittently in CI
[
https://issues.apache.org/jira/browse/GEODE-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068842#comment-17068842
]
Donal Evans commented on GEODE-7905:
Reoccurred:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1684
> RedisDistDUnitTest failing intermittently in CI
> ---
>
> Key: GEODE-7905
> URL: https://issues.apache.org/jira/browse/GEODE-7905
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Sarah Abbey
>Priority: Major
>
> Fix RedisDistDUnitTest, which fails intermittently:
> [https://concourse.apachegeode-ci.info/builds/141130]
>
> {code:java}
> org.apache.geode.redis.RedisDistDUnitTest > classMethod FAILED
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 5030
> [error 2020/03/23 19:26:51.559 GMT tid=99]
> org.apache.geode.ToDataException: toData failed on DataSerializer with id=0
> for class class java.util.HashSet
> 6 tests completed, 1 failed
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-7905) RedisDistDUnitTest failing intermittently in CI
[
https://issues.apache.org/jira/browse/GEODE-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donal Evans reassigned GEODE-7905:
--
Assignee: Raymond Ingles
> RedisDistDUnitTest failing intermittently in CI
> ---
>
> Key: GEODE-7905
> URL: https://issues.apache.org/jira/browse/GEODE-7905
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Sarah Abbey
>Assignee: Raymond Ingles
>Priority: Major
>
> Fix RedisDistDUnitTest, which fails intermittently:
> [https://concourse.apachegeode-ci.info/builds/141130]
>
> {code:java}
> org.apache.geode.redis.RedisDistDUnitTest > classMethod FAILED
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 5030
> [error 2020/03/23 19:26:51.559 GMT tid=99]
> org.apache.geode.ToDataException: toData failed on DataSerializer with id=0
> for class class java.util.HashSet
> 6 tests completed, 1 failed
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7905) RedisDistDUnitTest failing intermittently in CI
[
https://issues.apache.org/jira/browse/GEODE-7905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarah Abbey updated GEODE-7905:
---
Description:
Fix RedisDistDUnitTest, which fails intermittently:
[https://concourse.apachegeode-ci.info/builds/141130]
{code:java}
org.apache.geode.redis.RedisDistDUnitTest > classMethod FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 5030
[error 2020/03/23 19:26:51.559 GMT tid=99]
org.apache.geode.ToDataException: toData failed on DataSerializer with id=0 for
class class java.util.HashSet
6 tests completed, 1 failed
{code}
ASSIGNED TO: sabbey37 [Sarah Abbey] / ringles [Raymond Ingles]
(unfortunately we can't assign it to ourselves, though we've sent an email to :
[d...@geode.apache.org|mailto:d...@geode.apache.org] requesting access.
was:
Fix RedisDistDUnitTest, which fails intermittently:
[https://concourse.apachegeode-ci.info/builds/141130]
{code:java}
org.apache.geode.redis.RedisDistDUnitTest > classMethod FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use IgnoredException.addIgnoredException to ignore.
---
Found suspect string in log4j at line 5030
[error 2020/03/23 19:26:51.559 GMT tid=99]
org.apache.geode.ToDataException: toData failed on DataSerializer with id=0 for
class class java.util.HashSet
6 tests completed, 1 failed
{code}
> RedisDistDUnitTest failing intermittently in CI
> ---
>
> Key: GEODE-7905
> URL: https://issues.apache.org/jira/browse/GEODE-7905
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Sarah Abbey
>Assignee: Raymond Ingles
>Priority: Major
>
> Fix RedisDistDUnitTest, which fails intermittently:
> [https://concourse.apachegeode-ci.info/builds/141130]
>
> {code:java}
> org.apache.geode.redis.RedisDistDUnitTest > classMethod FAILED
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 5030
> [error 2020/03/23 19:26:51.559 GMT tid=99]
> org.apache.geode.ToDataException: toData failed on DataSerializer with id=0
> for class class java.util.HashSet
> 6 tests completed, 1 failed
> {code}
>
> ASSIGNED TO: sabbey37 [Sarah Abbey] / ringles [Raymond Ingles]
> (unfortunately we can't assign it to ourselves, though we've sent an email to
> : [d...@geode.apache.org|mailto:d...@geode.apache.org] requesting access.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7918) Improve error in geode-tcp-server under DNS hijacking (ISP) issues
Robert Houghton created GEODE-7918: -- Summary: Improve error in geode-tcp-server under DNS hijacking (ISP) issues Key: GEODE-7918 URL: https://issues.apache.org/jira/browse/GEODE-7918 Project: Geode Issue Type: Improvement Components: tests Reporter: Robert Houghton Testing Geode from home, my DNS from ISP was resolving things to a search engine causing test failures. Adds messaging to the tests that failed to give clues to future victims. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7919) Add additional integration tests to the geode-membership module
Dan Smith created GEODE-7919: Summary: Add additional integration tests to the geode-membership module Key: GEODE-7919 URL: https://issues.apache.org/jira/browse/GEODE-7919 Project: Geode Issue Type: Improvement Components: membership Reporter: Dan Smith We need some more integration tests of the membership module that test running multiple membership managers connecting to each other, using the membership api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7919) Add additional integration tests to the geode-membership module
[ https://issues.apache.org/jira/browse/GEODE-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith reassigned GEODE-7919: Assignee: Dan Smith > Add additional integration tests to the geode-membership module > --- > > Key: GEODE-7919 > URL: https://issues.apache.org/jira/browse/GEODE-7919 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > > We need some more integration tests of the membership module that test > running multiple membership managers connecting to each other, using the > membership api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7920) Geode UDP INT thread found processing cache operations
Bruce J Schuchardt created GEODE-7920:
-
Summary: Geode UDP INT thread found processing cache operations
Key: GEODE-7920
URL: https://issues.apache.org/jira/browse/GEODE-7920
Project: Geode
Issue Type: Improvement
Components: membership, messaging
Reporter: Bruce J Schuchardt
While looking into another problem in a test run with disable-tcp=true I found
this JGroups thread processing a cache operation in-line. These threads should
never process cache ops. They exist just to read messages and hand them off to
an Executor.
Fixing this should improve UDP messaging performance somewhat.
{noformat}
"Geode UDP INT-2,rs-Awesome-781-1145-1a0i32xlarge-hydra-client-4-27004" #54
daemon prio=5 os_prio=0 tid=0x7f202c05b800 nid=0x778d runnable
[0x7f20b0bb6000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:171)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)
at java.io.BufferedInputStream.read(BufferedInputStream.java:265)
- locked <0xc292f560> (a java.io.BufferedInputStream)
at java.io.DataInputStream.readByte(DataInputStream.java:265)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:240)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:163)
at
java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:235)
at
java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:180)
at com.sun.proxy.$Proxy53.increment(Unknown Source)
at
hydra.blackboard.AnySharedCountersImpl.increment(AnySharedCountersImpl.java:159)
at
util.AbstractListener.incrementAfterDestroyCounters(AbstractListener.java:450)
at event.ETListener.afterDestroy(ETListener.java:88)
at
org.apache.geode.internal.cache.EnumListenerEvent$AFTER_DESTROY.dispatchEvent(EnumListenerEvent.java:178)
at
org.apache.geode.internal.cache.LocalRegion.dispatchEvent(LocalRegion.java:8242)
at
org.apache.geode.internal.cache.LocalRegion.dispatchListenerEvent(LocalRegion.java:6952)
at
org.apache.geode.internal.cache.LocalRegion.invokeDestroyCallbacks(LocalRegion.java:6760)
at
org.apache.geode.internal.cache.EntryEventImpl.invokeCallbacks(EntryEventImpl.java:2443)
at
org.apache.geode.internal.cache.entries.AbstractRegionEntry.dispatchListenerEvents(AbstractRegionEntry.java:164)
at
org.apache.geode.internal.cache.LocalRegion.basicDestroyPart2(LocalRegion.java:6701)
at
org.apache.geode.internal.cache.map.RegionMapDestroy.removeEntryOrLeaveTombstone(RegionMapDestroy.java:509)
at
org.apache.geode.internal.cache.map.RegionMapDestroy.retryRemoveWithTombstone(RegionMapDestroy.java:373)
- locked <0xfe71d6e0> (a
org.apache.geode.internal.cache.entries.VersionedStatsRegionEntryOffHeapStringKey2)
at
org.apache.geode.internal.cache.map.RegionMapDestroy.checkTombstoneAndConcurrency(RegionMapDestroy.java:202)
at
org.apache.geode.internal.cache.map.RegionMapDestroy.destroy(RegionMapDestroy.java:147)
at
org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:980)
at
org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6490)
at
org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6464)
at
org.apache.geode.internal.cache.LocalRegionDataView.destroyExistingEntry(LocalRegionDataView.java:58)
at
org.apache.geode.internal.cache.LocalRegion.basicDestroy(LocalRegion.java:6415)
at
org.apache.geode.internal.cache.DistributedRegion.basicDestroy(DistributedRegion.java:1720)
at
org.apache.geode.internal.cache.DestroyOperation$DestroyMessage.operateOnRegion(DestroyOperation.java:88)
at
org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1208)
at
org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1110)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
at
org.apache.geode.distributed.internal.DistributionMessage.schedule(DistributionMessage.java:431)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.scheduleIncomingMessage(ClusterDistributionManager.java:2072)
at
org.apache.geode.distributed.internal.ClusterDistributionManager.handleIncomingDMsg(ClusterDistributionManager.java:1847)
[jira] [Created] (GEODE-7921) NullPointerExceptions logged during auto-reconnect
Bruce J Schuchardt created GEODE-7921:
-
Summary: NullPointerExceptions logged during auto-reconnect
Key: GEODE-7921
URL: https://issues.apache.org/jira/browse/GEODE-7921
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Bruce J Schuchardt
In a test with disable-tcp=true I found a huge number of NPEs logged when a
server auto-reconnected.
{noformat}
[fatal 2020/03/25 15:26:57.136 PDT tid=0x17f]
Uncaught exception processing LatestLastAccessTimeMessage@546d3459
processorId=0
sender=rs-FullRegression25213428a3i32xlarge-hydra-client-22(gemfire3_host1_32677:32677):41009
java.lang.NullPointerException
at
org.apache.geode.internal.cache.LatestLastAccessTimeMessage.process(LatestLastAccessTimeMessage.java:66)
at
org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
at
org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:440)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:442)
at
org.apache.geode.distributed.internal.ClusterOperationExecutors.doProcessingThread(ClusterOperationExecutors.java:389)
at
org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
at java.base/java.lang.Thread.run(Thread.java:834)
{noformat}
These came from a queue of messages built up by the QuorumChecker that were
processed before a new cache was built. The QuorumChecker shouldn't be
queueing cache operations. It only needs to queue membership messages.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7919) Move MembershipOnlyJunit test to the geode-membership module
[ https://issues.apache.org/jira/browse/GEODE-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-7919: - Summary: Move MembershipOnlyJunit test to the geode-membership module (was: Add additional integration tests to the geode-membership module) > Move MembershipOnlyJunit test to the geode-membership module > > > Key: GEODE-7919 > URL: https://issues.apache.org/jira/browse/GEODE-7919 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > > We need some more integration tests of the membership module that test > running multiple membership managers connecting to each other, using the > membership api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-7919) Move MembershipOnlyJunit test to the geode-membership module
[ https://issues.apache.org/jira/browse/GEODE-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-7919: - Description: Move the MembershipOnlyJunit test to the membership module and add more integration tests that test running multiple membership managers connecting to each other, using the membership api. (was: We need some more integration tests of the membership module that test running multiple membership managers connecting to each other, using the membership api.) > Move MembershipOnlyJunit test to the geode-membership module > > > Key: GEODE-7919 > URL: https://issues.apache.org/jira/browse/GEODE-7919 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > > Move the MembershipOnlyJunit test to the membership module and add more > integration tests that test running multiple membership managers connecting > to each other, using the membership api. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7922) Add concurrency tests to the geode-membership module
Dan Smith created GEODE-7922: Summary: Add concurrency tests to the geode-membership module Key: GEODE-7922 URL: https://issues.apache.org/jira/browse/GEODE-7922 Project: Geode Issue Type: Improvement Components: membership Reporter: Dan Smith Add tests to the geode-membership module that test the membership API in the face of concurrent operations - multiple members joining at the same time, etc. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-6504) CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
[
https://issues.apache.org/jira/browse/GEODE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069081#comment-17069081
]
Robert Houghton commented on GEODE-6504:
Again:
[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsCoreIntegrationTestOpenJDK8/builds/881]
with artifacts:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0124/test-results/integrationTest/1585306224/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Test report artifacts from this job are available at:
http://files.apachegeode-ci.info/builds/apache-develop-main/1.13.0-SNAPSHOT.0124/test-artifacts/1585306224/windows-coreintegrationtestfiles-OpenJDK8-1.13.0-SNAPSHOT.0124.tgz
> CI: RegionExpirationIntegrationTest > increaseRegionTtl[EMPTY] FAILED
> -
>
> Key: GEODE-6504
> URL: https://issues.apache.org/jira/browse/GEODE-6504
> Project: Geode
> Issue Type: Bug
> Components: expiration
>Reporter: Mark Hanson
>Assignee: Kirk Lund
>Priority: Major
> Attachments: RegionExpirationIntegrationTest.log
>
>
> CI failure: see attached log.
>
> Failed on WindowsIntegrationTestOpenJDK11
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/272]
> {noformat}
> org.apache.geode.cache.RegionExpirationIntegrationTest >
> increaseRegionTtl[EMPTY] FAILED
> java.lang.AssertionError:
> Expecting:
> <7L>
> to be greater than or equal to:
> <8L>
> at
> org.apache.geode.cache.RegionExpirationIntegrationTest.increaseRegionTtl(RegionExpirationIntegrationTest.java:88)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7787) GitHub token integration issue with rate-limit
[
https://issues.apache.org/jira/browse/GEODE-7787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069096#comment-17069096
]
Robert Houghton commented on GEODE-7787:
Opened a new issue
[INFRA-20042|https://issues.apache.org/jira/browse/INFRA-20042]
> GitHub token integration issue with rate-limit
> --
>
> Key: GEODE-7787
> URL: https://issues.apache.org/jira/browse/GEODE-7787
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Robert Houghton
>Priority: Major
>
> GitHub limits the API usage of the asf-ci account given to us by Apache.
> Attempted to rectify with ASF via GitHub rate limit increases in
> [INFRA-19731|https://issues.apache.org/jira/browse/INFRA-19731]
> {noformat}
> failed to set status: POST
> https://api.github.com/repos/apache/geode/statuses/123abc: 403 API rate limit
> exceeded for user ID 40367165. [rate reset in 3m42s]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7915) remove examples zip test from rc pipeline
[ https://issues.apache.org/jira/browse/GEODE-7915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069109#comment-17069109 ] ASF subversion and git services commented on GEODE-7915: Commit 80ffe65afeb84223faa75eebca77ad39e29f7f5a in geode's branch refs/heads/develop from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=80ffe65 ] GEODE-7915: rc pipeline fixes and improvements (#4853) * remove examples.zip test from pipeline as .zip is no longer produced * check all source artifacts to ensure they do not contain any binaries * check that no unexpected artifacts are present * align release retention with "N-2" proposal > remove examples zip test from rc pipeline > - > > Key: GEODE-7915 > URL: https://issues.apache.org/jira/browse/GEODE-7915 > Project: Geode > Issue Type: Improvement > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Now that .zip version of examples is no longer part of the release artifacts, > the rc pipeline no longer needs the `run-geode-examples-from-src-zip-11` job > (but does still need to test 11, so just change to use tgz) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7915) remove examples zip test from rc pipeline
[ https://issues.apache.org/jira/browse/GEODE-7915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Owen Nichols resolved GEODE-7915. - Fix Version/s: 1.13.0 Resolution: Fixed also fixed for 1.12 (merge not necessary as release manager will run the release scripts from develop) > remove examples zip test from rc pipeline > - > > Key: GEODE-7915 > URL: https://issues.apache.org/jira/browse/GEODE-7915 > Project: Geode > Issue Type: Improvement > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Now that .zip version of examples is no longer part of the release artifacts, > the rc pipeline no longer needs the `run-geode-examples-from-src-zip-11` job > (but does still need to test 11, so just change to use tgz) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7915) remove examples zip test from rc pipeline
[ https://issues.apache.org/jira/browse/GEODE-7915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069173#comment-17069173 ] ASF subversion and git services commented on GEODE-7915: Commit 6293da1b7280e6e8811403b871bcaa51b19b08cb in geode's branch refs/heads/release/1.12.0 from Owen Nichols [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6293da1 ] GEODE-7915: rc pipeline fixes and improvements (#4853) * remove examples.zip test from pipeline as .zip is no longer produced * check all source artifacts to ensure they do not contain any binaries * check that no unexpected artifacts are present * align release retention with "N-2" proposal (cherry picked from commit 80ffe65afeb84223faa75eebca77ad39e29f7f5a) > remove examples zip test from rc pipeline > - > > Key: GEODE-7915 > URL: https://issues.apache.org/jira/browse/GEODE-7915 > Project: Geode > Issue Type: Improvement > Components: release >Reporter: Owen Nichols >Assignee: Owen Nichols >Priority: Major > Fix For: 1.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Now that .zip version of examples is no longer part of the release artifacts, > the rc pipeline no longer needs the `run-geode-examples-from-src-zip-11` job > (but does still need to test 11, so just change to use tgz) -- This message was sent by Atlassian Jira (v8.3.4#803005)
