From: "Li, Philip" <philip.li@intel.com>
To: Dmitry Vyukov <dvyukov@google.com>, lkp <lkp@intel.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"kbuild-all@01.org" <kbuild-all@01.org>
Subject: RE: [kbuild-all] [linux-next:master 5885/8111] /tmp/cc3gKKeM.s:35: Error: .err encountered
Date: Sat, 26 May 2018 14:37:23 +0000 [thread overview]
Message-ID: <831EE4E5E37DCC428EB295A351E662494CB5166D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CACT4Y+bR+ywj_OtGDYiCp+PZ4MfdqfrXg5XQwN36uRnNCEHEZg@mail.gmail.com>
> Subject: Re: [kbuild-all] [linux-next:master 5885/8111] /tmp/cc3gKKeM.s:35:
> Error: .err encountered
>
> On Sun, May 20, 2018 at 9:15 PM, kbuild test robot <lkp@intel.com> wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: fbbe3b8c2c9c5f84caf668703c26154cb4fbb9d1
> > commit: 3b67022379d3d0c6a5cc5152f6b46eeea635a194 [5885/8111] arm: port
> KCOV to arm
> > config: arm-allmodconfig (attached as .config)
> > compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
> > reproduce:
> > wget https://raw.githubusercontent.com/intel/lkp-
> tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > git checkout 3b67022379d3d0c6a5cc5152f6b46eeea635a194
> > # save the attached .config to linux build tree
> > make.cross ARCH=arm
> >
> > All errors (new ones prefixed by >>):
> >
> > /tmp/cc3gKKeM.s: Assembler messages:
> >>> /tmp/cc3gKKeM.s:35: Error: .err encountered
> > /tmp/cc3gKKeM.s:36: Error: .err encountered
> > /tmp/cc3gKKeM.s:37: Error: .err encountered
>
> I've tried to reproduce this following the instructions, but I failed,
thanks for input, we will follow up this to see whether there's issue
in bot side.
> build succeeds for me:
> https://www.spinics.net/lists/linux-mm/msg152336.html
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2018-05-26 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-20 19:15 kbuild test robot
2018-05-26 10:14 ` Dmitry Vyukov
2018-05-26 14:37 ` Li, Philip [this message]
[not found] ` <831EE4E5E37DCC428EB295A351E662494CB9C137@shsmsx102.ccr.corp.intel.com>
2018-06-07 2:02 ` FW: [kbuild-all] " Chen Rong
2018-06-07 5:41 ` Dmitry Vyukov
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=831EE4E5E37DCC428EB295A351E662494CB5166D@shsmsx102.ccr.corp.intel.com \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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