[U-Boot] [PULL] u-boot-sh/master

[Tom Rini]

On Fri, Jun 15, 2018 at 06:09:49AM +0200, Marek Vasut wrote:
> On 06/14/2018 11:42 PM, Tom Rini wrote:
> > On Thu, Jun 14, 2018 at 10:58:22PM +0200, Marek Vasut wrote:
> >> On 06/14/2018 03:07 PM, Tom Rini wrote:
> >>> On Thu, Jun 14, 2018 at 01:35:05PM +0200, Marek Vasut wrote:
> >>>> On 06/14/2018 01:19 PM, Tom Rini wrote:
> >>>>> On Wed, Jun 13, 2018 at 06:05:08AM +0200, Marek Vasut wrote:
> >>>>>
> >>>>>> The following changes since commit 813d1fb56dc0af9567feb86cd71c49f14662044b:
> >>>>>>
> >>>>>>   Merge branch 'master' of git://git.denx.de/u-boot-ubi (2018-06-08
> >>>>>> 10:08:20 -0400)
> >>>>>>
> >>>>>> are available in the Git repository at:
> >>>>>>
> >>>>>>   git://git.denx.de/u-boot-sh.git master
> >>>>>>
> >>>>>> for you to fetch changes up to 0a52b00627c4fb6b100745c97910b75c99f3f4a9:
> >>>>>>
> >>>>>>   ARM: rmobile: Fix environment placement on Draak (2018-06-10 16:34:43
> >>>>>> +0200)
> >>>>>>
> >>>>>
> >>>>> NAK.  First, there are a lot of should be fix style errors in
> >>>>> the new files in drivers/pinctrl/renesas/.  Second, you have build
> >>>>> failures:
> >>>>> https://travis-ci.org/trini/u-boot/jobs/391819805
> >>>>> https://travis-ci.org/trini/u-boot/jobs/391819826
> >>>>
> >>>> Great, thanks!
> >>>>
> >>>> If the travis didn't vomit constant false positives recently, I'd trust
> >>>> it. With what it does now, I cannot trust it anymore.
> >>>
> >>> Can you elaborate?
> >>
> >> Don't you see the constant random timeouts during builds for some
> >> targets? I cannot get a successful build on the first try almost never
> >> these days, I have to keep restarting until I see that different targets
> >> failed during each build with a timeout and then extrapolate that the
> >> build is actually fine from that. It's annoying.
> > 
> > I see maybe 2-5 of those per day when I'm busy, which is annoying, but
> > I've never had it fail a second time in a row.
> 
> Good for you.
> 
> >> And then there is the other category of boards which indicate "red"
> >> failure marker due to ie. DT problems, which if you pull DTs from Linux
> >> is something you cannot really fix on the U-Boot side right away, but
> >> rather fix in Linux and then resync.
> > 
> > Yes, there are DT warnings that should be fixed.  But they aren't travis
> > errors, only actual fail to builds (like in the above, which indeed are
> > confusingly DT related, but not a travis problem at all, I see them
> > locally too) and new C warnings.
> 
> I'd prefer to see only errors which are relevant in the logs. Oh well.

Then fix the kernel dts.  I swear when I looked into these last they're
just as visible there.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180615/57f78a54/attachment.sig>