tests: don't swallow stderr when running babeltrace CLI
authorSimon Marchi <simon.marchi@efficios.com>
Wed, 3 Jul 2019 19:23:15 +0000 (15:23 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Thu, 18 Jul 2019 15:53:34 +0000 (11:53 -0400)
commit1ec8b5b54448c9cdeb430463a81ea0242d280ebf
tree631a360e85c1e036c549e1a3c82e5f4fe67a9238
parentcd03c43c9c60177a6b0cb2496a784bfefca9740f
tests: don't swallow stderr when running babeltrace CLI

I have found it very difficult to investigate failing tests if we don't
show stderr, so I suggest we just let it get printed.  Some tests are
expected to print to stderr in their normal course of operation (because
they test babeltrace error cases), so it means there will be some
additional output in a normal test run.  But I think it's a fair
trade-off.

Change-Id: Ia9bc5a706dd756ce0c9d1be4fec7510b12dface7
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/1609
CI-Build: Philippe Proulx <eeppeliteloop@gmail.com>
Tested-by: jenkins <jenkins@lttng.org>
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>
tests/utils/utils.sh
This page took 0.036436 seconds and 4 git commands to generate.