Discussed privately with Max.
Discussion results provided at the slack channel [1].
[1] https://the-asf.slack.com/archives/C016F4PS8KV/p1595336751234500
On Wed, Jul 15, 2020 at 3:59 PM Max Shonichev wrote:
> Anton, Nikolay,
>
> I want to share some more findings about ducktests I've stubmled up
Anton, Nikolay,
I want to share some more findings about ducktests I've stubmled upon
during porting them to Tiden.
First problem was that GridGain Tiden-based tests by default use real
production-like configuration for Ignite nodes, notably:
- persitence enabled
- ~120 caches in ~40 gro
Anton,
I've prepared a PoC of running Tiden in dockerized environment.
The code is in fork of your repo at
https://github.com/mshonichev/ignite.git, branch 'ignite-ducktape',
module 'integration-tests.
Steps to run PoC are as follows:
```
$ mkdir -p $HOME/tiden_poc
$ cd $HOME/tiden_poc
$ gi
> Have you had a chance to deploy ducktests in bare metal?
Working on servers obtaining.
On Thu, Jul 9, 2020 at 10:11 AM Max Shonichev wrote:
> Anton,
>
> well, strange thing, but clean up and rerun helped.
>
>
> Ubuntu 18.04
>
>
>
Anton,
well, strange thing, but clean up and rerun helped.
Ubuntu 18.04
SESSION REPORT (ALL TESTS)
ducktape version: 0.7.7
session_id: 2020-07-06--003
run time: 4 minutes 44.835 s
Nikolay,
Can you, please, write down your version of requirements so we can reach a
> consensus on that and therefore move to the discussion of the
> implementation?
I guess that Max's requirements quite similar to your requirements:
1. The framework should support deployment on hardware/dock
Max,
Thanks for the check!
> Is it OK for those tests to fail?
No.
I see really strange things at logs.
Looks like you have concurrent ducktests run started not expected services,
and this broke the tests.
Could you please clean up the docker (use clean-up script [1]).
Compile sources (use script
Hello, Maxim.
Thanks for writing down the minutes.
There is no such thing as «Nikolay team» on the dev-list.
I propose to focus on product requirements and what we want to gain from the
framework instead of taking into account the needs of some team.
Can you, please, write down your version of
Folks,
Please share the summary of that Slack conversation here for records once
you find common ground.
-
Denis
On Thu, Jul 2, 2020 at 3:22 AM Nikolay Izhikov wrote:
> Igniters.
>
> All who are interested in integration testing framework discussion are
> welcome into slack channel -
> https:
Igniters.
All who are interested in integration testing framework discussion are welcome
into slack channel -
https://join.slack.com/share/zt-fk2ovehf-TcomEAwiXaPzLyNKZbmfzw?cdn_fallback=2
> 2 июля 2020 г., в 13:06, Anton Vinogradov написал(а):
>
> Max,
> Thanks for joining us.
>
> > 1. ti
Max,
Thanks for joining us.
> 1. tiden can deploy artifacts by itself, while ducktape relies on
> dependencies being deployed by external scripts.
No. It is important to distinguish development, deploy, and orchestration.
All-in-one solutions have extremely limited usability.
As to Ducktests:
Dock
Hello, Maxim.
> 1. tiden can deploy artifacts by itself, while ducktape relies on
> dependencies being deployed by external scripts
Why do you think that maintaining deploy scripts coupled with the testing
framework is an advantage?
I thought we want to see and maintain deployment scripts separ
Anton, Nikolay,
Let's agree on what we are arguing about: whether it is about "like or
don't like" or about technical properties of suggested solutions.
If it is about likes and dislikes, then the whole discussion is
meaningless. However, I hope together we can analyse pros and cons
carefull
Folks,
First, I've created PR [1] with ducktests improvements
PR contains the following changes
- Pme-free switch proof-benchmark (2.7.6 vs master)
- Ability to check (compare with) previous releases (eg. 2.7.6 & 2.8)
- Global refactoring
-- benchmarks javacode simplification
-- services python an
Hello, Maxim.
Thank you for so detailed explanation.
Can we put the content of this discussion somewhere on the wiki?
So It doesn’t get lost.
I divide the answer in several parts. From the requirements to the
implementation.
So, if we agreed on the requirements we can proceed with the discussio
Greetings, Nikolay,
First of all, thank you for you great effort preparing PoC of
integration testing to Ignite community.
It’s a shame Ignite did not have at least some such tests yet, however,
GridGain, as a major contributor to Apache Ignite had a profound
collection of in-house tools to
Hello,
Branch with duck tape created -
https://github.com/apache/ignite/tree/ignite-ducktape
Any who are willing to contribute to PoC are welcome.
> 21 мая 2020 г., в 22:33, Nikolay Izhikov написал(а):
>
> Hello, Denis.
>
> There is no rush with these improvements.
> We can wait for Maxim
Hello, Denis.
There is no rush with these improvements.
We can wait for Maxim proposal and compare two solutions :)
> 21 мая 2020 г., в 22:24, Denis Magda написал(а):
>
> Hi Nikolay,
>
> Thanks for kicking off this conversation and sharing your findings with the
> results. That's the right ini
Hi Nikolay,
Thanks for kicking off this conversation and sharing your findings with the
results. That's the right initiative. I do agree that Ignite needs to have
an integration testing framework with capabilities listed by you.
As we discussed privately, I would only check if instead of
Confluen
Hello, Anton.
> Could you please explain how to perform testing on the different environments?
Different JDK:
1. We should prepare our environment and put the desired JDK in the known
locations. [/opt/jdk1.8, /opt/jdk11], for example.
2. We should parametrize test and just setup java environme
Nikolay,
Great proposal!
Could you please explain how to perform testing on the different
environments?
For Example, you provided a rebalance test.
Is it possible to perform this test with TDE enabled?
Is it possible to perform it on custom OS (eg. Windows)?
Is it possible to perform in on bare
21 matches
Mail list logo
