Am 26.06.2018 um 20:14 schrieb Eric Sunshine:
On Tue, Jun 26, 2018 at 2:06 PM Johannes Sixt wrote:
Hence, these lines should actually be
p4 help client &&
! p4 help nosuchcommand
Thanks for the comment; you're right, of course. I'll certainly make
this
On Tue, Jun 26, 2018 at 2:06 PM Johannes Sixt wrote:
> Am 26.06.2018 um 11:21 schrieb Eric Sunshine:
> >> On Tue, Jun 26, 2018 at 12:29 AM, Eric Sunshine
> >> wrote:
> >>> + p4 help client &&
> >>> + test_must_fail p4 help nosuchcommand
> > [...] So, despite
> > the
Am 26.06.2018 um 11:21 schrieb Eric Sunshine:
On Tue, Jun 26, 2018 at 4:58 AM Elijah Newren wrote:
On Tue, Jun 26, 2018 at 12:29 AM, Eric Sunshine wrote:
+ p4 help client &&
+ test_must_fail p4 help nosuchcommand
same question?
Same answer. Not shown in this
On Tue, Jun 26, 2018 at 4:58 AM Elijah Newren wrote:
> On Tue, Jun 26, 2018 at 12:29 AM, Eric Sunshine
> wrote:
> > [...] Therefore,
> > replace the manual exit code management with test_must_fail() and a
> > normal &&-chain.
> >
> > Signed-off-by: Eric Sunshine
> > ---
> > diff --git
On Tue, Jun 26, 2018 at 12:29 AM, Eric Sunshine wrote:
> These tests intentionally break the &&-chain to manually check the exit
> code of invoked commands which they expect to fail, and invert that
> local expected failure into a successful exit code for the test overall.
> Such manual exit code
On 26 June 2018 at 08:29, Eric Sunshine wrote:
> These tests intentionally break the &&-chain to manually check the exit
> code of invoked commands which they expect to fail, and invert that
> local expected failure into a successful exit code for the test overall.
> Such manual exit code
These tests intentionally break the &&-chain to manually check the exit
code of invoked commands which they expect to fail, and invert that
local expected failure into a successful exit code for the test overall.
Such manual exit code manipulation predates the invention of
test_must_fail().
An
7 matches
Mail list logo