From: kernel test robot <lkp@intel.com>
To: Vipin Sharma <vipinsh@google.com>, kvm@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Vipin Sharma <vipinsh@google.com>
Subject: Re: [PATCH 1/1] KVM: selftestsi: Create KVM selftests runnner to run interesting tests
Date: Thu, 22 Aug 2024 18:48:55 +0800 [thread overview]
Message-ID: <202408221838.XU8LHJDm-lkp@intel.com> (raw)
In-Reply-To: <20240821223012.3757828-2-vipinsh@google.com>
Hi Vipin,
kernel test robot noticed the following build warnings:
[auto build test WARNING on de9c2c66ad8e787abec7c9d7eff4f8c3cdd28aed]
url: https://github.com/intel-lab-lkp/linux/commits/Vipin-Sharma/KVM-selftestsi-Create-KVM-selftests-runnner-to-run-interesting-tests/20240822-063157
base: de9c2c66ad8e787abec7c9d7eff4f8c3cdd28aed
patch link: https://lore.kernel.org/r/20240821223012.3757828-2-vipinsh%40google.com
patch subject: [PATCH 1/1] KVM: selftestsi: Create KVM selftests runnner to run interesting tests
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20240822/202408221838.XU8LHJDm-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240822/202408221838.XU8LHJDm-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/202408221838.XU8LHJDm-lkp@intel.com/
All warnings (new ones prefixed by >>):
tools/testing/selftests/arm64/tags/.gitignore: warning: ignored by one of the .gitignore files
tools/testing/selftests/arm64/tags/Makefile: warning: ignored by one of the .gitignore files
tools/testing/selftests/arm64/tags/tags_test.c: warning: ignored by one of the .gitignore files
tools/testing/selftests/kvm/.gitignore: warning: ignored by one of the .gitignore files
tools/testing/selftests/kvm/Makefile: warning: ignored by one of the .gitignore files
tools/testing/selftests/kvm/config: warning: ignored by one of the .gitignore files
>> tools/testing/selftests/kvm/runner.py: warning: ignored by one of the .gitignore files
tools/testing/selftests/kvm/settings: warning: ignored by one of the .gitignore files
>> tools/testing/selftests/kvm/tests.json: warning: ignored by one of the .gitignore files
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-08-22 10:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 22:30 [RFC PATCH 0/1] KVM selftests runner for running more than just default Vipin Sharma
2024-08-21 22:30 ` [PATCH 1/1] KVM: selftestsi: Create KVM selftests runnner to run interesting tests Vipin Sharma
2024-08-22 10:48 ` kernel test robot [this message]
2024-08-22 20:56 ` Vipin Sharma
2024-08-22 20:55 ` [RFC PATCH 0/1] KVM selftests runner for running more than just default Vipin Sharma
2024-11-01 22:13 ` Vipin Sharma
2024-11-06 17:06 ` Sean Christopherson
2024-11-08 11:05 ` Andrew Jones
2024-11-14 17:42 ` Sean Christopherson
2024-11-15 21:15 ` Vipin Sharma
2024-11-21 0:29 ` Sean Christopherson
2024-11-22 22:37 ` Vipin Sharma
2024-11-15 20:18 ` Vipin Sharma
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=202408221838.XU8LHJDm-lkp@intel.com \
--to=lkp@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vipinsh@google.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