public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: Alexey Brodkin <alexey.brodkin@synopsys.com>
Cc: Vineet Gupta <vineet.gupta1@synopsys.com>,
	"kernelci@groups.io" <kernelci@groups.io>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>
Subject: Re: failing ARC builds in kernelCI
Date: Tue, 27 Nov 2018 14:02:20 -0800	[thread overview]
Message-ID: <7h8t1ekwlv.fsf@baylibre.com> (raw)
In-Reply-To: <2b7adbb0eeef90de6895889be814fd632e20a22f.camel@synopsys.com>

Alexey Brodkin <alexey.brodkin@synopsys.com> writes:

> Hi Kevin,
>
> On Tue, 2018-11-27 at 07:23 -0800, Kevin Hilman wrote:
>> Hi Alexey,
>> 
>> You may have noticed that some defconfigs are failing to build
>> upstream for ARC.  For example, on mainline, both allnoconfig and
>> tinyconfig fail to build[1].
>
> Actually I haven't seen that!
>  1. I used to check https://kernelci.org/soc/ but there's still no mention
>     of ARC so I thought builds for ARC are not enabled still.

Yeah, the /soc/ page is currently for boot results, not build results

>  2. I haven't seen any email notifications as well if they exist at all.

The list where all the general build/boot reports go is here[1], and
here's an example[2] showing the warnings/errors.

> That said it would be good if warning emails are sent to our mailing-list
> linux-snps-arc@lists.infradead.org (see in Cc as well) so somebody reacts on them.

Unfortunately, we don't have a way of sending arch-specific mails at the
moment.

>
>> Do you guys have any plans to fix these, or should we disable them?
>> We currently build these for all the other arches.,
>
> Sure, let me take a look right now.

Thanks,

Kevin

>> 
>> Kevin
>> 
>> [1] https://kernelci.org/build/mainline/branch/master/kernel/v4.20-rc4-7-gef78e5ec9214/
>
> -Alexey

[1] https://lists.linaro.org/mailman/listinfo/kernel-build-reports
[2] https://lists.linaro.org/pipermail/kernel-build-reports/2018-November/039387.html

      parent reply	other threads:[~2018-11-27 22:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 15:23 failing ARC builds in kernelCI Kevin Hilman
2018-11-27 15:38 ` Alexey Brodkin
2018-11-27 15:45   ` Alexey Brodkin
2018-11-27 22:24     ` Kevin Hilman
2018-11-27 22:02   ` Kevin Hilman [this message]

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=7h8t1ekwlv.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=alexey.brodkin@synopsys.com \
    --cc=kernelci@groups.io \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=vineet.gupta1@synopsys.com \
    /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