Hi,
Can you help me, how to simulate ipv6 in new integration test framework?
BR,
Mario
Šalje: Jacob Barrett
Poslano: 14. kolovoza 2019. 21:00:35
Prima: dev@geode.apache.org
Predmet: Re: geode-native ipv6
Can you build an integration test in the new framewor
Hi Geode dev,
I've opened ticket about mixing cache.xml and cluster configuration
https://issues.apache.org/jira/browse/GEODE-7025
According to some comments on tickets(
https://issues.apache.org/jira/browse/GEODE-6772?focusedCommentId=16869670&page=com.atlassian.jira.plugin.system.issuetabpanel
I can work with you on this if you're still blocked.
--Jens
On Tue, Aug 20, 2019 at 4:12 PM Kirk Lund wrote:
> Does anyone know how to debug geode-assembly Jetty dunit tests that fail to
> launch modify_war?
>
> It passes 100% locally in intellij and with gradle cli. It only fails in
> concours
Hi,
I have just added the following proposal in the wiki for discussion and would
like to get feedback from the community.
https://cwiki.apache.org/confluence/display/GEODE/%5BDiscussion%5D+Improvements+on+client+Function+execution+API
Problem
The client API for function execution is inconsist
There are several integration tests failing on Windows in our potential
branch for 1.9.1.
*Does anyone know if integration tests were GREEN on Windows in 1.9.0?*
AvailablePortHelperIntegrationTest and BackupIntegrationTest seem to fail
consistently on Windows. ServerLauncherRemoteFileIntegrationT
Hello Geode Dev Community,
We have created a new release branch for Apache Geode 1.9.1 - "release/1.9.1"
Currently it has the two fixes proposed previously[1][2] on the dev list, as
well as necessary CI updates for pipeline[3].
Please do review and raise any concern with the release branch.
If
Just to be clear between java and native-client api:
- Read timeout in function execution Java client API - This is to change
the java client behavior
And following are the native client problems and solution applies to
native-client?
- Timeout in ResultCollector::getResult() and Execution::execu
Build Update for apache/geode-examples
-
Build: #338
Status: Errored
Duration: 13 secs
Commit: 4eb6b07 (release/1.9.1)
Author: Owen Nichols
Message: Upgraded version number for releasing 1.9.1
View the changeset: https://github.com/apache/geode-examples/commit
Build Update for apache/geode-native
-
Build: #2053
Status: Failed
Duration: 1 hr, 34 mins, and 45 secs
Commit: add53da (release/1.9.1)
Author: Dave Barnes
Message: User Guide: Add a link to the official XSD declarative cache schema
View the changeset: https:/
Hi Alberto,
If you have added a file as part of your PR, please add the header as a
commit to your working branch and add that as part of the same PR. Your
branch should be able to pass a build, spotlessCheck, and unit tests as a
prerequisite for making a pull request.
Please follow up here if yo
Hi Helena,
I think the problem is that rat is currently broken on geode-native
develop.
-Dan
On Wed, Aug 21, 2019 at 2:55 PM Helena Bales wrote:
> Hi Alberto,
>
> If you have added a file as part of your PR, please add the header as a
> commit to your working branch and add that as part of the
Given the current types that gfsh supports, I don't see that it will be
lots of validation. We have the redundancy level to validate for the
REDUNDANT types. And we have HEAP_LRU and OVERFLOW to validate. That is it.
The only other thing is the partition only attributes should be rejected
when crea
You might start by updating the framework’s Cluster class accept a hostname
that would be used for both Locator and Server classes. Then in an IPv6 tests
you could set the hostname to '0:0:0:0:0:0:0:1’, which is the loopback address.
In theory this should work.
In Cluster.hpp:
Look for all the
13 matches
Mail list logo
