-
Notifications
You must be signed in to change notification settings - Fork 684
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade tests with the flaky detection #6804
Comments
JelteF
added a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804
JelteF
added a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804
JelteF
added a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804
JelteF
added a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804
JelteF
added a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804
JelteF
added a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804
agedemenli
pushed a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804 (cherry picked from commit a0625b3)
JelteF
added a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804
agedemenli
pushed a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804 (cherry picked from commit 72a7898)
JelteF
added a commit
that referenced
this issue
Mar 31, 2023
For some tests such as upgrade tests and arbitrary config tests we set up the citus cluster using Python. This setup is slightly different from the perl based setup script (`multi_regress.pl`). Most importantly it uses replication factor 1 by default. This changes our run_test.py script to be able to run a schedule using python instead of `multi_regress.pl`, for the tests that require it. For now arbitrary config tests are still not runnable with `run_test.py`, but this brings us one step closer to being able to do that. Fixes #6804
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrade tests do not work well with the flakiness detection.
An example: #6794
Here it is trying to run the before test once and the after test 8 times. The first failure is in the before test due to replication factor > 1
The text was updated successfully, but these errors were encountered: