[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383943#comment-17383943
]
ASF GitHub Bot commented on GEODE-9431:
---
pivotal-jbarrett commented on a change in pull request #831:
URL: https://github.com/apache/geode-native/pull/831#discussion_r672432754
##
File path: cppcache/test/ByteArrayFixture.cpp
##
@@ -20,7 +20,7 @@
::testing::AssertionResult ByteArrayFixture::assertByteArrayEqual(
const char* /*expectedStr*/, const char* /*bytesStr*/, const char*
expected,
const apache::geode::client::ByteArray& bytes) {
- // One would normally just use std::regex but gcc 4.4.7 is lacking.
+ // One would normally just use boost::regex but gcc 4.4.7 is lacking.
Review comment:
How about just resolving the issue in the comment. We don't support GCC
4.4.7 anymore.
##
File path: cppcache/include/geode/CacheableString.hpp
##
@@ -54,11 +54,11 @@ class APACHE_GEODE_EXPORT CacheableString
: m_str(std::move(value)), m_hashcode(0) {
bool ascii = isAscii(m_str);
-m_type = m_str.length() > (std::numeric_limits::max)()
- ? ascii ? DSCode::CacheableASCIIStringHuge
- : DSCode::CacheableStringHuge
- : ascii ? DSCode::CacheableASCIIString
- : DSCode::CacheableString;
+m_type =
+m_str.length() > (std::numeric_limits::max)()
+? ascii ? DSCode::CacheableASCIIStringHuge
+: DSCode::CacheableStringHuge
+: ascii ? DSCode::CacheableASCIIString : DSCode::CacheableString;
Review comment:
Did you make these changes on Windows? The CI version and macOS version
seem to be in agreement.
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383974#comment-17383974
]
ASF GitHub Bot commented on GEODE-9431:
---
pivotal-jbarrett commented on pull request #831:
URL: https://github.com/apache/geode-native/pull/831#issuecomment-882667398
> > This seems like a really big hammer for what strikes me an issue with
maybe a specific RHEL C++ runtime patch or gcc patch. I didn't see any open
tickets with RHEL or GNU regarding these issues in the GEODE ticket. Given that
boost::regex is the basis for std::regex if we are using std::regex incorrectly
resulting in different undefined behavior in RHEL then I would be just as
concerned with our use of boost::regex.
>
> I spent most of last week picking up and discarding various "hammers" as
solutions to this problem - this was the first one that worked. Let me know
what mitigations you think we need for this, I'm fine with most things. If we
need/want a JIRA ticket to revert this back once it's fixed by RedHat or
whomever, that's fine. I would also argue it's not really _that_ big of a
hammer, since the change itself took about an hour to make and verify, and
backing it out is the work of a few minutes. I'll figure out how to file the
bug with RedHat and GNU today, but I don't think waiting for them to provide a
fix is a viable strategy. We need to get our CI pipeline off the floor so we
can proceed with dev work and know we're not further damaging the product on
RHEL-8.
As long as we can get issues opened with RH and and with ourselves to revert
back to `std::regex` once we or RH fixes the underlying issue, I could get on
board with this change.
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9430) Update Geode Session Management example
[ https://issues.apache.org/jira/browse/GEODE-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383965#comment-17383965 ] ASF GitHub Bot commented on GEODE-9430: --- davebarnes97 merged pull request #108: URL: https://github.com/apache/geode-examples/pull/108 -- 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 > Update Geode Session Management example > --- > > Key: GEODE-9430 > URL: https://issues.apache.org/jira/browse/GEODE-9430 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.13.4, 1.14.0, 1.15.0 > > > Issue GEODE-9426 included issues related to the user guide and a related > example. This tracks the fact that example needs updating. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383986#comment-17383986
]
ASF GitHub Bot commented on GEODE-9431:
---
pdxcodemonkey commented on pull request #831:
URL: https://github.com/apache/geode-native/pull/831#issuecomment-882661385
> This seems like a really big hammer for what strikes me an issue with
maybe a specific RHEL C++ runtime patch or gcc patch. I didn't see any open
tickets with RHEL or GNU regarding these issues in the GEODE ticket. Given that
boost::regex is the basis for std::regex if we are using std::regex incorrectly
resulting in different undefined behavior in RHEL then I would be just as
concerned with our use of boost::regex.
I spent most of last week picking up and discarding various "hammers" as
solutions to this problem - this was the first one that worked. Let me know
what mitigations you think we need for this, I'm fine with most things. If we
need/want a JIRA ticket to revert this back once it's fixed by RedHat or
whomever, that's fine. I would also argue it's not really _that_ big of a
hammer, since the change itself took about an hour to make and verify, and
backing it out is the work of a few minutes. I'll figure out how to file the
bug with RedHat and GNU today, but I don't think waiting for them to provide a
fix is a viable strategy. We need to get our CI pipeline off the floor so we
can proceed with dev work and know we're not further damaging the product on
RHEL-8.
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383989#comment-17383989
]
ASF GitHub Bot commented on GEODE-9431:
---
pdxcodemonkey commented on a change in pull request #831:
URL: https://github.com/apache/geode-native/pull/831#discussion_r672430467
##
File path: cppcache/include/geode/CacheableString.hpp
##
@@ -54,11 +54,11 @@ class APACHE_GEODE_EXPORT CacheableString
: m_str(std::move(value)), m_hashcode(0) {
bool ascii = isAscii(m_str);
-m_type = m_str.length() > (std::numeric_limits::max)()
- ? ascii ? DSCode::CacheableASCIIStringHuge
- : DSCode::CacheableStringHuge
- : ascii ? DSCode::CacheableASCIIString
- : DSCode::CacheableString;
+m_type =
+m_str.length() > (std::numeric_limits::max)()
+? ascii ? DSCode::CacheableASCIIStringHuge
+: DSCode::CacheableStringHuge
+: ascii ? DSCode::CacheableASCIIString : DSCode::CacheableString;
Review comment:
Fixed - just another artifact of the fact that the CI version of
clangformat is "special" :/
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9430) Update Geode Session Management example
[ https://issues.apache.org/jira/browse/GEODE-9430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384125#comment-17384125 ] ASF GitHub Bot commented on GEODE-9430: --- davebarnes97 merged pull request #108: URL: https://github.com/apache/geode-examples/pull/108 -- 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 > Update Geode Session Management example > --- > > Key: GEODE-9430 > URL: https://issues.apache.org/jira/browse/GEODE-9430 > Project: Geode > Issue Type: Bug > Components: examples >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.13.4, 1.14.0, 1.15.0 > > > Issue GEODE-9426 included issues related to the user guide and a related > example. This tracks the fact that example needs updating. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384135#comment-17384135
]
ASF GitHub Bot commented on GEODE-9431:
---
pivotal-jbarrett commented on pull request #831:
URL: https://github.com/apache/geode-native/pull/831#issuecomment-882667398
> > This seems like a really big hammer for what strikes me an issue with
maybe a specific RHEL C++ runtime patch or gcc patch. I didn't see any open
tickets with RHEL or GNU regarding these issues in the GEODE ticket. Given that
boost::regex is the basis for std::regex if we are using std::regex incorrectly
resulting in different undefined behavior in RHEL then I would be just as
concerned with our use of boost::regex.
>
> I spent most of last week picking up and discarding various "hammers" as
solutions to this problem - this was the first one that worked. Let me know
what mitigations you think we need for this, I'm fine with most things. If we
need/want a JIRA ticket to revert this back once it's fixed by RedHat or
whomever, that's fine. I would also argue it's not really _that_ big of a
hammer, since the change itself took about an hour to make and verify, and
backing it out is the work of a few minutes. I'll figure out how to file the
bug with RedHat and GNU today, but I don't think waiting for them to provide a
fix is a viable strategy. We need to get our CI pipeline off the floor so we
can proceed with dev work and know we're not further damaging the product on
RHEL-8.
As long as we can get issues opened with RH and and with ourselves to revert
back to `std::regex` once we or RH fixes the underlying issue, I could get on
board with this change.
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384147#comment-17384147
]
ASF GitHub Bot commented on GEODE-9431:
---
pdxcodemonkey commented on a change in pull request #831:
URL: https://github.com/apache/geode-native/pull/831#discussion_r672430467
##
File path: cppcache/include/geode/CacheableString.hpp
##
@@ -54,11 +54,11 @@ class APACHE_GEODE_EXPORT CacheableString
: m_str(std::move(value)), m_hashcode(0) {
bool ascii = isAscii(m_str);
-m_type = m_str.length() > (std::numeric_limits::max)()
- ? ascii ? DSCode::CacheableASCIIStringHuge
- : DSCode::CacheableStringHuge
- : ascii ? DSCode::CacheableASCIIString
- : DSCode::CacheableString;
+m_type =
+m_str.length() > (std::numeric_limits::max)()
+? ascii ? DSCode::CacheableASCIIStringHuge
+: DSCode::CacheableStringHuge
+: ascii ? DSCode::CacheableASCIIString : DSCode::CacheableString;
Review comment:
Fixed - just another artifact of the fact that the CI version of
clangformat is "special" :/
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384146#comment-17384146
]
ASF GitHub Bot commented on GEODE-9431:
---
pdxcodemonkey commented on pull request #831:
URL: https://github.com/apache/geode-native/pull/831#issuecomment-882661385
> This seems like a really big hammer for what strikes me an issue with
maybe a specific RHEL C++ runtime patch or gcc patch. I didn't see any open
tickets with RHEL or GNU regarding these issues in the GEODE ticket. Given that
boost::regex is the basis for std::regex if we are using std::regex incorrectly
resulting in different undefined behavior in RHEL then I would be just as
concerned with our use of boost::regex.
I spent most of last week picking up and discarding various "hammers" as
solutions to this problem - this was the first one that worked. Let me know
what mitigations you think we need for this, I'm fine with most things. If we
need/want a JIRA ticket to revert this back once it's fixed by RedHat or
whomever, that's fine. I would also argue it's not really _that_ big of a
hammer, since the change itself took about an hour to make and verify, and
backing it out is the work of a few minutes. I'll figure out how to file the
bug with RedHat and GNU today, but I don't think waiting for them to provide a
fix is a viable strategy. We need to get our CI pipeline off the floor so we
can proceed with dev work and know we're not further damaging the product on
RHEL-8.
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384168#comment-17384168
]
ASF GitHub Bot commented on GEODE-9431:
---
pivotal-jbarrett commented on a change in pull request #831:
URL: https://github.com/apache/geode-native/pull/831#discussion_r672432754
##
File path: cppcache/test/ByteArrayFixture.cpp
##
@@ -20,7 +20,7 @@
::testing::AssertionResult ByteArrayFixture::assertByteArrayEqual(
const char* /*expectedStr*/, const char* /*bytesStr*/, const char*
expected,
const apache::geode::client::ByteArray& bytes) {
- // One would normally just use std::regex but gcc 4.4.7 is lacking.
+ // One would normally just use boost::regex but gcc 4.4.7 is lacking.
Review comment:
How about just resolving the issue in the comment. We don't support GCC
4.4.7 anymore.
##
File path: cppcache/include/geode/CacheableString.hpp
##
@@ -54,11 +54,11 @@ class APACHE_GEODE_EXPORT CacheableString
: m_str(std::move(value)), m_hashcode(0) {
bool ascii = isAscii(m_str);
-m_type = m_str.length() > (std::numeric_limits::max)()
- ? ascii ? DSCode::CacheableASCIIStringHuge
- : DSCode::CacheableStringHuge
- : ascii ? DSCode::CacheableASCIIString
- : DSCode::CacheableString;
+m_type =
+m_str.length() > (std::numeric_limits::max)()
+? ascii ? DSCode::CacheableASCIIStringHuge
+: DSCode::CacheableStringHuge
+: ascii ? DSCode::CacheableASCIIString : DSCode::CacheableString;
Review comment:
Did you make these changes on Windows? The CI version and macOS version
seem to be in agreement.
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9070) CI Failure: ClientServerSessionCacheDUnitTest > addServerToExistingClusterCreatesSessionRegion
[
https://issues.apache.org/jira/browse/GEODE-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384289#comment-17384289
]
ASF subversion and git services commented on GEODE-9070:
Commit 400dee12fa2d35d59adb81655bf811898d311d6c in geode's branch
refs/heads/develop from Sarah
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=400dee1 ]
GEODE-9070: Improve ClientServerSessionCacheDUnitTest and add additional
logging (#6567)
> CI Failure: ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion
> --
>
> Key: GEODE-9070
> URL: https://issues.apache.org/jira/browse/GEODE-9070
> Project: Geode
> Issue Type: Bug
> Components: ci, http session
>Reporter: Jens Deppe
>Assignee: Benjamin P Ross
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion FAILED
> 00:47:45org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$84/1299235653.run
> in VM 1 running on Host 51208612ea94 with 4 VMs
> 00:47:45at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 00:47:45at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.addServerToExistingClusterCreatesSessionRegion(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[] within 5 minutes.
> 00:47:45at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:47:45at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:47:45at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$addServerToExistingClusterCreatesSessionRegion$bb17a952$1(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45java.lang.AssertionError:
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[]
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateServer(ClientServerSessionCacheDUnitTest.java:245)
> 00:47:53{noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161716/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161716/distributedtestfiles-OpenJDK8-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9439) Convert CertifacteBuilder to sun/jdk APIs
Jens Deppe created GEODE-9439:
-
Summary: Convert CertifacteBuilder to sun/jdk APIs
Key: GEODE-9439
URL: https://issues.apache.org/jira/browse/GEODE-9439
Project: Geode
Issue Type: Test
Components: tests
Reporter: Jens Deppe
The {{CertificateBuilder}} test utility uses Bouncy Castle APIs to build CA and
regular certs for test purposes. In some cases it is desirable for these
certificates to be serializable. In such cases it is also required that the BC
security provider have a higher priority than the standard java one otherwise
the deserialized certificates are not usable.
It would be less trouble to just use standard jdk APIs to build these
certificates. Although no {{X509}} APIs are public/documented they are well
used throughout the JDK. For example the {{keytool}} utility. Java 9 introduces
its own {{CertificateBuilder}} API which could eventually replace this one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9070) CI Failure: ClientServerSessionCacheDUnitTest > addServerToExistingClusterCreatesSessionRegion
[
https://issues.apache.org/jira/browse/GEODE-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarah Abbey reassigned GEODE-9070:
--
Assignee: Sarah Abbey (was: Benjamin P Ross)
> CI Failure: ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion
> --
>
> Key: GEODE-9070
> URL: https://issues.apache.org/jira/browse/GEODE-9070
> Project: Geode
> Issue Type: Bug
> Components: ci, http session
>Reporter: Jens Deppe
>Assignee: Sarah Abbey
>Priority: Major
> Labels: pull-request-available
>
> {noformat}
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion FAILED
> 00:47:45org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$84/1299235653.run
> in VM 1 running on Host 51208612ea94 with 4 VMs
> 00:47:45at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 00:47:45at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.addServerToExistingClusterCreatesSessionRegion(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[] within 5 minutes.
> 00:47:45at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:47:45at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:47:45at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$addServerToExistingClusterCreatesSessionRegion$bb17a952$1(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45java.lang.AssertionError:
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[]
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateServer(ClientServerSessionCacheDUnitTest.java:245)
> 00:47:53{noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161716/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161716/distributedtestfiles-OpenJDK8-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9439) Convert CertifacteBuilder to sun/jdk APIs
[
https://issues.apache.org/jira/browse/GEODE-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9439:
--
Labels: pull-request-available (was: )
> Convert CertifacteBuilder to sun/jdk APIs
> -
>
> Key: GEODE-9439
> URL: https://issues.apache.org/jira/browse/GEODE-9439
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> The {{CertificateBuilder}} test utility uses Bouncy Castle APIs to build CA
> and regular certs for test purposes. In some cases it is desirable for these
> certificates to be serializable. In such cases it is also required that the
> BC security provider have a higher priority than the standard java one
> otherwise the deserialized certificates are not usable.
> It would be less trouble to just use standard jdk APIs to build these
> certificates. Although no {{X509}} APIs are public/documented they are well
> used throughout the JDK. For example the {{keytool}} utility. Java 9
> introduces its own {{CertificateBuilder}} API which could eventually replace
> this one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-9070) CI Failure: ClientServerSessionCacheDUnitTest > addServerToExistingClusterCreatesSessionRegion
[
https://issues.apache.org/jira/browse/GEODE-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarah Abbey resolved GEODE-9070.
Fix Version/s: 1.15.0
Resolution: Fixed
This issue occurs when the function tries to execute on a member that has just
joined the cluster, but because the new view is not done processing by
membership, the member is considered shunned and nonexistent. Root issue
(GEODE-9350) was fixed and backported to 1.14.
Merged PR that adds tests improvements and debug logging to assist in
diagnosing the issue if it ever happens again.
> CI Failure: ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion
> --
>
> Key: GEODE-9070
> URL: https://issues.apache.org/jira/browse/GEODE-9070
> Project: Geode
> Issue Type: Bug
> Components: ci, http session
>Reporter: Jens Deppe
>Assignee: Sarah Abbey
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion FAILED
> 00:47:45org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$84/1299235653.run
> in VM 1 running on Host 51208612ea94 with 4 VMs
> 00:47:45at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 00:47:45at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.addServerToExistingClusterCreatesSessionRegion(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[] within 5 minutes.
> 00:47:45at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:47:45at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:47:45at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$addServerToExistingClusterCreatesSessionRegion$bb17a952$1(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45java.lang.AssertionError:
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[]
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateServer(ClientServerSessionCacheDUnitTest.java:245)
> 00:47:53{noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161716/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161716/distributedtestfiles-OpenJDK8-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9070) CI Failure: ClientServerSessionCacheDUnitTest > addServerToExistingClusterCreatesSessionRegion
[
https://issues.apache.org/jira/browse/GEODE-9070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sarah Abbey updated GEODE-9070:
---
Affects Version/s: 1.15.0
> CI Failure: ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion
> --
>
> Key: GEODE-9070
> URL: https://issues.apache.org/jira/browse/GEODE-9070
> Project: Geode
> Issue Type: Bug
> Components: ci, http session
>Affects Versions: 1.15.0
>Reporter: Jens Deppe
>Assignee: Sarah Abbey
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {noformat}
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest >
> addServerToExistingClusterCreatesSessionRegion FAILED
> 00:47:45org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest$$Lambda$84/1299235653.run
> in VM 1 running on Host 51208612ea94 with 4 VMs
> 00:47:45at
> org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:631)
> 00:47:45at org.apache.geode.test.dunit.VM.invoke(VM.java:448)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.addServerToExistingClusterCreatesSessionRegion(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45org.awaitility.core.ConditionTimeoutException: Assertion
> condition defined as a lambda expression in
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[] within 5 minutes.
> 00:47:45at
> org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:165)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
> 00:47:45at
> org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
> 00:47:45at
> org.awaitility.core.ConditionFactory.until(ConditionFactory.java:895)
> 00:47:45at
> org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:679)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.lambda$addServerToExistingClusterCreatesSessionRegion$bb17a952$1(ClientServerSessionCacheDUnitTest.java:100)
> 00:47:45
> 00:47:45Caused by:
> 00:47:45java.lang.AssertionError:
> 00:47:45Expected size: 1 but was: 0 in:
> 00:47:45[]
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateBootstrapped(ClientServerSessionCacheDUnitTest.java:258)
> 00:47:45at
> org.apache.geode.modules.util.ClientServerSessionCacheDUnitTest.validateServer(ClientServerSessionCacheDUnitTest.java:245)
> 00:47:53{noformat}
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-results/distributedTest/161716/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0081/test-artifacts/161716/distributedtestfiles-OpenJDK8-1.15.0-build.0081.tgz
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384331#comment-17384331
]
ASF GitHub Bot commented on GEODE-9431:
---
pdxcodemonkey commented on a change in pull request #831:
URL: https://github.com/apache/geode-native/pull/831#discussion_r673218319
##
File path: cppcache/test/ByteArrayFixture.cpp
##
@@ -20,7 +20,7 @@
::testing::AssertionResult ByteArrayFixture::assertByteArrayEqual(
const char* /*expectedStr*/, const char* /*bytesStr*/, const char*
expected,
const apache::geode::client::ByteArray& bytes) {
- // One would normally just use std::regex but gcc 4.4.7 is lacking.
+ // One would normally just use boost::regex but gcc 4.4.7 is lacking.
Review comment:
Hmmm, impenetrable test code with a somewhat cryptic comment about a
compiler we no longer use. How about we just delete the comment and move on?
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384334#comment-17384334
]
ASF subversion and git services commented on GEODE-9431:
Commit 7bcaa9ee5806020f5a07c5919c419df6556debf9 in geode-native's branch
refs/heads/develop from Matthew Reddington
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=7bcaa9e ]
GEODE-9431: Replaced std regex with Boost due to RHEL8. (#831)
* Replaced std regex with Boost due to RHEL8.
* Fix formatting issues
Co-authored-by: Blake Bender
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384333#comment-17384333
]
ASF GitHub Bot commented on GEODE-9431:
---
pdxcodemonkey merged pull request #831:
URL: https://github.com/apache/geode-native/pull/831
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9440) Revert changes for GEODE-9431
Blake Bender created GEODE-9440: --- Summary: Revert changes for GEODE-9431 Key: GEODE-9440 URL: https://issues.apache.org/jira/browse/GEODE-9440 Project: Geode Issue Type: Task Components: native client Reporter: Blake Bender We encountered a problem with `std::regex` crashing on RHEL-8 in release builds, and the first fix we found that worked was to switch to `boost::regex`. We're filing bugs with RedHat and GNU, so if/when the issue is resolved we will need to verify the fix and revert the workaround. We should be using `std::` objects whenever possible, certainly for something as mainstream as `regex`. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender resolved GEODE-9431.
-
Resolution: Fixed
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender updated GEODE-9431:
Fix Version/s: 1.15.0
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender closed GEODE-9431.
---
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9431) CI Failure: SegFault in apache-geode_unittests
[
https://issues.apache.org/jira/browse/GEODE-9431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384348#comment-17384348
]
ASF GitHub Bot commented on GEODE-9431:
---
pivotal-jbarrett commented on a change in pull request #831:
URL: https://github.com/apache/geode-native/pull/831#discussion_r673239968
##
File path: cppcache/test/ByteArrayFixture.cpp
##
@@ -20,7 +20,7 @@
::testing::AssertionResult ByteArrayFixture::assertByteArrayEqual(
const char* /*expectedStr*/, const char* /*bytesStr*/, const char*
expected,
const apache::geode::client::ByteArray& bytes) {
- // One would normally just use std::regex but gcc 4.4.7 is lacking.
+ // One would normally just use boost::regex but gcc 4.4.7 is lacking.
Review comment:
Yup
--
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
> CI Failure: SegFault in apache-geode_unittests
> --
>
> Key: GEODE-9431
> URL: https://issues.apache.org/jira/browse/GEODE-9431
> Project: Geode
> Issue Type: Bug
> Components: native client
>Reporter: Kamilla Aslami
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> {{Two consequent geode-native-develop/build-rhel-8-release runs failed with
> segmentation fault: }}
> {noformat}
> selected worker: 3eb01fee-0959-4e2d-8c25-44a153962eaa
> Warning: Permanently added '34.67.7.72' (ECDSA) to the list of known hosts.
> Test project /home/build/build/cppcache/test
> Start 1: apache-geode_unittests
> 1/1 Test #1: apache-geode_unittests ...***Exception: SegFault 0.43
> sec
> Running main() from
> /home/build/build/dependencies/gtest/gtest-extern-prefix/src/gtest-extern/googletest/src/gtest_main.cc
> [==] Running 374 tests from 42 test suites.
> [--] Global test environment set-up.
> [--] 6 tests from durationTest
> [ RUN ] durationTest.ceil
> [ OK ] durationTest.ceil (0 ms)
> [ RUN ] durationTest.toString
> [ OK ] durationTest.toString (0 ms)
> [ RUN ] durationTest.fromString
> [ OK ] durationTest.fromString (0 ms)
> [ RUN ] durationTest.fromStringWithCeil
> [ OK ] durationTest.fromStringWithCeil (0 ms)
> [ RUN ] durationTest.fromStringException
> [ OK ] durationTest.fromStringException (0 ms)
> [ RUN ] durationTest.assertBounds
> [ OK ] durationTest.assertBounds (1 ms)
> [--] 6 tests from durationTest (1 ms total){noformat}
> ...
> {noformat}
> 0% tests passed, 1 tests failed out of 1
> Total Test time (real) = 0.91 sec
> The following tests FAILED:
> 1 - apache-geode_unittests (SEGFAULT)
> Errors while running CTest{noformat}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9378) Implement ZRANGEBYSCORE Command
[ https://issues.apache.org/jira/browse/GEODE-9378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles reassigned GEODE-9378: - Assignee: Ray Ingles > Implement ZRANGEBYSCORE Command > --- > > Key: GEODE-9378 > URL: https://issues.apache.org/jira/browse/GEODE-9378 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Ray Ingles >Priority: Major > Labels: pull-request-available, redis > > Implement the [ZRANGEBYSCORE|https://redis.io/commands/zrangebyscore] command. > +Acceptance Criteria+ > The ZRANGEBYSCORE command has been implemented along with appropriate unit > tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. > The command has been tested using the redis-cli tool. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9378) Implement ZRANGEBYSCORE Command
[ https://issues.apache.org/jira/browse/GEODE-9378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384354#comment-17384354 ] ASF subversion and git services commented on GEODE-9378: Commit 0726d5a445d218b3775902d3a4dc4da5308ae4ed in geode's branch refs/heads/develop from Ray Ingles [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0726d5a ] GEODE-9378: Implement ZRANGEBYSCORE (#6700) GEODE-9378: Implements the ZRANGEBYSCORE command, including LIMITS option. Also fixes a formatting difference between Radish and Redis regarding Double values that represent integers. > Implement ZRANGEBYSCORE Command > --- > > Key: GEODE-9378 > URL: https://issues.apache.org/jira/browse/GEODE-9378 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Ray Ingles >Priority: Major > Labels: pull-request-available, redis > > Implement the [ZRANGEBYSCORE|https://redis.io/commands/zrangebyscore] command. > +Acceptance Criteria+ > The ZRANGEBYSCORE command has been implemented along with appropriate unit > tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. > The command has been tested using the redis-cli tool. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9378) Implement ZRANGEBYSCORE Command
[ https://issues.apache.org/jira/browse/GEODE-9378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384355#comment-17384355 ] ASF subversion and git services commented on GEODE-9378: Commit 0726d5a445d218b3775902d3a4dc4da5308ae4ed in geode's branch refs/heads/develop from Ray Ingles [ https://gitbox.apache.org/repos/asf?p=geode.git;h=0726d5a ] GEODE-9378: Implement ZRANGEBYSCORE (#6700) GEODE-9378: Implements the ZRANGEBYSCORE command, including LIMITS option. Also fixes a formatting difference between Radish and Redis regarding Double values that represent integers. > Implement ZRANGEBYSCORE Command > --- > > Key: GEODE-9378 > URL: https://issues.apache.org/jira/browse/GEODE-9378 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Ray Ingles >Priority: Major > Labels: pull-request-available, redis > > Implement the [ZRANGEBYSCORE|https://redis.io/commands/zrangebyscore] command. > +Acceptance Criteria+ > The ZRANGEBYSCORE command has been implemented along with appropriate unit > tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. > The command has been tested using the redis-cli tool. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9378) Implement ZRANGEBYSCORE Command
[ https://issues.apache.org/jira/browse/GEODE-9378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles resolved GEODE-9378. --- Fix Version/s: 1.15.0 Resolution: Fixed Implement ZRANGEBYSCORE command, including LIMIT option. > Implement ZRANGEBYSCORE Command > --- > > Key: GEODE-9378 > URL: https://issues.apache.org/jira/browse/GEODE-9378 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Ray Ingles >Priority: Major > Labels: pull-request-available, redis > Fix For: 1.15.0 > > > Implement the [ZRANGEBYSCORE|https://redis.io/commands/zrangebyscore] command. > +Acceptance Criteria+ > The ZRANGEBYSCORE command has been implemented along with appropriate unit > tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. > The command has been tested using the redis-cli tool. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-8609) Create a dunit suspect file per VM
[
https://issues.apache.org/jira/browse/GEODE-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag updated GEODE-8609:
---
Fix Version/s: 1.14.0
> Create a dunit suspect file per VM
> --
>
> Key: GEODE-8609
> URL: https://issues.apache.org/jira/browse/GEODE-8609
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> In some situations, especially when restarting Dunit VMs, it appears that the
> suspect log file can be corrupted since suspect processing reports errors
> such as:
> {noformat}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> 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 19594
> /home/geode/.gradle/caches/modules-2/files-2.1/antlr/antlr/2.7.7/83cd2cd674a21[warn
> 2020/10/11 15:23:24.988 GMT tid=105] Execution
> of Redis command APPEND append-key-1 -append-key-1-17484- failed:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.execute.FunctionInvocationTargetException:
> memberDeparted event for < 172.17.0.20(server-3:2004):41003 > crashed,
> true{noformat}
> Where the suspected string is corrupted.
> The proposed fix will create a new dunit_suspect log for each VM. The logs
> will now be named {{dunit_suspect-vm.log}}. The {{locator}} vm and the
> test runner vm will have logs named {{dunit_suspect-locator.log}} and
> {{dunit_suspect-local.log}} respectively.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-8609) Create a dunit suspect file per VM
[
https://issues.apache.org/jira/browse/GEODE-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag resolved GEODE-8609.
Resolution: Fixed
> Create a dunit suspect file per VM
> --
>
> Key: GEODE-8609
> URL: https://issues.apache.org/jira/browse/GEODE-8609
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> In some situations, especially when restarting Dunit VMs, it appears that the
> suspect log file can be corrupted since suspect processing reports errors
> such as:
> {noformat}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> 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 19594
> /home/geode/.gradle/caches/modules-2/files-2.1/antlr/antlr/2.7.7/83cd2cd674a21[warn
> 2020/10/11 15:23:24.988 GMT tid=105] Execution
> of Redis command APPEND append-key-1 -append-key-1-17484- failed:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.execute.FunctionInvocationTargetException:
> memberDeparted event for < 172.17.0.20(server-3:2004):41003 > crashed,
> true{noformat}
> Where the suspected string is corrupted.
> The proposed fix will create a new dunit_suspect log for each VM. The logs
> will now be named {{dunit_suspect-vm.log}}. The {{locator}} vm and the
> test runner vm will have logs named {{dunit_suspect-locator.log}} and
> {{dunit_suspect-local.log}} respectively.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (GEODE-8609) Create a dunit suspect file per VM
[
https://issues.apache.org/jira/browse/GEODE-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nabarun Nag closed GEODE-8609.
--
> Create a dunit suspect file per VM
> --
>
> Key: GEODE-8609
> URL: https://issues.apache.org/jira/browse/GEODE-8609
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> In some situations, especially when restarting Dunit VMs, it appears that the
> suspect log file can be corrupted since suspect processing reports errors
> such as:
> {noformat}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> 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 19594
> /home/geode/.gradle/caches/modules-2/files-2.1/antlr/antlr/2.7.7/83cd2cd674a21[warn
> 2020/10/11 15:23:24.988 GMT tid=105] Execution
> of Redis command APPEND append-key-1 -append-key-1-17484- failed:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.execute.FunctionInvocationTargetException:
> memberDeparted event for < 172.17.0.20(server-3:2004):41003 > crashed,
> true{noformat}
> Where the suspected string is corrupted.
> The proposed fix will create a new dunit_suspect log for each VM. The logs
> will now be named {{dunit_suspect-vm.log}}. The {{locator}} vm and the
> test runner vm will have logs named {{dunit_suspect-locator.log}} and
> {{dunit_suspect-local.log}} respectively.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-8609) Create a dunit suspect file per VM
[
https://issues.apache.org/jira/browse/GEODE-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384365#comment-17384365
]
ASF subversion and git services commented on GEODE-8609:
Commit 1637b7a3dce5edaa4317284e65d749e985e0 in geode's branch
refs/heads/support/1.14 from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1637b7a ]
GEODE-8609: Check logs for suspicious logs when VM is stopped.
* When a VM is stopped, the suspect string file is deleted
* Log checker is called at the end of the test.
* If a VM is restarted during a test, the logs are deleted and is not
checked at the end of the test.
* With the fix the logs are checked when the VM is stopped.
(cherry picked from commit e39c4c5ad79ee07d7760c98a85259cfb68c64e4c)
> Create a dunit suspect file per VM
> --
>
> Key: GEODE-8609
> URL: https://issues.apache.org/jira/browse/GEODE-8609
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> In some situations, especially when restarting Dunit VMs, it appears that the
> suspect log file can be corrupted since suspect processing reports errors
> such as:
> {noformat}
> org.apache.geode.redis.internal.executor.CrashAndNoRepeatDUnitTest >
> 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 19594
> /home/geode/.gradle/caches/modules-2/files-2.1/antlr/antlr/2.7.7/83cd2cd674a21[warn
> 2020/10/11 15:23:24.988 GMT tid=105] Execution
> of Redis command APPEND append-key-1 -append-key-1-17484- failed:
> org.apache.geode.cache.execute.FunctionException:
> org.apache.geode.cache.execute.FunctionInvocationTargetException:
> memberDeparted event for < 172.17.0.20(server-3:2004):41003 > crashed,
> true{noformat}
> Where the suspected string is corrupted.
> The proposed fix will create a new dunit_suspect log for each VM. The logs
> will now be named {{dunit_suspect-vm.log}}. The {{locator}} vm and the
> test runner vm will have logs named {{dunit_suspect-locator.log}} and
> {{dunit_suspect-local.log}} respectively.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9426) Update docs for HTTP Session Management
[
https://issues.apache.org/jira/browse/GEODE-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9426:
Labels: blocks-1.14.0 pull-request-available (was: pull-request-available)
> Update docs for HTTP Session Management
> ---
>
> Key: GEODE-9426
> URL: https://issues.apache.org/jira/browse/GEODE-9426
> Project: Geode
> Issue Type: Bug
> Components: docs
>Affects Versions: 1.13.3
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
>
> [From a community member] I suspect this affects many older versions ... but
> I wanted to document what I saw as I attempted to follow the docs:
> This page has incorrect jar:
> [https://geode.apache.org/docs/guide/113/tools_modules/http_session_mgmt/tomcat_installing_the_module.html]
>
> {{"geode-commons jar" should be "geode-common jar" ... no "s"}}
> Also missing geode tcp server jar (geode-tcp-server)
> And is missing this step (copied here from geode-examples):
> {nofomat}
> $ cp $CATALINA_HOME/bin/tomcat-juli.jar $CATALINA_HOME/lib/
> App would not start with this in context.xml ... it was not there already ...
> and when I added it, startup failed.
> Suggest working through both the geode-examples AND the official
> documentation to verify correctness. [Example treated separately - see
> GEODE-9430]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9426) Update docs for HTTP Session Management
[
https://issues.apache.org/jira/browse/GEODE-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen Nichols updated GEODE-9426:
Fix Version/s: 1.15.0
1.13.4
> Update docs for HTTP Session Management
> ---
>
> Key: GEODE-9426
> URL: https://issues.apache.org/jira/browse/GEODE-9426
> Project: Geode
> Issue Type: Bug
> Components: docs
>Affects Versions: 1.13.3
>Reporter: Dave Barnes
>Assignee: Dave Barnes
>Priority: Major
> Labels: blocks-1.14.0, pull-request-available
> Fix For: 1.13.4, 1.15.0
>
>
> [From a community member] I suspect this affects many older versions ... but
> I wanted to document what I saw as I attempted to follow the docs:
> This page has incorrect jar:
> [https://geode.apache.org/docs/guide/113/tools_modules/http_session_mgmt/tomcat_installing_the_module.html]
>
> {{"geode-commons jar" should be "geode-common jar" ... no "s"}}
> Also missing geode tcp server jar (geode-tcp-server)
> And is missing this step (copied here from geode-examples):
> {nofomat}
> $ cp $CATALINA_HOME/bin/tomcat-juli.jar $CATALINA_HOME/lib/
> App would not start with this in context.xml ... it was not there already ...
> and when I added it, startup failed.
> Suggest working through both the geode-examples AND the official
> documentation to verify correctness. [Example treated separately - see
> GEODE-9430]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9441) The NestedFunctionExecutionDistributedTest uses too many threads
Barrett Oglesby created GEODE-9441:
--
Summary: The NestedFunctionExecutionDistributedTest uses too many
threads
Key: GEODE-9441
URL: https://issues.apache.org/jira/browse/GEODE-9441
Project: Geode
Issue Type: Test
Components: tests
Reporter: Barrett Oglesby
The {{NestedFunctionExecutionDistributedTest}} uses {{OperationExecutors
MAX_FE_THREADS}} to configure both client function invocations and cache server
max connections.
It uses MAX_FE_THREADS * 2 for function executions which use Function Execution
Processor threads:
{noformat}
client.invoke(() -> executeFunction(new ParentFunction(), MAX_FE_THREADS * 2));
{noformat}
And potentially MAX_FE_THREADS * 3 for client connections which use
ServerConnection threads:
{noformat}
cacheServer.setMaxConnections(Math.max(CacheServer.DEFAULT_MAX_CONNECTIONS,
MAX_FE_THREADS * 3));
{noformat}
MAX_FE_THREADS was changed recently to:
{noformat}
Math.max(Runtime.getRuntime().availableProcessors() * 16, 16))
{noformat}
It doesn't need to use this many threads to test the behavior it is testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9441) The NestedFunctionExecutionDistributedTest uses too many threads
[
https://issues.apache.org/jira/browse/GEODE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrett Oglesby reassigned GEODE-9441:
--
Assignee: Dale Emery
> The NestedFunctionExecutionDistributedTest uses too many threads
>
>
> Key: GEODE-9441
> URL: https://issues.apache.org/jira/browse/GEODE-9441
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Barrett Oglesby
>Assignee: Dale Emery
>Priority: Major
>
> The {{NestedFunctionExecutionDistributedTest}} uses {{OperationExecutors
> MAX_FE_THREADS}} to configure both client function invocations and cache
> server max connections.
> It uses MAX_FE_THREADS * 2 for function executions which use Function
> Execution Processor threads:
> {noformat}
> client.invoke(() -> executeFunction(new ParentFunction(), MAX_FE_THREADS *
> 2));
> {noformat}
> And potentially MAX_FE_THREADS * 3 for client connections which use
> ServerConnection threads:
> {noformat}
> cacheServer.setMaxConnections(Math.max(CacheServer.DEFAULT_MAX_CONNECTIONS,
> MAX_FE_THREADS * 3));
> {noformat}
> MAX_FE_THREADS was changed recently to:
> {noformat}
> Math.max(Runtime.getRuntime().availableProcessors() * 16, 16))
> {noformat}
> It doesn't need to use this many threads to test the behavior it is testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9438) NC user guides: Delete obsolete Auth properties
[ https://issues.apache.org/jira/browse/GEODE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384423#comment-17384423 ] ASF GitHub Bot commented on GEODE-9438: --- davebarnes97 opened a new pull request #832: URL: https://github.com/apache/geode-native/pull/832 Deleted three obsolete system properties: - security-client-auth-factory - security-client-auth-library - security-client-dhalgo Removed a redundant copy of the same table and updated the only link that pointed to it. -- 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 > NC user guides: Delete obsolete Auth properties > --- > > Key: GEODE-9438 > URL: https://issues.apache.org/jira/browse/GEODE-9438 > Project: Geode > Issue Type: Bug > Components: docs, native client >Affects Versions: 1.13.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > > Native client user guides (both .NET and C++) still include three obsolete > auth-related system properties: > security-client-auth-factory > security-client-auth-library > security-client-dhalgo > These should be deleted from the documentation. > Note: Functionality of the first two has been superseded by > SetAuthInitialize(). Examples showing its usage have already been included in > the docs. > Pages in which these properties appear include: > .NET: > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html > C++: > https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9438) NC user guides: Delete obsolete Auth properties
[ https://issues.apache.org/jira/browse/GEODE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-9438: -- Labels: pull-request-available (was: ) > NC user guides: Delete obsolete Auth properties > --- > > Key: GEODE-9438 > URL: https://issues.apache.org/jira/browse/GEODE-9438 > Project: Geode > Issue Type: Bug > Components: docs, native client >Affects Versions: 1.13.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Native client user guides (both .NET and C++) still include three obsolete > auth-related system properties: > security-client-auth-factory > security-client-auth-library > security-client-dhalgo > These should be deleted from the documentation. > Note: Functionality of the first two has been superseded by > SetAuthInitialize(). Examples showing its usage have already been included in > the docs. > Pages in which these properties appear include: > .NET: > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html > C++: > https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9379) Implement ZREVRANGEBYSCORE Command
[ https://issues.apache.org/jira/browse/GEODE-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ray Ingles reassigned GEODE-9379: - Assignee: Ray Ingles > Implement ZREVRANGEBYSCORE Command > -- > > Key: GEODE-9379 > URL: https://issues.apache.org/jira/browse/GEODE-9379 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Ray Ingles >Priority: Major > Labels: redis > > Implement the [ZREVRANGEBYSCORE|https://redis.io/commands/zrevrangebyscore] > command. > > Acceptance Criteria > The ZREVRANGEBYSCORE command has been implemented along with appropriate unit > tests. > > The command has been added to the AbstractHitsMissesIntegrationTest. > The command has been tested using the redis-cli tool. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9441) The NestedFunctionExecutionDistributedTest uses too many threads
[
https://issues.apache.org/jira/browse/GEODE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9441:
--
Labels: pull-request-available (was: )
> The NestedFunctionExecutionDistributedTest uses too many threads
>
>
> Key: GEODE-9441
> URL: https://issues.apache.org/jira/browse/GEODE-9441
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Barrett Oglesby
>Assignee: Dale Emery
>Priority: Major
> Labels: pull-request-available
>
> The {{NestedFunctionExecutionDistributedTest}} uses {{OperationExecutors
> MAX_FE_THREADS}} to configure both client function invocations and cache
> server max connections.
> It uses MAX_FE_THREADS * 2 for function executions which use Function
> Execution Processor threads:
> {noformat}
> client.invoke(() -> executeFunction(new ParentFunction(), MAX_FE_THREADS *
> 2));
> {noformat}
> And potentially MAX_FE_THREADS * 3 for client connections which use
> ServerConnection threads:
> {noformat}
> cacheServer.setMaxConnections(Math.max(CacheServer.DEFAULT_MAX_CONNECTIONS,
> MAX_FE_THREADS * 3));
> {noformat}
> MAX_FE_THREADS was changed recently to:
> {noformat}
> Math.max(Runtime.getRuntime().availableProcessors() * 16, 16))
> {noformat}
> It doesn't need to use this many threads to test the behavior it is testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9441) The NestedFunctionExecutionDistributedTest uses too many threads
[
https://issues.apache.org/jira/browse/GEODE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-9441:
--
Labels: GeodeOperationAPI pull-request-available (was:
pull-request-available)
> The NestedFunctionExecutionDistributedTest uses too many threads
>
>
> Key: GEODE-9441
> URL: https://issues.apache.org/jira/browse/GEODE-9441
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Barrett Oglesby
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> The {{NestedFunctionExecutionDistributedTest}} uses {{OperationExecutors
> MAX_FE_THREADS}} to configure both client function invocations and cache
> server max connections.
> It uses MAX_FE_THREADS * 2 for function executions which use Function
> Execution Processor threads:
> {noformat}
> client.invoke(() -> executeFunction(new ParentFunction(), MAX_FE_THREADS *
> 2));
> {noformat}
> And potentially MAX_FE_THREADS * 3 for client connections which use
> ServerConnection threads:
> {noformat}
> cacheServer.setMaxConnections(Math.max(CacheServer.DEFAULT_MAX_CONNECTIONS,
> MAX_FE_THREADS * 3));
> {noformat}
> MAX_FE_THREADS was changed recently to:
> {noformat}
> Math.max(Runtime.getRuntime().availableProcessors() * 16, 16))
> {noformat}
> It doesn't need to use this many threads to test the behavior it is testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9388) Implement ZRANGEBYLEX Command
[ https://issues.apache.org/jira/browse/GEODE-9388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donal Evans reassigned GEODE-9388: -- Assignee: Donal Evans > Implement ZRANGEBYLEX Command > - > > Key: GEODE-9388 > URL: https://issues.apache.org/jira/browse/GEODE-9388 > Project: Geode > Issue Type: New Feature > Components: redis >Affects Versions: 1.15.0 >Reporter: Wayne >Assignee: Donal Evans >Priority: Major > Labels: redis > > Implement the [ZRANGEBYLEX|https://redis.io/commands/zrangebylex] command > without the LIMIT option. > +Acceptance Criteria+ > The ZRANGEBYLEX command has been implemented along with appropriate unit > tests. > The command has been added to the AbstractHitsMissesIntegrationTest. The > command has been tested using the redis-cli tool. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[ https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384452#comment-17384452 ] ASF GitHub Bot commented on GEODE-9360: --- pdxcodemonkey commented on a change in pull request #823: URL: https://github.com/apache/geode-native/pull/823#discussion_r673423735 ## File path: .gitignore ## @@ -18,3 +18,7 @@ /tools/gnmsg/.idea/ /tools/gnmsg/__pycache__/ + +/netcore/*/bin/ Review comment: > Is there any way to get .NET build tools to not build in the source tree? Not as far as I know. A quick web search yields a lot of info about MSBuild-style csproj files, but nothing about the new improved dotnet kind. -- 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 > Initial revision of .net core support > - > > Key: GEODE-9360 > URL: https://issues.apache.org/jira/browse/GEODE-9360 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > As a .net core developer, I would like to be able to access the geode-native > API. To facilitate this, we need to implement a minimal set of C# classes > that use p/invoke to access geode-native via C bindings (GEODE-9358). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[ https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384453#comment-17384453 ] ASF GitHub Bot commented on GEODE-9360: --- pivotal-jbarrett commented on a change in pull request #823: URL: https://github.com/apache/geode-native/pull/823#discussion_r673427639 ## File path: .gitignore ## @@ -18,3 +18,7 @@ /tools/gnmsg/.idea/ /tools/gnmsg/__pycache__/ + +/netcore/*/bin/ Review comment: Ok, so this is a function you you checking in the csproj as source rather than generating it with CMake. -- 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 > Initial revision of .net core support > - > > Key: GEODE-9360 > URL: https://issues.apache.org/jira/browse/GEODE-9360 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > As a .net core developer, I would like to be able to access the geode-native > API. To facilitate this, we need to implement a minimal set of C# classes > that use p/invoke to access geode-native via C bindings (GEODE-9358). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[ https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384455#comment-17384455 ] ASF GitHub Bot commented on GEODE-9360: --- pdxcodemonkey commented on a change in pull request #823: URL: https://github.com/apache/geode-native/pull/823#discussion_r673434331 ## File path: .gitignore ## @@ -18,3 +18,7 @@ /tools/gnmsg/.idea/ /tools/gnmsg/__pycache__/ + +/netcore/*/bin/ Review comment: RIght, cmake generates the "old" style .csproj and .sln files. -- 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 > Initial revision of .net core support > - > > Key: GEODE-9360 > URL: https://issues.apache.org/jira/browse/GEODE-9360 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > As a .net core developer, I would like to be able to access the geode-native > API. To facilitate this, we need to implement a minimal set of C# classes > that use p/invoke to access geode-native via C bindings (GEODE-9358). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9428) CI Failure: PSetEXNativeRedisAcceptanceTest fails with CLUSTERDOWN error
[
https://issues.apache.org/jira/browse/GEODE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384465#comment-17384465
]
Geode Integration commented on GEODE-9428:
--
Seen in [acceptance-test-openjdk11
#90|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk11/builds/90]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-results/acceptanceTest/1626806511/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-artifacts/1626806511/acceptancetestfiles-openjdk11-1.15.0-build.0375.tgz].
> CI Failure: PSetEXNativeRedisAcceptanceTest fails with CLUSTERDOWN error
>
>
> Key: GEODE-9428
> URL: https://issues.apache.org/jira/browse/GEODE-9428
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Hale Bales
>Assignee: Hale Bales
>Priority: Major
>
> CI run is here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk11/builds/82#L60e11384:311
> {code:java}
> org.apache.geode.redis.internal.executor.string.PSetEXNativeRedisAcceptanceTest
> > testPSetEX FAILED
> redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
> cluster is down
> at redis.clients.jedis.Protocol.processError(Protocol.java:125)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at
> redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:270)
> at redis.clients.jedis.Jedis.psetex(Jedis.java:3616)
> at redis.clients.jedis.JedisCluster$30.execute(JedisCluster.java:572)
> at redis.clients.jedis.JedisCluster$30.execute(JedisCluster.java:569)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.psetex(JedisCluster.java:574)
> at
> org.apache.geode.redis.internal.executor.string.AbstractPSetEXIntegrationTest.testPSetEX(AbstractPSetEXIntegrationTest.java:54)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:120)
> at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.g
[jira] [Commented] (GEODE-9428) CI Failure: PSetEXNativeRedisAcceptanceTest fails with CLUSTERDOWN error
[
https://issues.apache.org/jira/browse/GEODE-9428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384466#comment-17384466
]
Geode Integration commented on GEODE-9428:
--
Seen in [acceptance-test-openjdk11
#90|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk11/builds/90]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-results/acceptanceTest/1626806511/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-artifacts/1626806511/acceptancetestfiles-openjdk11-1.15.0-build.0375.tgz].
> CI Failure: PSetEXNativeRedisAcceptanceTest fails with CLUSTERDOWN error
>
>
> Key: GEODE-9428
> URL: https://issues.apache.org/jira/browse/GEODE-9428
> Project: Geode
> Issue Type: Bug
> Components: redis
>Reporter: Hale Bales
>Assignee: Hale Bales
>Priority: Major
>
> CI run is here:
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk11/builds/82#L60e11384:311
> {code:java}
> org.apache.geode.redis.internal.executor.string.PSetEXNativeRedisAcceptanceTest
> > testPSetEX FAILED
> redis.clients.jedis.exceptions.JedisClusterException: CLUSTERDOWN The
> cluster is down
> at redis.clients.jedis.Protocol.processError(Protocol.java:125)
> at redis.clients.jedis.Protocol.process(Protocol.java:169)
> at redis.clients.jedis.Protocol.read(Protocol.java:223)
> at
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:352)
> at
> redis.clients.jedis.Connection.getStatusCodeReply(Connection.java:270)
> at redis.clients.jedis.Jedis.psetex(Jedis.java:3616)
> at redis.clients.jedis.JedisCluster$30.execute(JedisCluster.java:572)
> at redis.clients.jedis.JedisCluster$30.execute(JedisCluster.java:569)
> at
> redis.clients.jedis.JedisClusterCommand.runWithRetries(JedisClusterCommand.java:121)
> at
> redis.clients.jedis.JedisClusterCommand.run(JedisClusterCommand.java:45)
> at redis.clients.jedis.JedisCluster.psetex(JedisCluster.java:574)
> at
> org.apache.geode.redis.internal.executor.string.AbstractPSetEXIntegrationTest.testPSetEX(AbstractPSetEXIntegrationTest.java:54)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at
> org.apache.geode.redis.NativeRedisClusterTestRule$1.evaluate(NativeRedisClusterTestRule.java:120)
> at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecutor.runTestClass(JUnitTestClassExecutor.java:110)
> at
> org.g
[jira] [Commented] (GEODE-9156) Switch from docker-compose to testcontainers
[ https://issues.apache.org/jira/browse/GEODE-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384474#comment-17384474 ] Geode Integration commented on GEODE-9156: -- Seen on support/1.12 in [acceptance-test-openjdk8 #20|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/acceptance-test-openjdk8/builds/20] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0264/test-results/acceptanceTest/1626148702/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0264/test-artifacts/1626148702/acceptancetestfiles-openjdk8-1.12.4-build.0264.tgz]. > Switch from docker-compose to testcontainers > > > Key: GEODE-9156 > URL: https://issues.apache.org/jira/browse/GEODE-9156 > Project: Geode > Issue Type: Task > Components: membership >Reporter: Ernest Burghardt >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.12.4, 1.13.4, 1.14.0, 1.15.0 > > > Palantir docker-compose-rule is sunsetting this month. Palantir advises > switching to testcontainers' docker compose integration. We already use > testcontainer... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9156) Switch from docker-compose to testcontainers
[ https://issues.apache.org/jira/browse/GEODE-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384473#comment-17384473 ] Geode Integration commented on GEODE-9156: -- Seen on support/1.12 in [acceptance-test-openjdk8 #17.2|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/acceptance-test-openjdk8/builds/17.2] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0263/test-results/acceptanceTest/1626140057/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0263/test-artifacts/1626140057/acceptancetestfiles-openjdk8-1.12.4-build.0263.tgz]. > Switch from docker-compose to testcontainers > > > Key: GEODE-9156 > URL: https://issues.apache.org/jira/browse/GEODE-9156 > Project: Geode > Issue Type: Task > Components: membership >Reporter: Ernest Burghardt >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > Fix For: 1.12.4, 1.13.4, 1.14.0, 1.15.0 > > > Palantir docker-compose-rule is sunsetting this month. Palantir advises > switching to testcontainers' docker compose integration. We already use > testcontainer... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384475#comment-17384475
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [distributed-test-openjdk8
#12|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/12]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0257/test-results/distributedTest/1625102217/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0257/test-artifacts/1625102217/distributedtestfiles-openjdk8-1.12.4-build.0257.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7702) DistributedAckRegionCCEDUnitTest > testClearOnNonReplicateWithConcurrentEvents is showing a product bug
[
https://issues.apache.org/jira/browse/GEODE-7702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384476#comment-17384476
]
Geode Integration commented on GEODE-7702:
--
Seen on support/1.12 in [distributed-test-openjdk11
#15|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk11/builds/15]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0259/test-results/distributedTest/1625880263/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0259/test-artifacts/1625880263/distributedtestfiles-openjdk11-1.12.4-build.0259.tgz].
> DistributedAckRegionCCEDUnitTest >
> testClearOnNonReplicateWithConcurrentEvents is showing a product bug
> ---
>
> Key: GEODE-7702
> URL: https://issues.apache.org/jira/browse/GEODE-7702
> Project: Geode
> Issue Type: Bug
> Components: client/server
>Reporter: Mark Hanson
>Assignee: Xiaojian Zhou
>Priority: Major
> Labels: GeodeCommons
> Fix For: 1.14.0
>
>
> testClearOnNonReplicateWithConcurrentEvents in
> DistributedAckRegionCCEDUnitTest.java
> versionTestClearOnNonReplicateWithConcurrentEvents in
> MultiVMRegionTestCase.java
> doOpsLoop
> doOpsLoopNoFlush
> {noformat}
> case 5:
> if (includeClear) {
> CCRegion.clear();
> break;
> } else {
> if (CCRegion.getAttributes().getDataPolicy().withReplication()) {
> if (oldkey != null) {
> CCRegion.putIfAbsent(oldkey, value);
> }
> break;
> } // else fall through to invalidate
> } {noformat}
> the addition of this chunk of code causes this test to fail.
> The core of the problem is that a putall and a clear are happening
> concurrently and the "system" does not respond by either clearing all entries
> or letting all entries persist.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-5782) LauncherMemberMXBeanIntegrationTest can fail intermittently
[
https://issues.apache.org/jira/browse/GEODE-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384477#comment-17384477
]
Geode Integration commented on GEODE-5782:
--
Seen on support/1.12 in [windows-core-integration-test-openjdk8
#18|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/windows-core-integration-test-openjdk8/builds/18]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0263/test-results/integrationTest/1626121506/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0263/test-artifacts/1626121506/windows-coreintegrationtestfiles-openjdk8-1.12.4-build.0263.tgz].
> LauncherMemberMXBeanIntegrationTest can fail intermittently
> ---
>
> Key: GEODE-5782
> URL: https://issues.apache.org/jira/browse/GEODE-5782
> Project: Geode
> Issue Type: Bug
> Components: jmx
>Affects Versions: 1.9.0
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Noticed this failure:
> {noformat}
> org.apache.geode.distributed.LauncherMemberMXBeanIntegrationTest >
> showOSMetrics_reconstructsOSMetricsFromCompositeDataType FAILED
> org.junit.ComparisonFailure: expected:<204.[68]> but was:<204.[55]>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at
> org.apache.geode.distributed.LauncherMemberMXBeanIntegrationTest.showOSMetrics_reconstructsOSMetricsFromCompositeDataType(LauncherMemberMXBeanIntegrationTest.java:143)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-694) CI failure: ReliableMessagingDUnitTest.testPeriodicAckSendByClientPrimaryFailover
[
https://issues.apache.org/jira/browse/GEODE-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384480#comment-17384480
]
Geode Integration commented on GEODE-694:
-
Seen on support/1.12 in [distributed-test-openjdk8
#18|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk8/builds/18]
... see [test
results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0264/test-results/distributedTest/1626132305/]
or download
[artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.4-build.0264/test-artifacts/1626132305/distributedtestfiles-openjdk8-1.12.4-build.0264.tgz].
> CI failure:
> ReliableMessagingDUnitTest.testPeriodicAckSendByClientPrimaryFailover
> -
>
> Key: GEODE-694
> URL: https://issues.apache.org/jira/browse/GEODE-694
> Project: Geode
> Issue Type: Bug
> Components: client queues
>Affects Versions: 1.0.0-incubating
>Reporter: Jens Deppe
>Priority: Major
> Labels: CI, Flaky
>
> https://builds.apache.org/job/Geode-nightly/313/testReport/junit/com.gemstone.gemfire.internal.cache.tier.sockets/ReliableMessagingDUnitTest/testPeriodicAckSendByClientPrimaryFailover/
> git rev ec9d16a3130e33ee53d837301dc35c3a8bf0e99d build #313
> {noformat}
> Error Message
> junit.framework.AssertionFailedError: Creation time 1450161450166 supposed to
> be same as seo 1450161454951
> Stacktrace
> junit.framework.AssertionFailedError: Creation time 1450161450166 supposed to
> be same as seo 1450161454951
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ReliableMessagingDUnitTest.waitForClientAck(ReliableMessagingDUnitTest.java:150)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ReliableMessagingDUnitTest.testPeriodicAckSendByClientPrimaryFailover(ReliableMessagingDUnitTest.java:120)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:49
[jira] [Assigned] (GEODE-9423) Improve Tomcat rolling upgrade tests
[ https://issues.apache.org/jira/browse/GEODE-9423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarah Abbey reassigned GEODE-9423: -- Assignee: Benjamin P Ross (was: Sarah Abbey) > Improve Tomcat rolling upgrade tests > > > Key: GEODE-9423 > URL: https://issues.apache.org/jira/browse/GEODE-9423 > Project: Geode > Issue Type: Test >Reporter: Sarah Abbey >Assignee: Benjamin P Ross >Priority: Major > > Refactor/improve Tomcat rolling upgrade tests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9418) Add Rolling Upgrade Tests for Tomcat 9
[ https://issues.apache.org/jira/browse/GEODE-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarah Abbey reassigned GEODE-9418: -- Assignee: Benjamin P Ross (was: Sarah Abbey) > Add Rolling Upgrade Tests for Tomcat 9 > -- > > Key: GEODE-9418 > URL: https://issues.apache.org/jira/browse/GEODE-9418 > Project: Geode > Issue Type: Test >Reporter: Sarah Abbey >Assignee: Benjamin P Ross >Priority: Major > Labels: pull-request-available > > We have these tests for Tomcat 8, but never added them for Tomcat 9 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-9351) Create Session State Module for Tomcat 10
[ https://issues.apache.org/jira/browse/GEODE-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarah Abbey reassigned GEODE-9351: -- Assignee: Benjamin P Ross (was: Sarah Abbey) > Create Session State Module for Tomcat 10 > - > > Key: GEODE-9351 > URL: https://issues.apache.org/jira/browse/GEODE-9351 > Project: Geode > Issue Type: New Feature >Affects Versions: 1.15.0 >Reporter: Sarah Abbey >Assignee: Benjamin P Ross >Priority: Minor > > Tomcat 10 is here! Let's create a Geode Tomcat Session State module to > support it. Or create a generic one if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9351) Create Session State Module for Tomcat 10
[ https://issues.apache.org/jira/browse/GEODE-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sarah Abbey updated GEODE-9351: --- Priority: Minor (was: Major) > Create Session State Module for Tomcat 10 > - > > Key: GEODE-9351 > URL: https://issues.apache.org/jira/browse/GEODE-9351 > Project: Geode > Issue Type: New Feature >Affects Versions: 1.15.0 >Reporter: Sarah Abbey >Assignee: Sarah Abbey >Priority: Minor > > Tomcat 10 is here! Let's create a Geode Tomcat Session State module to > support it. Or create a generic one if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9438) NC user guides: Delete obsolete Auth properties
[ https://issues.apache.org/jira/browse/GEODE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384506#comment-17384506 ] ASF subversion and git services commented on GEODE-9438: Commit ea86065265c6d380a86e96e763bbafc62b01d17d in geode-native's branch refs/heads/develop from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=ea86065 ] GEODE-9438: NC user guides - Delete obsolete Auth properties (#832) > NC user guides: Delete obsolete Auth properties > --- > > Key: GEODE-9438 > URL: https://issues.apache.org/jira/browse/GEODE-9438 > Project: Geode > Issue Type: Bug > Components: docs, native client >Affects Versions: 1.13.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Native client user guides (both .NET and C++) still include three obsolete > auth-related system properties: > security-client-auth-factory > security-client-auth-library > security-client-dhalgo > These should be deleted from the documentation. > Note: Functionality of the first two has been superseded by > SetAuthInitialize(). Examples showing its usage have already been included in > the docs. > Pages in which these properties appear include: > .NET: > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html > C++: > https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9438) NC user guides: Delete obsolete Auth properties
[ https://issues.apache.org/jira/browse/GEODE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384507#comment-17384507 ] ASF GitHub Bot commented on GEODE-9438: --- davebarnes97 merged pull request #832: URL: https://github.com/apache/geode-native/pull/832 -- 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 > NC user guides: Delete obsolete Auth properties > --- > > Key: GEODE-9438 > URL: https://issues.apache.org/jira/browse/GEODE-9438 > Project: Geode > Issue Type: Bug > Components: docs, native client >Affects Versions: 1.13.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Native client user guides (both .NET and C++) still include three obsolete > auth-related system properties: > security-client-auth-factory > security-client-auth-library > security-client-dhalgo > These should be deleted from the documentation. > Note: Functionality of the first two has been superseded by > SetAuthInitialize(). Examples showing its usage have already been included in > the docs. > Pages in which these properties appear include: > .NET: > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html > C++: > https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9438) NC user guides: Delete obsolete Auth properties
[ https://issues.apache.org/jira/browse/GEODE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384510#comment-17384510 ] ASF subversion and git services commented on GEODE-9438: Commit aadac580f4daa1282515b1c728276a670acdbd59 in geode-native's branch refs/heads/support/1.13 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=aadac58 ] GEODE-9438: NC user guides - Delete obsolete Auth properties (#832) > NC user guides: Delete obsolete Auth properties > --- > > Key: GEODE-9438 > URL: https://issues.apache.org/jira/browse/GEODE-9438 > Project: Geode > Issue Type: Bug > Components: docs, native client >Affects Versions: 1.13.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Native client user guides (both .NET and C++) still include three obsolete > auth-related system properties: > security-client-auth-factory > security-client-auth-library > security-client-dhalgo > These should be deleted from the documentation. > Note: Functionality of the first two has been superseded by > SetAuthInitialize(). Examples showing its usage have already been included in > the docs. > Pages in which these properties appear include: > .NET: > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html > C++: > https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[ https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384509#comment-17384509 ] ASF GitHub Bot commented on GEODE-9360: --- pdxcodemonkey commented on a change in pull request #823: URL: https://github.com/apache/geode-native/pull/823#discussion_r673536390 ## File path: .gitignore ## @@ -18,3 +18,7 @@ /tools/gnmsg/.idea/ /tools/gnmsg/__pycache__/ + +/netcore/*/bin/ Review comment: > Also, can you put these in a `.gitignore` in the `netcore` directory. Done. -- 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 > Initial revision of .net core support > - > > Key: GEODE-9360 > URL: https://issues.apache.org/jira/browse/GEODE-9360 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Blake Bender >Priority: Major > Labels: pull-request-available > > As a .net core developer, I would like to be able to access the geode-native > API. To facilitate this, we need to implement a minimal set of C# classes > that use p/invoke to access geode-native via C bindings (GEODE-9358). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9438) NC user guides: Delete obsolete Auth properties
[ https://issues.apache.org/jira/browse/GEODE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384508#comment-17384508 ] ASF subversion and git services commented on GEODE-9438: Commit 6950d9df1ff945f9598b70a6b028efd2a08b96e9 in geode-native's branch refs/heads/support/1.14 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=6950d9d ] GEODE-9438: NC user guides - Delete obsolete Auth properties (#832) > NC user guides: Delete obsolete Auth properties > --- > > Key: GEODE-9438 > URL: https://issues.apache.org/jira/browse/GEODE-9438 > Project: Geode > Issue Type: Bug > Components: docs, native client >Affects Versions: 1.13.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Native client user guides (both .NET and C++) still include three obsolete > auth-related system properties: > security-client-auth-factory > security-client-auth-library > security-client-dhalgo > These should be deleted from the documentation. > Note: Functionality of the first two has been superseded by > SetAuthInitialize(). Examples showing its usage have already been included in > the docs. > Pages in which these properties appear include: > .NET: > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html > C++: > https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384516#comment-17384516 ] Geode Integration commented on GEODE-9442: -- Seen in [acceptance-test-openjdk8 #88|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88] ... see [test results|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-results/acceptanceTest/1626808501/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-artifacts/1626808501/acceptancetestfiles-openjdk8-1.15.0-build.0375.tgz]. > CI Failure: acceptance-test-openjdk8 timed out > -- > > Key: GEODE-9442 > URL: https://issues.apache.org/jira/browse/GEODE-9442 > Project: Geode > Issue Type: Bug > Components: redis >Reporter: Eric Shu >Priority: Major > > This acceptance-test-openjdk8 failed due to timeout. > https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 > It does not appear to be one particular test hang -- as all running tests are > finished showing status of SUCCESS. > However, it shows that gradle no able to shut down one test worker: > in daemon-4088.out.log under .gradle_logs directory following exception was > seen: > Daemon is stopping immediately stop command received > Daemon vm is shutting down... The daemon has exited normally or was > terminated in response to a user interrupt. > failed to abort Gradle Test Executor 143 > org.gradle.process.internal.ExecException: A problem occurred waiting for > process 'Gradle Test Executor 143' to complete. > at > org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) > at > org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) > at > org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) > at > org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException: Shutdown in progress > at > java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) > at java.lang.Runtime.removeShutdownHook(Runtime.java:239) > at > org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) > at > org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) > at > org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) > at > org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) > at > org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) > ... 7 more > Also, in > geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary > output.bin file that Redis container was started but no further information > for its shutdown. No sure if this is normal or not. > ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] > Ryuk started - will monitor and terminate Testcontainers containers on JVM > exit > ^A<9c>^H^@^A > ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking > the system... > ^A<9c>^H^@^A > ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 > ^A<9c>^H^@^A > ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] > â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space > ^A<9c>^H^@^A > ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating > container for image: redis:5.0.6 > ^A<9c>^H^@^A > ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] > Starting container with ID: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 > ^A<9c>^H^@^A > ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] > Container redis:5.0.6 is starting: > 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007
[jira] [Updated] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-9442: Description: This acceptance-test-openjdk8 failed due to timeout. https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 It does not appear to be one particular test hang -- as all running tests are finished showing status of SUCCESS. However, it shows that gradle no able to shut down one test worker: in daemon-4088.out.log under .gradle_logs directory following exception was seen: Daemon is stopping immediately stop command received Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt. failed to abort Gradle Test Executor 143 org.gradle.process.internal.ExecException: A problem occurred waiting for process 'Gradle Test Executor 143' to complete. at org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) at org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) at java.lang.Runtime.removeShutdownHook(Runtime.java:239) at org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) at org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) at org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) ... 7 more Also, in geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary output.bin file that Redis container was started but no further information for its shutdown. No sure if this is normal or not. ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] Ryuk started - will monitor and terminate Testcontainers containers on JVM exit ^A<9c>^H^@^A ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking the system... ^A<9c>^H^@^A ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 ^A<9c>^H^@^A ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space ^A<9c>^H^@^A ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating container for image: redis:5.0.6 ^A<9c>^H^@^A ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] Starting container with ID: 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 ^A<9c>^H^@^A ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] Container redis:5.0.6 is starting: 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 ^A<9c>^H^@^A ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] Container redis:5.0.6 started in PT0.644S ^A<9c>^H^@^A ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started redis container with exposed port 6379 -> 33290 Someone has more knowledge of redis container should take a look and determine if it is an real issue or not. =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-results/acceptanceTest/1626808501/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-artifacts/1626808501/acceptancetestfiles-openjdk8-1.15.0-build.0375.tgz was: This acceptance-test-openjdk8 failed due to timeout. https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 It does
[jira] [Commented] (GEODE-9441) The NestedFunctionExecutionDistributedTest uses too many threads
[
https://issues.apache.org/jira/browse/GEODE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384515#comment-17384515
]
ASF subversion and git services commented on GEODE-9441:
Commit 6890221ddba6c60c80796f581dab164f4043b65b in geode's branch
refs/heads/develop from Dale Emery
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6890221 ]
GEODE-9441: Reduce Nested func test thread count (#6708)
Change `NestedFunctionExecutionDistributedTest` to create fewer threads.
The test creates a number of threads that is a multiple of
`MAX_FE_THREADS`. On a CI machine, the default value of `MAX_FE_THREADS`
can be very high, causing this test to create thousands of threads. This
can leave the system unable to create threads for other processes, which
in turn can cause Gradle processes or other tests to fail or hang.
This test now sets `MAX_FE_THREADS` to a lower value (100), which
suffices for the purpose of the test, and results in greatly reduced
consumption of threads.
Co-authored-by: Dale Emery
> The NestedFunctionExecutionDistributedTest uses too many threads
>
>
> Key: GEODE-9441
> URL: https://issues.apache.org/jira/browse/GEODE-9441
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Barrett Oglesby
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> The {{NestedFunctionExecutionDistributedTest}} uses {{OperationExecutors
> MAX_FE_THREADS}} to configure both client function invocations and cache
> server max connections.
> It uses MAX_FE_THREADS * 2 for function executions which use Function
> Execution Processor threads:
> {noformat}
> client.invoke(() -> executeFunction(new ParentFunction(), MAX_FE_THREADS *
> 2));
> {noformat}
> And potentially MAX_FE_THREADS * 3 for client connections which use
> ServerConnection threads:
> {noformat}
> cacheServer.setMaxConnections(Math.max(CacheServer.DEFAULT_MAX_CONNECTIONS,
> MAX_FE_THREADS * 3));
> {noformat}
> MAX_FE_THREADS was changed recently to:
> {noformat}
> Math.max(Runtime.getRuntime().availableProcessors() * 16, 16))
> {noformat}
> It doesn't need to use this many threads to test the behavior it is testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
[ https://issues.apache.org/jira/browse/GEODE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Shu updated GEODE-9442: Description: This acceptance-test-openjdk8 failed due to timeout. https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 It does not appear to be one particular test hang -- as all running tests are finished showing status of SUCCESS. There are 1153 tests shown being run in this run. Test Summary 1153 tests The previous run showed 1295 tests were run. Test Summary 1295 tests However, it shows that gradle no able to shut down one test worker: in daemon-4088.out.log under .gradle_logs directory following exception was seen: Daemon is stopping immediately stop command received Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt. failed to abort Gradle Test Executor 143 org.gradle.process.internal.ExecException: A problem occurred waiting for process 'Gradle Test Executor 143' to complete. at org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) at org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) at java.lang.Runtime.removeShutdownHook(Runtime.java:239) at org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) at org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) at org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) ... 7 more Also, in geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary output.bin file that Redis container was started but no further information for its shutdown. No sure if this is normal or not. ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] Ryuk started - will monitor and terminate Testcontainers containers on JVM exit ^A<9c>^H^@^A ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking the system... ^A<9c>^H^@^A ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 ^A<9c>^H^@^A ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space ^A<9c>^H^@^A ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating container for image: redis:5.0.6 ^A<9c>^H^@^A ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] Starting container with ID: 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 ^A<9c>^H^@^A ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] Container redis:5.0.6 is starting: 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 ^A<9c>^H^@^A ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] Container redis:5.0.6 started in PT0.644S ^A<9c>^H^@^A ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started redis container with exposed port 6379 -> 33290 Someone has more knowledge of redis container should take a look and determine if it is an real issue or not. =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-results/acceptanceTest/1626808501/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: http://files.apachegeode-ci.info/builds/apache-develop-main/1.15.0-build.0375/test-artifacts/1626808501/acceptancetestfiles-openjdk8-1.15.0-build.0375.tgz was: This acceptance-test-openjdk8 failed
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[
https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384518#comment-17384518
]
ASF GitHub Bot commented on GEODE-9360:
---
pdxcodemonkey commented on a change in pull request #823:
URL: https://github.com/apache/geode-native/pull/823#discussion_r673545627
##
File path: netcore/NetCore.Test/CacheFactoryUnitTest.cs
##
@@ -0,0 +1,81 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System;
+using Apache.Geode.Client;
+using Xunit;
+
+namespace GeodeDotNetTest {
Review comment:
Fixed.
--
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
> Initial revision of .net core support
> -
>
> Key: GEODE-9360
> URL: https://issues.apache.org/jira/browse/GEODE-9360
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
>
> As a .net core developer, I would like to be able to access the geode-native
> API. To facilitate this, we need to implement a minimal set of C# classes
> that use p/invoke to access geode-native via C bindings (GEODE-9358).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9443) Increase kernel.pid_max in CI images
Dale Emery created GEODE-9443:
-
Summary: Increase kernel.pid_max in CI images
Key: GEODE-9443
URL: https://issues.apache.org/jira/browse/GEODE-9443
Project: Geode
Issue Type: Test
Components: tests
Reporter: Dale Emery
Certain Geode tests create a lot of threads. When these tests run in parallel
with many other tests (as they do in CI), the whole set of concurrently running
tests can overwhelm the Linux kernel's ability to assign PIDs to new threads.
When this happens, test processes, Gradle processes, and other processes can
become unable to create new threads.
The relevant system parameter is {{kernel.pid_max}}. On our CI systems,
{{pid_max}} is 98,304.
Raising {{pid_max}} to 983040 (10x the default value). A build can run 24
concurrent instances of even our most thread-heavy tests without exceeding this
threshold.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (GEODE-9443) Increase kernel.pid_max in CI images
[
https://issues.apache.org/jira/browse/GEODE-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery reassigned GEODE-9443:
-
Assignee: Dale Emery
> Increase kernel.pid_max in CI images
>
>
> Key: GEODE-9443
> URL: https://issues.apache.org/jira/browse/GEODE-9443
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
>
> Certain Geode tests create a lot of threads. When these tests run in parallel
> with many other tests (as they do in CI), the whole set of concurrently
> running tests can overwhelm the Linux kernel's ability to assign PIDs to new
> threads. When this happens, test processes, Gradle processes, and other
> processes can become unable to create new threads.
> The relevant system parameter is {{kernel.pid_max}}. On our CI systems,
> {{pid_max}} is 98,304.
> Raising {{pid_max}} to 983040 (10x the default value). A build can run 24
> concurrent instances of even our most thread-heavy tests without exceeding
> this threshold.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-9443) Increase kernel.pid_max in CI images
[
https://issues.apache.org/jira/browse/GEODE-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-9443:
--
Labels: GeodeOperationAPI pull-request-available (was: GeodeOperationAPI)
> Increase kernel.pid_max in CI images
>
>
> Key: GEODE-9443
> URL: https://issues.apache.org/jira/browse/GEODE-9443
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
>
> Certain Geode tests create a lot of threads. When these tests run in parallel
> with many other tests (as they do in CI), the whole set of concurrently
> running tests can overwhelm the Linux kernel's ability to assign PIDs to new
> threads. When this happens, test processes, Gradle processes, and other
> processes can become unable to create new threads.
> The relevant system parameter is {{kernel.pid_max}}. On our CI systems,
> {{pid_max}} is 98,304.
> Raising {{pid_max}} to 983040 (10x the default value). A build can run 24
> concurrent instances of even our most thread-heavy tests without exceeding
> this threshold.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-9442) CI Failure: acceptance-test-openjdk8 timed out
Eric Shu created GEODE-9442: --- Summary: CI Failure: acceptance-test-openjdk8 timed out Key: GEODE-9442 URL: https://issues.apache.org/jira/browse/GEODE-9442 Project: Geode Issue Type: Bug Components: redis Reporter: Eric Shu This acceptance-test-openjdk8 failed due to timeout. https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/acceptance-test-openjdk8/builds/88 It does not appear to be one particular test hang -- as all running tests are finished showing status of SUCCESS. However, it shows that gradle no able to shut down one test worker: in daemon-4088.out.log under .gradle_logs directory following exception was seen: Daemon is stopping immediately stop command received Daemon vm is shutting down... The daemon has exited normally or was terminated in response to a user interrupt. failed to abort Gradle Test Executor 143 org.gradle.process.internal.ExecException: A problem occurred waiting for process 'Gradle Test Executor 143' to complete. at org.gradle.process.internal.DefaultExecHandle.execExceptionFor(DefaultExecHandle.java:241) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:218) at org.gradle.process.internal.DefaultExecHandle.failed(DefaultExecHandle.java:369) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:87) at org.gradle.internal.operations.CurrentBuildOperationPreservingRunnable.run(CurrentBuildOperationPreservingRunnable.java:42) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.remove(ApplicationShutdownHooks.java:82) at java.lang.Runtime.removeShutdownHook(Runtime.java:239) at org.gradle.process.internal.shutdown.ShutdownHooks.removeShutdownHook(ShutdownHooks.java:33) at org.gradle.process.internal.DefaultExecHandle.setEndStateInfo(DefaultExecHandle.java:208) at org.gradle.process.internal.DefaultExecHandle.aborted(DefaultExecHandle.java:365) at org.gradle.process.internal.ExecHandleRunner.completed(ExecHandleRunner.java:108) at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:84) ... 7 more Also, in geode-apis-compatible-with-redis/build/test-results/acceptanceTest/binary output.bin file that Redis container was started but no further information for its shutdown. No sure if this is normal or not. ^A<9c>^H^@<8a>^A[info 2021/07/20 16:55:00.011 UTC tid=0xa] Ryuk started - will monitor and terminate Testcontainers containers on JVM exit ^A<9c>^H^@^A ^A<9c>^H^@Q[info 2021/07/20 16:55:00.012 UTC tid=0xa] Checking the system... ^A<9c>^H^@^A ^A<9c>^H^@p[info 2021/07/20 16:55:00.013 UTC tid=0xa] â<9c><94>ï¸<8e> Docker server version should be at least 1.6.0 ^A<9c>^H^@^A ^A<9c>^H^@~[info 2021/07/20 16:55:00.142 UTC tid=0xa] â<9c><94>ï¸<8e> Docker environment should have more than 2GB free disk space ^A<9c>^H^@^A ^A<9c>^H^@d[info 2021/07/20 16:55:00.161 UTC tid=0xa] Creating container for image: redis:5.0.6 ^A<9c>^H^@^A ^A<9c>^H^@<97>^A[info 2021/07/20 16:55:00.218 UTC tid=0xa] Starting container with ID: 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 ^A<9c>^H^@^A ^A<9c>^H^@<9e>^A[info 2021/07/20 16:55:00.658 UTC tid=0xa] Container redis:5.0.6 is starting: 3d1530c27f0b4f6e526bfc48b8232708abd3e0de55f188c74e007db30a19d634 ^A<9c>^H^@^A ^A<9c>^H^@d[info 2021/07/20 16:55:00.789 UTC tid=0xa] Container redis:5.0.6 started in PT0.644S ^A<9c>^H^@^A ^A<9c>^H^@r[info 2021/07/20 16:55:00.791 UTC tid=0xa] Started redis container with exposed port 6379 -> 33290 Someone has more knowledge of redis container should take a look and determine if it is an real issue or not. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9438) NC user guides: Delete obsolete Auth properties
[ https://issues.apache.org/jira/browse/GEODE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Barnes resolved GEODE-9438. Fix Version/s: 1.12.3 1.13.3 1.15.0 1.14.0 Resolution: Fixed > NC user guides: Delete obsolete Auth properties > --- > > Key: GEODE-9438 > URL: https://issues.apache.org/jira/browse/GEODE-9438 > Project: Geode > Issue Type: Bug > Components: docs, native client >Affects Versions: 1.13.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > Fix For: 1.14.0, 1.15.0, 1.13.3, 1.12.3 > > > Native client user guides (both .NET and C++) still include three obsolete > auth-related system properties: > security-client-auth-factory > security-client-auth-library > security-client-dhalgo > These should be deleted from the documentation. > Note: Functionality of the first two has been superseded by > SetAuthInitialize(). Examples showing its usage have already been included in > the docs. > Pages in which these properties appear include: > .NET: > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html > C++: > https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-9441) The NestedFunctionExecutionDistributedTest uses too many threads
[
https://issues.apache.org/jira/browse/GEODE-9441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery resolved GEODE-9441.
---
Fix Version/s: 1.15.0
Resolution: Fixed
> The NestedFunctionExecutionDistributedTest uses too many threads
>
>
> Key: GEODE-9441
> URL: https://issues.apache.org/jira/browse/GEODE-9441
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Barrett Oglesby
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI, pull-request-available
> Fix For: 1.15.0
>
>
> The {{NestedFunctionExecutionDistributedTest}} uses {{OperationExecutors
> MAX_FE_THREADS}} to configure both client function invocations and cache
> server max connections.
> It uses MAX_FE_THREADS * 2 for function executions which use Function
> Execution Processor threads:
> {noformat}
> client.invoke(() -> executeFunction(new ParentFunction(), MAX_FE_THREADS *
> 2));
> {noformat}
> And potentially MAX_FE_THREADS * 3 for client connections which use
> ServerConnection threads:
> {noformat}
> cacheServer.setMaxConnections(Math.max(CacheServer.DEFAULT_MAX_CONNECTIONS,
> MAX_FE_THREADS * 3));
> {noformat}
> MAX_FE_THREADS was changed recently to:
> {noformat}
> Math.max(Runtime.getRuntime().availableProcessors() * 16, 16))
> {noformat}
> It doesn't need to use this many threads to test the behavior it is testing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9438) NC user guides: Delete obsolete Auth properties
[ https://issues.apache.org/jira/browse/GEODE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384511#comment-17384511 ] ASF subversion and git services commented on GEODE-9438: Commit d92ed121ac6cbc60441bd3b808f3591155a9bf04 in geode-native's branch refs/heads/support/1.12 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d92ed12 ] GEODE-9438: NC user guides - Delete obsolete Auth properties (#832) > NC user guides: Delete obsolete Auth properties > --- > > Key: GEODE-9438 > URL: https://issues.apache.org/jira/browse/GEODE-9438 > Project: Geode > Issue Type: Bug > Components: docs, native client >Affects Versions: 1.13.3 >Reporter: Dave Barnes >Assignee: Dave Barnes >Priority: Major > Labels: pull-request-available > > Native client user guides (both .NET and C++) still include three obsolete > auth-related system properties: > security-client-auth-factory > security-client-auth-library > security-client-dhalgo > These should be deleted from the documentation. > Note: Functionality of the first two has been superseded by > SetAuthInitialize(). Examples showing its usage have already been included in > the docs. > Pages in which these properties appear include: > .NET: > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html > C++: > https://gemfire-native-cpp.docs.pivotal.io/102/geode-native-client-cpp/configuring/sysprops.html > https://gemfire-native-dotnet.docs.pivotal.io/102/geode-native-client-dotnet/security/security-systemprops.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (GEODE-9443) Increase kernel.pid_max in CI images
[
https://issues.apache.org/jira/browse/GEODE-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale Emery updated GEODE-9443:
--
Labels: GeodeOperationAPI (was: )
> Increase kernel.pid_max in CI images
>
>
> Key: GEODE-9443
> URL: https://issues.apache.org/jira/browse/GEODE-9443
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Dale Emery
>Assignee: Dale Emery
>Priority: Major
> Labels: GeodeOperationAPI
>
> Certain Geode tests create a lot of threads. When these tests run in parallel
> with many other tests (as they do in CI), the whole set of concurrently
> running tests can overwhelm the Linux kernel's ability to assign PIDs to new
> threads. When this happens, test processes, Gradle processes, and other
> processes can become unable to create new threads.
> The relevant system parameter is {{kernel.pid_max}}. On our CI systems,
> {{pid_max}} is 98,304.
> Raising {{pid_max}} to 983040 (10x the default value). A build can run 24
> concurrent instances of even our most thread-heavy tests without exceeding
> this threshold.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[
https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384542#comment-17384542
]
ASF GitHub Bot commented on GEODE-9360:
---
pdxcodemonkey commented on a change in pull request #823:
URL: https://github.com/apache/geode-native/pull/823#discussion_r673582416
##
File path: netcore/NetCore.Test/CacheFactoryUnitTest.cs
##
@@ -0,0 +1,81 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System;
+using Apache.Geode.Client;
+using Xunit;
+
+namespace GeodeDotNetTest {
+ [Collection("Geode .net Core Collection")]
+ public class CacheFactoryUnitTests {
Review comment:
Everything is now singular `Test`, and I removed `Unit` from all the
class names and renamed the files appropriately.
--
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
> Initial revision of .net core support
> -
>
> Key: GEODE-9360
> URL: https://issues.apache.org/jira/browse/GEODE-9360
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
>
> As a .net core developer, I would like to be able to access the geode-native
> API. To facilitate this, we need to implement a minimal set of C# classes
> that use p/invoke to access geode-native via C bindings (GEODE-9358).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9360) Initial revision of .net core support
[
https://issues.apache.org/jira/browse/GEODE-9360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384543#comment-17384543
]
ASF GitHub Bot commented on GEODE-9360:
---
pdxcodemonkey commented on a change in pull request #823:
URL: https://github.com/apache/geode-native/pull/823#discussion_r673582739
##
File path: netcore/NetCore/Cache.cs
##
@@ -0,0 +1,170 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+using System;
+using System.Collections.Generic;
+using System.Runtime.CompilerServices;
+using System.Runtime.InteropServices;
+
+namespace Apache {
Review comment:
Totally - love that we can concatenate these in C#.
--
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
> Initial revision of .net core support
> -
>
> Key: GEODE-9360
> URL: https://issues.apache.org/jira/browse/GEODE-9360
> Project: Geode
> Issue Type: Improvement
> Components: native client
>Reporter: Blake Bender
>Priority: Major
> Labels: pull-request-available
>
> As a .net core developer, I would like to be able to access the geode-native
> API. To facilitate this, we need to implement a minimal set of C# classes
> that use p/invoke to access geode-native via C bindings (GEODE-9358).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-9439) Convert CertifacteBuilder to sun/jdk APIs
[
https://issues.apache.org/jira/browse/GEODE-9439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17384620#comment-17384620
]
ASF subversion and git services commented on GEODE-9439:
Commit d77cb31c85112a1ffadb6d2a152b4627216ccc97 in geode's branch
refs/heads/develop from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d77cb31 ]
GEODE-9439: Convert CertificateBuilder to sun/jdk APIs (#6707)
- Makes it easier to de/serialize created certificates
- Remove the requirement for the Bouncy Castle library
- Suppress deprecated API warnings during compile
- Make CertificateMaterial Serializable
> Convert CertifacteBuilder to sun/jdk APIs
> -
>
> Key: GEODE-9439
> URL: https://issues.apache.org/jira/browse/GEODE-9439
> Project: Geode
> Issue Type: Test
> Components: tests
>Reporter: Jens Deppe
>Priority: Major
> Labels: pull-request-available
>
> The {{CertificateBuilder}} test utility uses Bouncy Castle APIs to build CA
> and regular certs for test purposes. In some cases it is desirable for these
> certificates to be serializable. In such cases it is also required that the
> BC security provider have a higher priority than the standard java one
> otherwise the deserialized certificates are not usable.
> It would be less trouble to just use standard jdk APIs to build these
> certificates. Although no {{X509}} APIs are public/documented they are well
> used throughout the JDK. For example the {{keytool}} utility. Java 9
> introduces its own {{CertificateBuilder}} API which could eventually replace
> this one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
