From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, mathieu.acher@irisa.fr
Cc: Kevin Hilman <khilman@baylibre.com>
Subject: Re: kci_build proposal
Date: Fri, 29 May 2020 11:44:20 +0100 [thread overview]
Message-ID: <20200529104420.GC4610@sirena.org.uk> (raw)
In-Reply-To: <18306.1590738124792037023@groups.io>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
On Fri, May 29, 2020 at 12:42:04AM -0700, Mathieu Acher wrote:
> One issue we found is to build the right Docker image: some
> configurations of the kernel require specific tools and anticipating
> all can be tricky, leading to some false-positive failures. Have you
> encountered this situation?
We do, generally when we notice something like this has happened we will
just add the new tool to our images and move on. Since linux-next is
included in our coverage we tend to notice when things hit that and
people are a bit more tolerant of breakage there than they might be in
other trees so long as it gets addressed reasonably promptly.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-05-29 10:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 16:36 kci_build proposal Dan Rue
2020-04-21 15:46 ` Guillaume Tucker
2020-04-21 15:53 ` Mark Brown
2020-04-21 17:32 ` Dan Rue
2020-04-21 17:28 ` Dan Rue
2020-05-22 18:22 ` Kevin Hilman
2020-05-27 19:58 ` Dan Rue
2020-05-28 6:43 ` Guillaume Tucker
2020-05-28 17:28 ` Dan Rue
2020-05-28 21:03 ` Guillaume Tucker
2020-05-29 15:53 ` Dan Rue
2020-06-15 13:22 ` "Audience"/"Guest" can join for this meeting running on 23rd? koti koti
2020-06-16 16:16 ` Mark Brown
2020-06-17 1:49 ` koti koti
2020-06-17 10:31 ` Mark Brown
2020-06-17 10:55 ` koti koti
2020-05-28 23:31 ` kci_build proposal Kevin Hilman
2020-05-29 7:42 ` Mathieu Acher
2020-05-29 10:44 ` Mark Brown [this message]
2020-05-29 14:27 ` Guillaume Tucker
2020-06-16 16:33 ` Nick Desaulniers
2020-06-23 7:28 ` Mathieu Acher
2020-06-23 23:48 ` Nick Desaulniers
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=20200529104420.GC4610@sirena.org.uk \
--to=broonie@kernel.org \
--cc=kernelci@groups.io \
--cc=khilman@baylibre.com \
--cc=mathieu.acher@irisa.fr \
/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