From: kernel test robot <yujie.liu@intel.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: <oe-kbuild-all@lists.linux.dev>,
Linux Memory Management List <linux-mm@kvack.org>,
Kees Cook <keescook@chromium.org>
Subject: [linux-next:master 10918/12321] ../kselftest_harness.h:851:26: error: '_ip_local_port_range_late_bind_object' undeclared here (not in a function); did you mean 'ip_local_port_range_late_bind'?
Date: Fri, 10 May 2024 10:59:21 +0800 [thread overview]
Message-ID: <202405100339.vfBe0t9C-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 704ba27ac55579704ba1289392448b0c66b56258
commit: 8a25c905ae398bdd40f75cffed170516c749e7db [10918/12321] selftests/harness: Share _metadata between forked processes
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
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 <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202405100339.vfBe0t9C-lkp@intel.com/
All errors (new ones prefixed by >>):
linux/tools/testing/selftests/net$ make
...
gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem tools/testing/selftests/../../../usr/include -I../ ip_local_port_range.c -o tools/testing/selftests/net/ip_local_port_range
In file included from ip_local_port_range.c:13:
>> ../kselftest_harness.h:851:26: error: '_ip_local_port_range_late_bind_object' undeclared here (not in a function); did you mean 'ip_local_port_range_late_bind'?
851 | .test = &_##fixture_name##_##test_name##_object, \
| ^
ip_local_port_range.c:414:1: note: in expansion of macro 'XFAIL_ADD'
414 | XFAIL_ADD(ip_local_port_range, ip4_stcp, late_bind);
| ^~~~~~~~~
make: *** [../lib.mk:179: tools/testing/selftests/net/ip_local_port_range] Error 1
vim +851 tools/testing/selftests/net/../kselftest_harness.h
2709473c938602 Jakub Kicinski 2024-02-28 834
2709473c938602 Jakub Kicinski 2024-02-28 835 /**
2709473c938602 Jakub Kicinski 2024-02-28 836 * XFAIL_ADD() - mark variant + test case combination as expected to fail
2709473c938602 Jakub Kicinski 2024-02-28 837 * @fixture_name: name of the fixture
2709473c938602 Jakub Kicinski 2024-02-28 838 * @variant_name: name of the variant
2709473c938602 Jakub Kicinski 2024-02-28 839 * @test_name: name of the test case
2709473c938602 Jakub Kicinski 2024-02-28 840 *
2709473c938602 Jakub Kicinski 2024-02-28 841 * Mark a combination of variant + test case for a given fixture as expected
2709473c938602 Jakub Kicinski 2024-02-28 842 * to fail. Tests marked this way will report XPASS / XFAIL return codes,
2709473c938602 Jakub Kicinski 2024-02-28 843 * instead of PASS / FAIL,and use respective counters.
2709473c938602 Jakub Kicinski 2024-02-28 844 */
2709473c938602 Jakub Kicinski 2024-02-28 845 #define XFAIL_ADD(fixture_name, variant_name, test_name) \
2709473c938602 Jakub Kicinski 2024-02-28 846 static struct __test_xfail \
2709473c938602 Jakub Kicinski 2024-02-28 847 _##fixture_name##_##variant_name##_##test_name##_xfail = \
2709473c938602 Jakub Kicinski 2024-02-28 848 { \
2709473c938602 Jakub Kicinski 2024-02-28 849 .fixture = &_##fixture_name##_fixture_object, \
2709473c938602 Jakub Kicinski 2024-02-28 850 .variant = &_##fixture_name##_##variant_name##_object, \
2709473c938602 Jakub Kicinski 2024-02-28 @851 .test = &_##fixture_name##_##test_name##_object, \
2709473c938602 Jakub Kicinski 2024-02-28 852 }; \
2709473c938602 Jakub Kicinski 2024-02-28 853 static void __attribute__((constructor)) \
2709473c938602 Jakub Kicinski 2024-02-28 854 _register_##fixture_name##_##variant_name##_##test_name##_xfail(void) \
2709473c938602 Jakub Kicinski 2024-02-28 855 { \
2709473c938602 Jakub Kicinski 2024-02-28 856 __register_xfail(&_##fixture_name##_##variant_name##_##test_name##_xfail); \
2709473c938602 Jakub Kicinski 2024-02-28 857 }
2709473c938602 Jakub Kicinski 2024-02-28 858
:::::: The code at line 851 was first introduced by commit
:::::: 2709473c938602c3955b87000009e9bf3cd9bb32 selftests: kselftest_harness: support using xfail
:::::: TO: Jakub Kicinski <kuba@kernel.org>
:::::: CC: David S. Miller <davem@davemloft.net>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-10 2:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202405100339.vfBe0t9C-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=mic@digikod.net \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).