4 Patch |
13 Review |
1eccb2bc1ff69817b2fc8d16a4707b64d8b514e7,
ebb59dd7cf0c4fb4a9d9135cf6442e59c109de31,
2a721e7b058025f42f8b86c8a2ecd851c2790f00,
e8c2b94b6f106e276800aa3de2628a73a70ac5e6 |
49a0f0111c241855823ed6ab3f751691177f4a7a,
9fa2c28dc2d701b7b2cc90d4282f05ee1a221943,
87e4f31e30f6a89f1c17b5a9eb6406208e384d51,
e7f7a593427f83ff7a256d91ee48bbb8380bc788,
8762267b13fffb921ae79b0220630f10695ee9d9,
493ddae492a9a9a47bc484a7dfa75ef86fd3d9b8,
ad9462ee737ebc92a86cb5b266fccdd93e1111a9,
ec84618b7450ef9357a3a88fc93e39d74a34b02e,
7ed2daf38699fa9555feb9049c1c27a410f1520e,
4ca24701e105226ca35da1adc7ff70b56a36fce2,
7ed96792878ed87340bde0224db0923777490f32,
b6a7a2db24bcdc139d08928ec08cafd30c9a4c10,
8eff3855117b37d304711ce182edc516ea0fbd35 |
1eccb2bc1ff69817b2fc8d16a4707b64d8b514e7 | Author: ningzi.zhan <ningzi.zhan@datastax.com>
| 2023-06-08 14:59:17-07:00
Fix error message handling when trying to use CLUSTERING ORDER with non-clustering column
Patch by Ningzi Zhan and Tomasz Lasica; reviewed by brandonwilliams,
edimitrova and Maxwell Guo for CASSANDRA-17818
Co-Authored-By: Tomek Lasica <tomasz.lasica@datastax.com>
4ca24701e105226ca35da1adc7ff70b56a36fce2 | Author: Mick Semb Wever <mck@apache.org>
| 2021-04-11 12:34:41+02:00
Split dockerised test runs into parallel docker container runs
Improvements
- build arm64 docker images on-the-fly (they are not deployed anywhere yet)
- only pull the docker images if they are not found locally (saves time!)
- return internal exit codes
- configure apt to retry on network failures
- avoid running empty test splits
- remove per-agent throttle (as they are now dockerised)
patch by Mick Semb Wever; reviewed by Tomek Łasica for CASSANDRA-16604
493ddae492a9a9a47bc484a7dfa75ef86fd3d9b8 | Author: Bereng <berenguerblasi@gmail.com>
| 2021-02-18 11:46:32+00:00
Add test to verify that a node can join when RF > N in multi-DC
patch by Berenguer Blasi; reviewed by Andrés de la Peña, Ekaterina Dimitrova and Tomasz Lasica for CASSANDRA-16296
87e4f31e30f6a89f1c17b5a9eb6406208e384d51 | Author: Bereng <berenguerblasi@gmail.com>
| 2021-02-18 11:42:24+00:00
Fix node unable to join when RF > N in multi-DC with added warning
patch by Berenguer Blasi; reviewed by Andrés de la Peña, Ekaterina Dimitrova and Tomasz Lasica for CASSANDRA-16296
8762267b13fffb921ae79b0220630f10695ee9d9 | Author: Bereng <berenguerblasi@gmail.com>
| 2021-02-15 08:13:22+01:00
Add explicit DC to tests where we have multidc setup
patch by Berenguer Blasi; reviewed by Ekaterina Dimitrova, Tomek Łasica, Andres de la Peña for CASSANDRA-16411
e7f7a593427f83ff7a256d91ee48bbb8380bc788 | Author: jacek-lewandowski <jacek.lewandowski@datastax.com>
| 2021-02-09 17:23:21+01:00
Fix Cassandra version families, and more…
- Remove OVERRIDE_MANIFEST, as it is unused.
- Upgrade manifest, remove upgrades from unsupported indev versions, and remove upgrades to current if indev is still supported.
- Correct the enforced protocol version to use v3 for 2.2/3.0 upgrades. (ref: CASSANDRA-15193)
- Fix broken thrift_upgrade_test.py
- Fix upgrade_udtfix_test.py (not applicable before 3.11.6, ref: CASSANDRA-15035)
- Remove hardcoded references to gitbox.a.o
- Remove unnecessary implicit upgrade scenarios. `--upgrade-target-version-only` only tests upgrades from the target version and to the target version, i.e. those upgrade paths where the target (indev) version was the origin or destination version. Previously the filter was applied only for the version family but not on the variant, pulling in completely unrelated upgrade scenarios.
patch by Jacek Lewandowski; reviewed by Tomek Łasica, Mick Semb Wever for CASSANDRA-16433
ad9462ee737ebc92a86cb5b266fccdd93e1111a9 | Author: Bereng <berenguerblasi@gmail.com>
| 2021-02-02 08:28:10+01:00
Add explicit DC to tests where we have multidc setup
patch by Berenguer Blasi, reviewed by Tomasz Lasica, Andres de la Peña and Ekaterina Dimitrova for CASSANDRA-16411
b6a7a2db24bcdc139d08928ec08cafd30c9a4c10 | Author: Mick Semb Wever <mck@apache.org>
| 2021-01-23 11:32:06+01:00
Jenkins builds to provide link to nightlies archive, and remove the Jenkins plaintext reports
Also add aggregated xml reports to the test jobs, and archive them to nightlies.a.o
patch by Mick Semb Wever; reviewed by Tomek Łasica for CASSANDRA-16401
9fa2c28dc2d701b7b2cc90d4282f05ee1a221943 | Author: Mick Semb Wever <mck@apache.org>
| 2021-01-23 11:18:46+01:00
Jenkins builds to provide link to nightlies archive, and remove the Jenkins plaintext reports
patch by Mick Semb Wever; reviewed by Tomek Łasica for CASSANDRA-16401
ec84618b7450ef9357a3a88fc93e39d74a34b02e | Author: jacek-lewandowski <jacek.lewandowski@datastax.com>
| 2021-01-22 08:55:28+01:00
Listing tests (--collect-only and --dtest-print-tests-only) only lists tests that will run according to other arguments specified
This patch fixes behaviour for both `run_dtests.py` and `pytest`.
- Error handling for invalid parameter values / combinations is in a single place (`dtest_config.py`) and is executed before we actually traverse through the tests
- We exit with just a clean error message instead of tons of spam
- `run_dtests.sh` will not loose the exit code of `pytest` any more so we can clearly detect when test cases collection fails
- removed a bit of boilerplate code from `run_dtests.py`, e.g. what it did with xml processing is simply provided with `-q` argument of `pytest`
- tests filtering has been refactored to be cleaner
- fixed filtering of resource intensive tests and other tests (note that except for upgrade tests, we took care only about test method annotations - module level annotations were ignored for vnodes, no_vnodes, no_offheap_memtables and resource_intensive, ...)
- added meta_tests for the filtering and parsing exception handling
- added special parameter --metatests which is enough to run all the meta tests
- fixed Travis configuration so that it runs meta tests
Note that now `run_dtests.py` seems to be redundant. If we need it only for listing dtests, we can simply achieve exactly the same effect using `--collect-only -q --ignore=meta_tests` arguments for `pytest` instead of `--dtest-print-tests-only`, plus we need to filter output with `grep '.py::'` (in order to not include the summary line) and pipe stdout to the target file. It is now simplified so `run_dtests.sh` just uses `pytest` with those arguments.
patch by Jacek Lewandowski; reviewed by Tomek Łasica and Mick Semb Wever for CASSANDRA-16399
e8c2b94b6f106e276800aa3de2628a73a70ac5e6 | Author: Tomek Lasica <tomasz.lasica@datastax.com>
| 2021-01-18 20:47:09+01:00
Explicit node start timeouts
Some tests require longer start timeout than default 90s:
* bootstrap with reset state
* node replacement
* cdc tests (due to checks for other seeds connectivity)
Before: use default timeout, 90s or rather 600s (due to bug in ccm)
After: use explicit timeout per test case: 120s or 180s
patch by Tomek Lasica; reviewed by Mick Semb Wever for CASSANDRA-16395
8eff3855117b37d304711ce182edc516ea0fbd35 | Author: Mick Semb Wever <mck@apache.org>
| 2020-12-26 19:20:24+01:00
Add microbench as a target in cassandra-test.sh, and as a jenkins job
The jenkins jmh report plugin needs the jmh-result.json remaining.
patch by Mick Semb Wever; reviewed by Tomek Łasica for CASSANDRA-16371