linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yujie Liu <yujie.liu@intel.com>
To: Philipp Stanner <pstanner@redhat.com>
Cc: lkp <lkp@intel.com>, "kmo@daterainc.com" <kmo@daterainc.com>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"neilb@suse.de" <neilb@suse.de>,
	"mhiramat@kernel.org" <mhiramat@kernel.org>,
	"arnd@kernel.org" <arnd@kernel.org>,
	"yury.norov@gmail.com" <yury.norov@gmail.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"helgaas@kernel.org" <helgaas@kernel.org>,
	"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>,
	"ben.dooks@codethink.co.uk" <ben.dooks@codethink.co.uk>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"Jiang, Dave" <dave.jiang@intel.com>,
	"jbaron@akamai.com" <jbaron@akamai.com>,
	"dakr@redhat.com" <dakr@redhat.com>,
	"davidgow@google.com" <davidgow@google.com>,
	"schnelle@linux.ibm.com" <schnelle@linux.ibm.com>,
	"sanpeqf@gmail.com" <sanpeqf@gmail.com>,
	"wuqiang.matt@bytedance.com" <wuqiang.matt@bytedance.com>,
	"eric.auger@redhat.com" <eric.auger@redhat.com>,
	"jgg@ziepe.ca" <jgg@ziepe.ca>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"paul@pgazz.com" <paul@pgazz.com>,
	"fazilyildiran@gmail.com" <fazilyildiran@gmail.com>,
	"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] lib: move pci_iomap.c to drivers/pci/
Date: Thu, 23 Nov 2023 14:42:05 +0800	[thread overview]
Message-ID: <ZV70PWDGfrEgr50K@yujie-X299> (raw)
In-Reply-To: <9828583bcb49e1adeaa9ac16204b2ad80bd77d4d.camel@redhat.com>

Hi Philipp,

On Wed, Nov 22, 2023 at 09:15:52AM +0100, Philipp Stanner wrote:
> On Wed, 2023-11-22 at 01:51 +0000, Liu, Yujie wrote:
> > Please kindly ignore these duplicate reports. There seems to be a bug
> > in the robot and we will fix this ASAP. Sorry for the noise.
> 
> They are not exactly duplicates, I think. You notice that by the mails'
> bottoms:
> 
> Mail N:
>    WARNING: unmet direct dependencies detected for GENERIC_PCI_IOMAP
>      Depends on [n]: PCI [=n]
>      Selected by [y]:
>      - SPARC [=y]
> 
> Mail N-1:
>    WARNING: unmet direct dependencies detected for GENERIC_PCI_IOMAP
>      Depends on [n]: PCI [=n]
>      Selected by [y]:
>      - PARISC [=y]
> 
> etc...
> 
> So it seems to me that it's testing all the architectures and then
> sends an email for each one where the build fails.

Thanks for the feedback. Yes, it was testing on various architectures so
they were considered as different unique issues, and a separate report
was sent out for each of them.

However, there is some noise info in the report as shown below, which
indicates a bug in the bot. We will fix this ASAP.

   /usr/bin/grep: /db/releases/20231121182703/kernel-tests/etc/kcflags: No such file or directory
   {"timestamp":"2023-11-21 22:16:15 +0800", "level":"WARN", "event":"kbuild.sh:3942:in `add_etc_kcflags': grep exit 2 (ShellError)",

Best Regards,
Yujie

> 
> P.
> 
> > 
> > On Tue, 2023-11-21 at 23:56 +0800, kernel test robot wrote:
> > > Hi Philipp,
> > > 
> > > kernel test robot noticed the following build warnings:
> > > 
> > > [auto build test WARNING on pci/next]
> > > [also build test WARNING on pci/for-linus linus/master v6.7-rc2
> > > next-
> > > 20231121]
> > > [If your patch is applied to the wrong git tree, kindly drop us a
> > > note.
> > > And when submitting patch, we suggest to use '--base' as documented
> > > in
> > > https://git-scm.com/docs/git-format-patch#_base_tree_information]
> > > 
> > > url:   
> > > https://github.com/intel-lab-lkp/linux/commits/Philipp-Stanner/lib-move-pci_iomap-c-to-drivers-pci/20231121-060258
> > > base:  
> > > https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
> > > patch link:   
> > > https://lore.kernel.org/r/20231120215945.52027-3-pstanner%40redhat.com
> > > patch subject: [PATCH 1/4] lib: move pci_iomap.c to drivers/pci/
> > > config: sparc64-kismet-CONFIG_GENERIC_PCI_IOMAP-CONFIG_SPARC-0-0
> > > (
> > > https://download.01.org/0day-ci/archive/20231121/202311212316.a0awwk
> > > aE-lkp@intel.com/config)
> > > reproduce:
> > > (
> > > https://download.01.org/0day-ci/archive/20231121/202311212316.a0awwk
> > > aE-lkp@intel.com/reproduce)
> > > 
> > > If you fix the issue in a separate patch/commit (i.e. not just a
> > > new
> > > version of
> > > the same patch/commit), kindly add following tags
> > > > Reported-by: kernel test robot <lkp@intel.com>
> > > > Closes:
> > > > https://lore.kernel.org/oe-kbuild-all/202311212316.a0awwkaE-lkp@intel.com/
> > > 
> > > kismet warnings: (new ones prefixed by >>)
> > > > > kismet: WARNING: unmet direct dependencies detected for
> > > > > GENERIC_PCI_IOMAP when selected by SPARC
> > >    /usr/bin/grep: /db/releases/20231121182703/kernel-
> > > tests/etc/kcflags: No such file or directory
> > >    {"timestamp":"2023-11-21 22:16:15 +0800", "level":"WARN",
> > > "event":"kbuild.sh:3942:in `add_etc_kcflags': grep exit 2
> > > (ShellError)", "detail":"cmd: '/usr/bin/grep' '-v' '-e' '^#' '-e'
> > > '^$' '/db/releases/20231121182703/kernel-tests/etc/kcflags'
> > > \nstderr:
> > > /usr/bin/grep: /db/releases/20231121182703/kernel-
> > > tests/etc/kcflags:
> > > No such file or directory\n\n", "hostname":"community-kbuild-
> > > consumer-123", "host_hostname":"lkp-worker50",
> > > "call_stack":"/zday/kernel-tests/lib/kbuild.sh:3942:in
> > > `add_etc_kcflags': /usr/bin/grep:
> > > /db/releases/20231121182703/kernel-
> > > tests/etc/kcflags: No such file or directory (ShellError 2)\n  from
> > > /zday/kernel-tests/lib/kbuild.sh:3971: setup_kcflags\n  from
> > > /zday/kernel-tests/lib/kbuild.sh:4016: invoke_make\n  from
> > > /zday/kernel-tests/lib/kbuild.sh:4122: make\n  from /zday/kernel-
> > > tests/lib/kbuild.sh:5623: make_config_allyes\n  from /zday/kernel-
> > > tests/common.sh:209: redirect_error_to_screen\n  from /zday/kernel-
> > > tests/common.sh:217: redirect_command_errors\n  from /zday/kernel-
> > > tests/lib/kbuild.sh:5630: make_config\n  from /zday/kernel-
> > > tests/lib/builder/kismet.sh:156:
> > > generate_make_olddefconfig_warnings\n  from /zday/kernel-
> > > tests/lib/builder/kismet.sh:297: builder_compile\n  from
> > > /zday/kernel-tests/bisect-test-build-error.sh:94: main\n"}
> > >    
> > >    WARNING: unmet direct dependencies detected for
> > > GENERIC_PCI_IOMAP
> > >      Depends on [n]: PCI [=n]
> > >      Selected by [y]:
> > >      - SPARC [=y]
> > > 
> > 
> 
> 


  reply	other threads:[~2023-11-23  6:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231120215945.52027-3-pstanner@redhat.com>
2023-11-21  4:20 ` kernel test robot
2023-11-21 10:44   ` Philipp Stanner
2023-11-21  6:48 ` kernel test robot
2023-11-21  7:22   ` Arnd Bergmann
2023-11-21  7:20 ` kernel test robot
2023-11-21  7:45 ` kernel test robot
2023-11-21  7:58 ` kernel test robot
2023-11-21  8:46 ` kernel test robot
2023-11-21 10:44 ` kernel test robot
2023-11-21 10:44 ` kernel test robot
2023-11-21 13:14 ` kernel test robot
2023-11-21 14:38 ` kernel test robot
2023-11-21 15:04 ` kernel test robot
2023-11-21 15:40 ` kernel test robot
2023-11-21 15:56 ` kernel test robot
2023-11-22  1:51   ` Liu, Yujie
2023-11-22  8:15     ` Philipp Stanner
2023-11-23  6:42       ` Yujie Liu [this message]
2023-11-22 16:28 ` kernel test robot

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=ZV70PWDGfrEgr50K@yujie-X299 \
    --to=yujie.liu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@kernel.org \
    --cc=ben.dooks@codethink.co.uk \
    --cc=dakr@redhat.com \
    --cc=dave.jiang@intel.com \
    --cc=davidgow@google.com \
    --cc=eric.auger@redhat.com \
    --cc=fazilyildiran@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jbaron@akamai.com \
    --cc=jgg@ziepe.ca \
    --cc=keescook@chromium.org \
    --cc=kmo@daterainc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mhiramat@kernel.org \
    --cc=neilb@suse.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paul@pgazz.com \
    --cc=pstanner@redhat.com \
    --cc=rdunlap@infradead.org \
    --cc=sanpeqf@gmail.com \
    --cc=schnelle@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=wuqiang.matt@bytedance.com \
    --cc=yury.norov@gmail.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