From: Alexander Graf <agraf@suse.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] travis: Add efi_loader grub2 test
Date: Tue, 22 Nov 2016 00:15:50 +0100 [thread overview]
Message-ID: <5f85260f-ad5d-2483-332f-e3dc08ae4e21@suse.de> (raw)
In-Reply-To: <20161121223106.GH2546@bill-the-cat>
On 21/11/2016 23:31, Tom Rini wrote:
> On Mon, Nov 21, 2016 at 03:21:43PM -0700, Stephen Warren wrote:
>> On 11/18/2016 05:18 AM, Alexander Graf wrote:
>>> We have all the building blocks now to run arbitrary efi applications
>>> in travis. The most important one out there is grub2, so let's add
>>> a simple test to verify that grub2 still comes up.
>>
>>> diff --git a/.travis.yml b/.travis.yml
>>
>>> @@ -45,6 +48,9 @@ install:
>>> - virtualenv /tmp/venv
>>> - . /tmp/venv/bin/activate
>>> - pip install pytest
>>> + - grub-mkimage -o ~/grub_x86.efi -O i386-efi normal echo lsefimmap lsefi lsefisystab efinet tftp minicmd
>>> + - mkdir ~/grub2-arm
>>> + - ( cd ~/grub2-arm; wget -O - http://download.opensuse.org/ports/armv7hl/distribution/leap/42.2/repo/oss/suse/armv7hl/grub2-arm-efi-2.02~beta2-87.1.armv7hl.rpm | rpm2cpio | cpio -di )
>>
>> Do we really want to do this for all the build-only jobs too? I
>> might have expected to do this inside the test scripts that actually
>> use those binaries.
>
> So, it's the difference between making various jobs / stanzas more
> correct vs taking more time to do stuff. Unless this starts to push the
> "catch-all" arm job over the time limit, I don't think it's a big deal
> either way. And since travis-ci will tell us how long a given stanza
> takes we'll have a good idea pretty quick on if that's starting to take
> too long. That said, I don't have a strong opinion here and it wouldn't
> be too hard to move all of this into being under the TEST_PY_BD check
> and since we aren't relying on apt, it's not going to be time-in-apt
> factor.
If we move it into TEST_PY_BD, we would either run the same sequence
over and over again for individual tests or check if the file exists
inside the generation path. Either way, it will get less readable :).
Overall, we're talking of 1s of build time for this:
https://travis-ci.org/agraf/u-boot/jobs/177000864
so I'd definitely prefer to keep it simple rather than optimized.
Alex
next prev parent reply other threads:[~2016-11-21 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 12:18 [U-Boot] [PATCH v2] travis: Add efi_loader grub2 test Alexander Graf
2016-11-21 22:21 ` Stephen Warren
2016-11-21 22:31 ` Tom Rini
2016-11-21 23:15 ` Alexander Graf [this message]
2016-11-30 4:27 ` Stephen Warren
2016-11-21 23:21 ` Alexander Graf
2016-11-30 4:28 ` Stephen Warren
2016-11-27 14:56 ` [U-Boot] [U-Boot,v2] " 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=5f85260f-ad5d-2483-332f-e3dc08ae4e21@suse.de \
--to=agraf@suse.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 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.