From c3b13b4932e26805100cfafc695eed822f7c3051 Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Thu, 23 Feb 2023 11:24:01 +0100 Subject: Enforce remote-execution unit tests ... now that they no longer depend on an external remote execution. --- test/utils/remote_execution/main-remote-execution.cpp | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'test/utils/remote_execution/main-remote-execution.cpp') diff --git a/test/utils/remote_execution/main-remote-execution.cpp b/test/utils/remote_execution/main-remote-execution.cpp index 952b025e..188d3eea 100644 --- a/test/utils/remote_execution/main-remote-execution.cpp +++ b/test/utils/remote_execution/main-remote-execution.cpp @@ -63,10 +63,8 @@ void wait_for_grpc_to_shutdown() { auto main(int argc, char* argv[]) -> int { ConfigureLogging(); - // In case remote execution address is not valid, we skip tests. This is in - // order to avoid tests being dependent on the environment. if (not ConfigureRemoteExecution()) { - return EXIT_SUCCESS; + return EXIT_FAILURE; } int result = Catch::Session().run(argc, argv); -- cgit v1.2.3