All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: kernel test robot <lkp@intel.com>
Cc: Yu Zhang <yu.c.zhang@linux.intel.com>, oe-kbuild-all@lists.linux.dev
Subject: Re: [kvm-x86:selftests 1/3] make[1]: *** No rule to make target 'kselftest/kvm/x86_64/cpuid_test.c', needed by 'kselftest/kvm/x86_64/cpuid_test.o'.
Date: Tue, 30 May 2023 15:01:55 -0700	[thread overview]
Message-ID: <ZHZyUxsezAz083lO@google.com> (raw)
In-Reply-To: <202305302015.D8PglEU7-lkp@intel.com>

On Tue, May 30, 2023, kernel test robot wrote:
> Hi Yu,
> 
> First bad commit (maybe != root cause):

Confirmed that reverting 954c9c3f96698f3af0c22f93a68e3905bc185458 makes the problem
go away.

> tree:   https://github.com/kvm-x86/linux selftests

In case it wasn't obvious, I applied and pushed this to kvm-x86/selftests but
hadn't yet merged it to kvm-x86/next.

> head:   a985a858acff64afaa5cf60e058357034cb14476
> commit: 954c9c3f96698f3af0c22f93a68e3905bc185458 [1/3] KVM: selftests: Add new CFLAGS to generate dependency files
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce:
>         # https://github.com/kvm-x86/linux/commit/954c9c3f96698f3af0c22f93a68e3905bc185458
>         git remote add kvm-x86 https://github.com/kvm-x86/linux
>         git fetch --no-tags kvm-x86 selftests
>         git checkout 954c9c3f96698f3af0c22f93a68e3905bc185458
>         make O=/tmp/kselftest headers
>         make O=/tmp/kselftest -C tools/testing/selftests
> 
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202305302015.D8PglEU7-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>    Makefile:89: *** Cannot find a vmlinux for VMLINUX_BTF at any of "vmlinux vmlinux ../../../../vmlinux /sys/kernel/btf/vmlinux /boot/vmlinux-5.9.0-2-amd64".  Stop.
> >> make[1]: *** No rule to make target 'kselftest/kvm/x86_64/cpuid_test.c', needed by 'kselftest/kvm/x86_64/cpuid_test.o'.

Yu, 

Can you take a look and send v3?  I unfortunately don't have bandwidth to dig
into this.  I'll drop commit 954c9c3f96698f3af0c22f93a68e3905bc185458.

  reply	other threads:[~2023-05-30 22:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 12:47 [kvm-x86:selftests 1/3] make[1]: *** No rule to make target 'kselftest/kvm/x86_64/cpuid_test.c', needed by 'kselftest/kvm/x86_64/cpuid_test.o' kernel test robot
2023-05-30 22:01 ` Sean Christopherson [this message]
2023-05-31 10:15   ` yu.c.zhang

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=ZHZyUxsezAz083lO@google.com \
    --to=seanjc@google.com \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yu.c.zhang@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.