Tim Burke 84ff0aef28 Only really destroy instances on new-enough liberasurecode ... On liberasurecode 1.6.4 and earlier, it's unsafe to destroy instances (at least, those using the built-in backend). This is currently leading to intermittent gate failures for Swift. Related-Change: https://review.opendev.org/c/openstack/liberasurecode/+/929193 Related-Change: https://review.opendev.org/c/openstack/pyeclib/+/930171 Change-Id: I7e78fe6461de34ad3619ad506bc9277e64713716		2024-10-23 16:19:53 -07:00
..
test_files	Added end-to-end testing of PyECLib that uses command-line encoder and decoder.	2013-09-30 00:21:24 -07:00
__init__.py	Initial import of re-factoring the unit tests to exist in a central location	2014-06-04 15:50:00 -06:00
ec_pyeclib_file_test.sh	Clean up extra spaces	2021-09-15 02:05:47 -04:00
run_core_tests_manual_valgrind.py	test: Run core tests only once	2015-02-25 09:45:29 -07:00
run_core_tests_manual.py	Fix gate	2023-05-01 08:49:55 -07:00
test_pyeclib_api.py	Merge "Add a multi-threaded test"	2024-10-22 18:37:26 +00:00
test_pyeclib_c.py	Only really destroy instances on new-enough liberasurecode	2024-10-23 16:19:53 -07:00