From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] .travis.yml: explicitly request sudo
Date: Thu, 4 Feb 2016 09:33:33 -0700 [thread overview]
Message-ID: <56B37D5D.4010401@wwwdotorg.org> (raw)
In-Reply-To: <56B31341.1000309@denx.de>
On 02/04/2016 02:00 AM, Heiko Schocher wrote:
> Hello Stephen,
>
> Am 03.02.2016 um 18:41 schrieb Stephen Warren:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Without this, builds default to using new Travis CI infra-structure which
>> does no allow sudo. The builds need sudo in order to install the ELDK
>> compilers. Consequently, almost all builds fail without this.
>>
>> I suspect that existing Travis CI users have not noticed this because
>> their accounts or builds have been grand-fathered into backwards-
>> compatible default settings, whereas I just set up a new build from
>> scratch and received new default settings.
>
> Did you tried it with current ML? Or at last with the patch from
> Roger?
>
> http://lists.denx.de/pipermail/u-boot/2016-January/243115.html
> [U-Boot] [PATCH] .travis.yml: rework according to new travis-ci infra
Both:-) That patch is already applied in mainline, and was included in
the branch I pushed "to" Travis.
> If I look into:
> https://travis-ci.org/u-boot/u-boot
>
> There are only mips and m68k for which the build fail ...
Yes. With the addition of the sudo tag, the same is now true for my branch.
next prev parent reply other threads:[~2016-02-04 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 17:41 [U-Boot] [PATCH] .travis.yml: explicitly request sudo Stephen Warren
2016-02-03 17:44 ` Andreas Färber
2016-02-04 9:00 ` Heiko Schocher
2016-02-04 16:33 ` Stephen Warren [this message]
2016-02-05 5:30 ` Heiko Schocher
2016-02-08 20:49 ` [U-Boot] " Tom Rini
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=56B37D5D.4010401@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox