You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, as workaround, we have a DummyOsExecutor (in task TestRunnerDBTestTask) which is a fallback when the environment info is incomplete, which can happen if ITDE's SpawnTestEnvironment was launched for an external database. See exasol/integration-test-docker-environment#403
After the linked issue is fixed, we can remove the DummyOsExecutor and adapt the test DockerRunDBTestExternalDBTest, which then will need to manage the SSH file.
Background
Currently, as workaround, we have a
DummyOsExecutor
(in task TestRunnerDBTestTask) which is a fallback when the environment info is incomplete, which can happen if ITDE'sSpawnTestEnvironment
was launched for an external database. See exasol/integration-test-docker-environment#403After the linked issue is fixed, we can remove the DummyOsExecutor and adapt the test DockerRunDBTestExternalDBTest, which then will need to manage the SSH file.
Acceptance Criteria
DummyOsExecutor
in (in task TestRunnerDBTestTask)f"--db-os-access {DbOsAccess.SSH.name}"
forrun-db-test
commandrun-db-test
command the user and key-fileThe text was updated successfully, but these errors were encountered: