From a16593272c497b60a3cccad7fe5b9c7b2eede11b Mon Sep 17 00:00:00 2001
From: Paul Cristian Sarbu <paul.cristian.sarbu@huawei.com>
Date: Tue, 10 Jan 2023 15:55:27 +0100
Subject: Tests: Fix stderr printout bug in just-mr usage

All desired outputs of just-mr (e.g., the config file after a setup call)
are printed to stdout, while all logging messages are printed to stderr.
Therefore, one should avoid explicitly piping stderr to stdout, as this
can break the intended use of just-mr.
---
 test/end-to-end/remote-execution/native-protocol.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/end-to-end/remote-execution/native-protocol.sh b/test/end-to-end/remote-execution/native-protocol.sh
index bef83e46..68667dad 100644
--- a/test/end-to-end/remote-execution/native-protocol.sh
+++ b/test/end-to-end/remote-execution/native-protocol.sh
@@ -67,7 +67,7 @@ cat > TARGETS <<EOF
 }
 EOF
 
-readonly CONF="$("${JUST_MR}" -C repos.json --local-build-root="${LBRDIR}" setup 2>&1)"
+readonly CONF="$("${JUST_MR}" -C repos.json --local-build-root="${LBRDIR}" setup)"
 
 NAME="native"
 ARGS=""
-- 
cgit v1.2.3