ma, 2025-07-14 kello 07:37 -0700, bluez.test.bot@xxxxxxxxx kirjoitti: > This is automated email and please do not reply to this email! > > Dear submitter, > > Thank you for submitting the patches to the linux bluetooth mailing list. > This is a CI test results with your patch series: > PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=982088 > > ---Test result--- > > Test Summary: > CheckPatch PENDING 0.44 seconds > GitLint PENDING 0.34 seconds > SubjectPrefix PASS 0.07 seconds > BuildKernel PASS 24.06 seconds > CheckAllWarning PASS 26.92 seconds > CheckSparse WARNING 29.90 seconds > BuildKernel32 PASS 24.59 seconds > TestRunnerSetup PASS 482.03 seconds > TestRunner_l2cap-tester PASS 28.08 seconds > TestRunner_iso-tester FAIL 41.16 seconds > TestRunner_bnep-tester PASS 5.95 seconds > TestRunner_mgmt-tester FAIL 134.62 seconds > TestRunner_rfcomm-tester PASS 9.35 seconds > TestRunner_sco-tester PASS 14.66 seconds > TestRunner_ioctl-tester PASS 9.96 seconds > TestRunner_mesh-tester FAIL 11.50 seconds > TestRunner_smp-tester PASS 9.74 seconds > TestRunner_userchan-tester PASS 6.10 seconds > IncrementalBuild PENDING 0.59 seconds > > Details > ############################## > Test: CheckPatch - PENDING > Desc: Run checkpatch.pl script > Output: > > ############################## > Test: GitLint - PENDING > Desc: Run gitlint > Output: > > ############################## > Test: CheckSparse - WARNING > Desc: Run sparse tool with linux kernel > Output: > net/bluetooth/af_bluetooth.c:248:25: warning: context imbalance in 'bt_accept_enqueue' - different lock contexts for basic blocknet/bluetooth/iso.c:2322:28: warning: incorrect type in assignment (different base types)net/bluetooth/iso.c:2322:28: expected unsigned short [usertype] snnet/bluetooth/iso.c:2322:28: got restricted __le16 [usertype] snnet/bluetooth/iso.c:2333:28: warning: incorrect type in assignment (different base types)net/bluetooth/iso.c:2333:28: expected unsigned short [usertype] snnet/bluetooth/iso.c:2333:28: got restricted __le16 [usertype] sn > ############################## > Test: TestRunner_iso-tester - FAIL > Desc: Run iso-tester with test-runner > Output: > Total: 130, Passed: 127 (97.7%), Failed: 2, Not Run: 1 > > Failed Test Cases > ISO Send - TX Timestamping Failed 0.233 seconds > ISO Send - TX CMSG Timestamping Failed 0.236 seconds These are false positives, they fail since the test is trying to use BT_POLL_ERRQUEUE socket option which does not exist in kernel, but has same value as the new BT_PTK_SEQNUM. The following patch removes the references to the non-existing kernel feature: https://lore.kernel.org/linux-bluetooth/2ffec6539fe38318c713b48985aaddda9671f258.1752501450.git.pav@xxxxxx/ > ############################## > Test: TestRunner_mgmt-tester - FAIL > Desc: Run mgmt-tester with test-runner > Output: > Total: 490, Passed: 485 (99.0%), Failed: 1, Not Run: 4 > > Failed Test Cases > LL Privacy - Add Device 3 (AL is full) Failed 0.228 seconds > ############################## > Test: TestRunner_mesh-tester - FAIL > Desc: Run mesh-tester with test-runner > Output: > Total: 10, Passed: 8 (80.0%), Failed: 2, Not Run: 0 > > Failed Test Cases > Mesh - Send cancel - 1 Timed out 2.061 seconds > Mesh - Send cancel - 2 Timed out 1.997 seconds > ############################## > Test: IncrementalBuild - PENDING > Desc: Incremental build with the patches in the series > Output: > > > > --- > Regards, > Linux Bluetooth
