From: kernel test robot <oliver.sang@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
<linux-wireless@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linux-next:master] [wifi] 97c19e42b2: hwsim.dpp_test_vector_p_256_b.fail
Date: Mon, 25 Sep 2023 15:59:10 +0800 [thread overview]
Message-ID: <202309251502.aa08a357-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "hwsim.dpp_test_vector_p_256_b.fail" on:
commit: 97c19e42b264e6b71a9ff9deea04c19f621805b9 ("wifi: mac80211: move offchannel works to wiphy work")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 926f75c8a5ab70567eb4c2d82fbc96963313e564]
in testcase: hwsim
version: hwsim-x86_64-717e5d7-1_20230720
with following parameters:
test: dpp_test_vector_p_256_b
compiler: gcc-12
test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-4790 v3 @ 3.60GHz (Haswell) with 6G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
we found the failure does not always happen, around ~50%. but keep clean on
parent.
730538edc8e0eb14 97c19e42b264e6b71a9ff9deea0
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:20 50% 10:20 hwsim.dpp_test_vector_p_256_b.fail
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 <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202309251502.aa08a357-oliver.sang@intel.com
group: group-34, test: dpp_test_vector_p_256_b
2023-09-22 11:50:05 export USER=root
2023-09-22 11:50:05 ./build.sh
Building TNC testing tools
Building wlantest
Building hs20-osu-client
Building hostapd
Building wpa_supplicant
2023-09-22 11:51:03 ./start.sh
2023-09-22 11:51:04 ./run-tests.py dpp_test_vector_p_256_b
DEV: wlan0: 02:00:00:00:00:00
DEV: wlan1: 02:00:00:00:01:00
DEV: wlan2: 02:00:00:00:02:00
APDEV: wlan3
APDEV: wlan4
START dpp_test_vector_p_256_b 1/1
Test: DPP P-256 test vector (Responder-only auth)
DPP authentication did not succeed (Responder)
Traceback (most recent call last):
File "/lkp/benchmarks/hwsim/tests/hwsim/./run-tests.py", line 531, in main
t(dev, apdev)
File "/lkp/benchmarks/hwsim/tests/hwsim/test_dpp.py", line 2583, in test_dpp_test_vector_p_256_b
wait_auth_success(dev[0], dev[1])
File "/lkp/benchmarks/hwsim/tests/hwsim/test_dpp.py", line 4878, in wait_auth_success
raise Exception("DPP authentication did not succeed (Responder)")
Exception: DPP authentication did not succeed (Responder)
FAIL dpp_test_vector_p_256_b 5.350665 2023-09-22 11:51:11.790041
passed 0 test case(s)
skipped 0 test case(s)
failed tests: dpp_test_vector_p_256_b
2023-09-22 11:51:11 ./stop.sh
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230925/202309251502.aa08a357-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-25 7: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=202309251502.aa08a357-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-mm@kvack.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@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