From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] support/testing: add test of BR2_CCACHE with an external toolchain
Date: Mon, 24 Jul 2017 19:54:58 +0200 [thread overview]
Message-ID: <20170724175458.GF2918@scaer> (raw)
In-Reply-To: <20170724163121.A64CB81DD3@busybox.osuosl.org>
Thomas, All,
On 2017-07-24 18:35 +0200, Thomas Petazzoni spake thusly:
> commit: https://git.buildroot.net/buildroot/commit/?id=6355ec2768c486de318b76835af73fdcb894b311
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>
> We reuse TestExternalToolchainBuildrootuClibc and add ccache to its
> configuration.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Reviewed-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> Tested-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> .gitlab-ci.yml | 1 +
> support/testing/tests/toolchain/test_external.py | 11 +++++++++++
> 2 files changed, 12 insertions(+)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 57710ab..42707ad 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -233,6 +233,7 @@ tests.package.test_python.TestPython2: *runtime_test
> tests.package.test_python.TestPython3: *runtime_test
> tests.toolchain.test_external.TestExternalToolchainBuildrootMusl: *runtime_test
> tests.toolchain.test_external.TestExternalToolchainBuildrootuClibc: *runtime_test
> +tests.toolchain.test_external.TestExternalToolchainCCache: *runtime_test
> tests.toolchain.test_external.TestExternalToolchainCtngMusl: *runtime_test
> tests.toolchain.test_external.TestExternalToolchainLinaroArm: *runtime_test
> tests.toolchain.test_external.TestExternalToolchainSourceryArmv4: *runtime_test
You don't need to list all tests in there, if you want to execute all
of them.i
Instead, you can just list 'tests' and all sub-tests will be run by
nose2. This way we need not update this file with every new test that we
add. And in fact I think we should not even need to list it, and make
the runtime-test entry just run everything...
I think it is even possible to mark some tests with 'test campaign tag'
so that they are only executed under some conditions that we define
ourselves (like, 'nightly', 'weekly', but also like 'arm', 'mips' or
whatever 'tag' we're interested in). If you think it might be usefull,
I can research that further...
Regards,
Yann E. MORIN.
> diff --git a/support/testing/tests/toolchain/test_external.py b/support/testing/tests/toolchain/test_external.py
> index afb4bb0..394fa17 100644
> --- a/support/testing/tests/toolchain/test_external.py
> +++ b/support/testing/tests/toolchain/test_external.py
> @@ -229,3 +229,14 @@ BR2_TOOLCHAIN_EXTERNAL_CXX=y
> kernel="builtin",
> options=["-initrd", img])
> self.emulator.login()
> +
> +class TestExternalToolchainCCache(TestExternalToolchainBuildrootuClibc):
> + extraconfig = \
> +"""
> +BR2_CCACHE=y
> +BR2_CCACHE_DIR="{builddir}/ccache-dir"
> +"""
> +
> + def __init__(self, names):
> + super(TestExternalToolchainBuildrootuClibc, self).__init__(names)
> + self.config += self.extraconfig.format(builddir=self.builddir)
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-07-24 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 16:35 [Buildroot] [git commit] support/testing: add test of BR2_CCACHE with an external toolchain Thomas Petazzoni
2017-07-24 17:54 ` Yann E. MORIN [this message]
2017-07-24 22:54 ` Arnout Vandecappelle
2017-07-25 7:03 ` Thomas Petazzoni
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=20170724175458.GF2918@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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