From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH][autobuild] autobuild-run: introduce "--tc-cfg-uri" option for toolchain configs URI
Date: Fri, 21 Oct 2016 11:56:21 +0000 [thread overview]
Message-ID: <1477050979.28679.16.camel@synopsys.com> (raw)
In-Reply-To: <20161021133452.0508e5c5@free-electrons.com>
Hi Thomas,
Yes, we wan't to use?
On Fri, 2016-10-21 at 13:34 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 21 Oct 2016 13:24:14 +0300, Vlad Zakharov wrote:
> >
> > This commit introduces "--tc-cfg-uri" option (short "-t").
> > Described option is used to pass URI of file that contain
> > toolchains configurations to be used in autobuilds.
> >
> > Default value refers to standard buildroot autobuild toolchain
> > configuration file:
> > http://autobuild.buildroot.org/toolchains/configs/toolchain-configs.csv
> >
> > Such update allows users to add their own toolchain configurations
> > to use in buildroot autobuilds.
> >
> > Signed-off-by: Vlad Zakharov <vzakhar@synopsys.com>
>
> I am not sure I like this approach very much. It means people can start
> using a non-default set of toolchains, and then submit results to
> autobuild.buildroot.org. Such results would possibly not be
> reproducible by others because we may not have access to those
> toolchains.
>
Of course people can misuse the script and run autobuilds with mysterious external toolchain and nobody except
themselves will be able to reproduce such builds. However if people use internal buildroot toolchain information of how
toolchain has been configured is always accessible in ".config" file that is provided with other build results.?
> Is this intended to run tests only the ARC architecture builds on your
> autobuilder?
>
In our case we want at least to run more autobuilds with internal up-to-date toolchain to get relevant visibility of
what is happening with ARC latest tools. Suggested approach will give us flexible way to set up such configurations.?
In default configs there is only one configuration for arc that uses internal tools.?
?
> Thomas
--
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>
next prev parent reply other threads:[~2016-10-21 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 10:24 [Buildroot] [PATCH][autobuild] autobuild-run: introduce "--tc-cfg-uri" option for toolchain configs URI Vlad Zakharov
2016-10-21 11:34 ` Thomas Petazzoni
2016-10-21 11:56 ` Vlad Zakharov [this message]
2016-10-21 12:04 ` Alexey Brodkin
2016-10-21 18:13 ` Arnout Vandecappelle
2016-10-21 19:18 ` Alexey Brodkin
2016-10-21 19:28 ` Arnout Vandecappelle
2016-10-21 19:44 ` Alexey Brodkin
2017-02-06 17:58 ` 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=1477050979.28679.16.camel@synopsys.com \
--to=vladislav.zakharov@synopsys.com \
--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