From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [rt-devel:linux-6.2.y-rt-rebase] [printk] 5342b8e20b: hwsim.ap_ft_eap_cui.fail
Date: Tue, 24 Jan 2023 15:10:06 +0100 [thread overview]
Message-ID: <Y8/mviV4zZbxgy1x@linutronix.de> (raw)
In-Reply-To: <202301242146.213fe56e-oliver.sang@intel.com>
On 2023-01-24 21:23:54 [+0800], kernel test robot wrote:
> d144a18b3d136079 5342b8e20b15e5fb37e49de2435
> ---------------- ---------------------------
> fail:runs %reproduction fail:runs
> | | |
> :6 83% 5:6 hwsim.ap_ft_eap_cui.fail
> :6 100% 6:6 hwsim.ap_ft_many.fail
> :6 100% 6:6 hwsim.ap_ft_pmf_bip_cmac_128.fail
…
> Roaming association rejected
> Traceback (most recent call last):
> File "/lkp/benchmarks/hwsim/tests/hwsim/./run-tests.py", line 534, in main
> t(dev, apdev)
> File "/lkp/benchmarks/hwsim/tests/hwsim/test_ap_ft.py", line 1519, in test_ap_ft_eap_cui
> generic_ap_ft_eap(dev, apdev, vlan=False, cui=True)
> File "/lkp/benchmarks/hwsim/tests/hwsim/test_ap_ft.py", line 1485, in generic_ap_ft_eap
> run_roams(dev[0], apdev, hapd, hapd1, ssid, passphrase, eap=True,
> File "/lkp/benchmarks/hwsim/tests/hwsim/test_ap_ft.py", line 273, in run_roams
> dev.roam(ap1['bssid'])
> File "/lkp/benchmarks/hwsim/tests/hwsim/wpasupplicant.py", line 1238, in roam
> raise Exception("Roaming association rejected")
> Exception: Roaming association rejected
> FAIL ap_ft_eap_cui 2.405507 2023-01-21 20:29:33.761610
> passed 0 test case(s)
> skipped 0 test case(s)
> failed tests: ap_ft_eap_cui
This looks unrelated to the commit question. Please check.
Sebastian
next prev parent reply other threads:[~2023-01-24 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 13:23 kernel test robot
2023-01-24 14:10 ` Sebastian Andrzej Siewior [this message]
2023-01-28 1:45 ` Oliver Sang
2023-01-30 9:02 ` Sebastian Andrzej Siewior
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=Y8/mviV4zZbxgy1x@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=rcu@vger.kernel.org \
/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
all inboxes | Powered by JetHome®