Re: [PATCH 2/3] t6050: redirect expected error output to /dev/null
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Mar 28, 2019, 18:41 UTC
- Message-ID
- <CAPig+cSj5WZeGy4nwgafGtBbz7y921M8H57eFbBXwRy2Bm-C+g@mail.gmail.com>
- In-Reply-To
- <20190328171722.9753-2-chriscool@tuxfamily.org>
On Thu, Mar 28, 2019 at 1:17 PM Christian Couder <christian.couder@gmail.com> wrote:
Show 9 quoted lines
> Otherwise the error from `git rev-parse` is uselessly > polluting the debug output. > > Signed-off-by: Christian Couder <chriscool@tuxfamily.org> > --- > diff --git a/t/t6050-replace.sh b/t/t6050-replace.sh > @@ -40,7 +40,7 @@ commit_peeling_shows_parents () > - test_must_fail git rev-parse --verify $_commit^$_parent_number > + test_must_fail git rev-parse --verify $_commit^$_parent_number 2>/dev/null
When I'm debugging test failures, I find it very helpful to see that a command which was expected to fail did indeed fail with the expected error message, so I don't consider such a message as "uselessly polluting the debug output". Consequently, I'm rather negative on this change.