From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-video/master fails test/py ut_dm_rtc_set_get
Date: Mon, 3 Dec 2018 19:19:22 +0100 [thread overview]
Message-ID: <20181203191922.4d24fe06@crub> (raw)
In-Reply-To: <bd1c3503-9e50-8fd0-f1e7-44876f6da73f@wwwdotorg.org>
Hi Stephen,
On Mon, 3 Dec 2018 10:25:34 -0700
Stephen Warren swarren at wwwdotorg.org wrote:
> Anatolij,
>
> My test system noticed that u-boot-video.git master branch currently fails:
>
> ./test/py/test.py --bd sandbox --build -k ut_dm_rtc_set_get
>
> That's because this bug exists in the version of u-boot.git master
> branch that the video branch is based on. If you rebase to include the
> following commit:
>
> 952061352acf "drivers: rtc: correctly convert seconds to time structure"
>
> ... then the problem will be fixed. If you could do that, it'd be
> helpful to anyone running test.py, since then there won't be any known
> failures.
I've just rebased on current master, should be fixed now.
--
Anatolij
next prev parent reply other threads:[~2018-12-03 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 17:25 [U-Boot] u-boot-video/master fails test/py ut_dm_rtc_set_get Stephen Warren
2018-12-03 18:19 ` Anatolij Gustschin [this message]
2018-12-03 18:36 ` Stephen Warren
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=20181203191922.4d24fe06@crub \
--to=agust@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox