All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/9] test/dm: clear unit test failure count each run
Date: Thu, 28 Jan 2016 21:02:16 -0700	[thread overview]
Message-ID: <CAPnjgZ08LiWdpOkOYbJOKvo-X8GN5QjU4JmxiTq8OD_7PDVbRw@mail.gmail.com> (raw)
In-Reply-To: <CAPnjgZ1qxOCLuRNGQWKU+O9wGYg+66Li=RhSwkT4zSXFuyEoVw@mail.gmail.com>

On 28 January 2016 at 20:46, Simon Glass <sjg@chromium.org> wrote:
> On 27 January 2016 at 23:57, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> The ut command prints a test failure count each time it is executed.
>> This is stored in a global variable which is never reset. Consequently,
>> the printed failure count accumulates across runs. Fix this by clearing
>> the counter each time "ut" is invoked.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>>  test/dm/test-main.c | 2 ++
>>  1 file changed, 2 insertions(+)
>
> Acked-by: Simon Glass <sjg@chromium.org>

Applied to u-boot-dm, thanks!

      reply	other threads:[~2016-01-29  4:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  6:57 [U-Boot] [PATCH 1/9] test/dm: clear unit test failure count each run Stephen Warren
2016-01-28  6:57 ` [U-Boot] [PATCH 2/9] test/py: fix spawn.expect multiple match handling Stephen Warren
2016-01-29  3:47   ` Simon Glass
2016-01-29  4:02     ` Simon Glass
2016-01-28  6:57 ` [U-Boot] [PATCH 3/9] test.py: calculate bad patterns on change only Stephen Warren
2016-01-29  3:47   ` Simon Glass
2016-01-29  4:02     ` Simon Glass
2016-01-28  6:57 ` [U-Boot] [PATCH 4/9] test/py: check for bad patterns everywhere we wait Stephen Warren
2016-01-29  3:47   ` Simon Glass
2016-01-29  4:02     ` Simon Glass
2016-01-28  6:57 ` [U-Boot] [PATCH 5/9] test/py: detect another "bad pattern" in console output Stephen Warren
2016-01-29  3:47   ` Simon Glass
2016-01-29  4:02     ` Simon Glass
2016-01-28  6:57 ` [U-Boot] [PATCH 6/9] test/py: correctly log xfail/xpass tests Stephen Warren
2016-01-29  3:47   ` Simon Glass
2016-01-29  4:02     ` Simon Glass
2016-01-28  6:57 ` [U-Boot] [PATCH 7/9] test/py: pass test DTB to sandbox Stephen Warren
2016-01-29  3:47   ` Simon Glass
2016-01-29  4:02     ` Simon Glass
2016-01-28  6:57 ` [U-Boot] [PATCH 8/9] test/py: run sandbox in source directory Stephen Warren
2016-01-29  3:47   ` Simon Glass
2016-01-29  4:02     ` Simon Glass
2016-01-28  6:57 ` [U-Boot] [PATCH 9/9] test/py: run C-based unit tests Stephen Warren
2016-01-29  3:47   ` Simon Glass
2016-01-29  3:46 ` [U-Boot] [PATCH 1/9] test/dm: clear unit test failure count each run Simon Glass
2016-01-29  4:02   ` Simon Glass [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=CAPnjgZ08LiWdpOkOYbJOKvo-X8GN5QjU4JmxiTq8OD_7PDVbRw@mail.gmail.com \
    --to=sjg@chromium.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.