All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] doc: driver-model: Update dm tests run using test.py
Date: Wed, 16 Mar 2016 10:27:40 -0600	[thread overview]
Message-ID: <56E9897C.4080903@wwwdotorg.org> (raw)
In-Reply-To: <1458129629-15541-1-git-send-email-jteki@openedev.com>

On 03/16/2016 06:00 AM, Jagan Teki wrote:
> Since all the tests are implemented in pytest infrastructure,
> So update the dm tests with the same instead of ./test/dm/test-dm.sh

> diff --git a/doc/driver-model/README.txt b/doc/driver-model/README.txt

> +   ./test/py/test.py --bd sandbox --build -k ut_dm -v

I'd suggest dropping the -v to simplify the output, although I suppose 
it might be useful to list the name of each test separately.

>
>   You should see something like this:
>
> -    <...U-Boot banner...>
...
> +(venv)$ ./test/py/test.py --bd sandbox --build -k ut_dm -v
> ++make O=/root/u-boot/build-sandbox -s sandbox_defconfig
> ++make O=/root/u-boot/build-sandbox -s -j8
> +======================================================================================== test session starts ========================================================================================
> +platform linux2 -- Python 2.7.5, pytest-2.9.0, py-1.4.31, pluggy-0.3.1 -- /root/u-boot/venv/bin/python

I'd suggest running the command in a terminal with 80 columns to narrow 
the width of the output.

Other than than, the series,
Acked-by: Stephen Warren <swarren@nvidia.com>

      parent reply	other threads:[~2016-03-16 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 12:00 [U-Boot] [PATCH 1/2] doc: driver-model: Update dm tests run using test.py Jagan Teki
2016-03-16 12:00 ` [U-Boot] [PATCH 2/2] board: README.sandbox: Update dm test command Jagan Teki
2016-03-16 16:27 ` Stephen Warren [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=56E9897C.4080903@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.