Closed tchaikov closed 1 year ago
only for testing the CCM CI test using Nix.
tested using
$ scripts/dbuild_collect_so.sh ~/dev/scylladb/build/cmake/scylla /tmp/dynamic_libs_for_dtest
$ SCYLLA_DBUILD_SO_DIR=/tmp/dynamic_libs_for_dtest JAVA_HOME=/usr/lib/jvm/jre-11 pytest --cassandra-dir $HOME/dev/scylladb/build/cmake scylla_sstable_test.py::TestScyllaSstableDumpData::test_scylla_sstable_basic
not really a dbuild build. but i also verified by checking the env variables manually.
I'll for @bhalevy to confirm, as the one that was hit by this issue, to validate it's solving it
I'll for @bhalevy to confirm, as the one that was hit by this issue, to validate it's solving it
@fruch Israel, Benny approved a superset of this change. see #501. but it introduced a regression identified by the ccm's own unit tests. so i abandoned it.
if scylla is built in a dtest environment,
nit: s/dtest/dbuild/
and the shared libraries which it is linked against cannot be found in the testbed's default ld.so.conf paths, the tests which run scylla-sstable would fail.
so, in this change. let's apply the
self._launch_env
when running scylla-sstable as well. previously, these env variables are only applied when launching scylla as a daemon.
if scylla is built in a dtest environment, and the shared libraries which it is linked against cannot be found in the testbed's default ld.so.conf paths, the tests which run scylla-sstable would fail.
so, in this change. let's apply the
self._launch_env
when running scylla-sstable as well. previously, these env variables are only applied when launching scylla as a daemon.