From: "Joachim Schmitz" <jojo@schmitz-digital.de>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>,
"'Johannes Sixt'" <j.sixt@viscovery.net>
Cc: <git@vger.kernel.org>
Subject: RE: make test
Date: Wed, 17 Oct 2012 10:30:11 +0200 [thread overview]
Message-ID: <002901cdac41$a0d381c0$e27a8540$@schmitz-digital.de> (raw)
In-Reply-To:
> From: Joachim Schmitz [mailto:jojo@schmitz-digital.de]
> Sent: Monday, October 15, 2012 3:18 PM
> To: 'Andreas Schwab'; 'Johannes Sixt'
> Cc: 'git@vger.kernel.org'
> Subject: RE: make test
>
> > From: Andreas Schwab [mailto:schwab@linux-m68k.org]
> > Sent: Monday, October 15, 2012 2:35 PM
> > To: Johannes Sixt
> > Cc: Joachim Schmitz; git@vger.kernel.org
> > Subject: Re: make test
> >
> > Johannes Sixt <j.sixt@viscovery.net> writes:
> >
> > > Am 10/15/2012 13:58, schrieb Joachim Schmitz:
> > >> ++ mkdir failing-cleanup
> > >> ++ cd failing-cleanup
> > >> ++ cat
> > >> ++ chmod +x failing-cleanup.sh
> > >> ++ test_must_fail ./failing-cleanup.sh
> > >> + eval_ret=1
> > >
> > > I wonder why the log does not show the commands of function
> > > test_must_fail.
> >
> > That's because stderr is redirected.
> >
>
> cat err
> ++ ./failing-cleanup.sh
> ++ exit_code=0
> ++ test 0 = 0
> ++ echo 'test_must_fail: command succeeded: ./failing-cleanup.sh'
> test_must_fail: command succeeded: ./failing-cleanup.sh
> ++ return 1
That test (as well as quite a few more) do pass when using bash rather than our sh (which really is a ksh)
Bye, Jojo
next prev parent reply other threads:[~2012-10-17 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 10:36 make test Joachim Schmitz
2012-10-15 10:53 ` Johannes Sixt
2012-10-15 11:00 ` Joachim Schmitz
2012-10-15 11:18 ` Johannes Sixt
2012-10-15 11:37 ` Joachim Schmitz
2012-10-15 11:52 ` Johannes Sixt
2012-10-15 11:58 ` Joachim Schmitz
2012-10-15 12:09 ` Johannes Sixt
2012-10-15 12:34 ` Andreas Schwab
2012-10-15 13:18 ` Joachim Schmitz
2012-10-17 8:30 ` Joachim Schmitz [this message]
2012-10-15 13:18 ` Joachim Schmitz
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 14:19 Joachim Schmitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002901cdac41$a0d381c0$e27a8540$@schmitz-digital.de' \
--to=jojo@schmitz-digital.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).