netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Kochan <vadim4j@gmail.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: Vadim Kochan <vadim4j@gmail.com>
Subject: Re: [PATCH iproute2] tests: Dont fail cls-testbed.t if tests/cls dir is empty
Date: Thu, 2 Oct 2014 11:35:07 +0300	[thread overview]
Message-ID: <CAMw6YJLEujeJqNJ1c94dv8eUt2u1M1vvLCQzgoUPguOVj8s1YA@mail.gmail.com> (raw)
In-Reply-To: <1412031436-14492-1-git-send-email-vadim4j@gmail.com>

Hi,

Please ignore this patch, I will send modified one with another sibject.

On Tue, Sep 30, 2014 at 1:57 AM, Vadim Kochan <vadim4j@gmail.com> wrote:
> Curently tests/cls-testbed.t tries to run any *.t in
> tests/cls/ folder but such folder does not exist.
>
> The better solution can be like having a generic mechanism which
> allows to SKIP some tests (by return code?).
>
> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
> ---
>  testsuite/tests/cls-testbed.t | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/testsuite/tests/cls-testbed.t b/testsuite/tests/cls-testbed.t
> index efae2a5..be32d79 100755
> --- a/testsuite/tests/cls-testbed.t
> +++ b/testsuite/tests/cls-testbed.t
> @@ -5,6 +5,11 @@ source lib/generic.sh
>
>  QDISCS="cbq htb dsmark"
>
> +if [ ! -d tests/cls ]; then
> +    ts_log "tests/cls folder is empty"
> +    exit 0
> +fi
> +
>  for q in ${QDISCS}; do
>         ts_log "Preparing classifier testbed with qdisc $q"
>
> --
> 2.1.0
>

      reply	other threads:[~2014-10-02  8:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 22:57 [PATCH iproute2] tests: Dont fail cls-testbed.t if tests/cls dir is empty Vadim Kochan
2014-10-02  8:35 ` Vadim Kochan [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMw6YJLEujeJqNJ1c94dv8eUt2u1M1vvLCQzgoUPguOVj8s1YA@mail.gmail.com \
    --to=vadim4j@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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.
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 NNTP newsgroup(s).