From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, conorkotwasinski2024@u.northwestern.edu
Subject: RE: [v2] sysfs: return -ENOENT from move/rename when kobj->sd is NULL
Date: Mon, 04 May 2026 00:29:53 -0700 (PDT) [thread overview]
Message-ID: <69f84af1.050a0220.2ef67e.53fe@mx.google.com> (raw)
In-Reply-To: <20260504050736.17672-1-conorkotwasinski2024@u.northwestern.edu>
[-- Attachment #1: Type: text/plain, Size: 3265 bytes --]
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=1089086
---Test result---
Test Summary:
CheckPatch PASS 0.66 seconds
GitLint PASS 0.28 seconds
SubjectPrefix FAIL 0.10 seconds
BuildKernel PASS 26.76 seconds
CheckAllWarning PASS 28.73 seconds
CheckSparse PASS 27.73 seconds
BuildKernel32 PASS 25.43 seconds
TestRunnerSetup PASS 525.64 seconds
TestRunner_l2cap-tester FAIL 6.55 seconds
TestRunner_iso-tester PASS 295.63 seconds
TestRunner_bnep-tester FAIL 6.40 seconds
TestRunner_mgmt-tester FAIL 8.76 seconds
TestRunner_rfcomm-tester PASS 28.75 seconds
TestRunner_sco-tester PASS 68.04 seconds
TestRunner_ioctl-tester FAIL 37.27 seconds
TestRunner_mesh-tester PASS 26.90 seconds
TestRunner_smp-tester PASS 6.41 seconds
TestRunner_userchan-tester FAIL 6.57 seconds
TestRunner_6lowpan-tester PASS 22.78 seconds
IncrementalBuild PASS 24.00 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_l2cap-tester - FAIL
Desc: Run l2cap-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_bnep-tester - FAIL
Desc: Run bnep-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
No test result found
##############################
Test: TestRunner_ioctl-tester - FAIL
Desc: Run ioctl-tester with test-runner
Output:
Total: 28, Passed: 0 (0.0%), Failed: 11, Not Run: 17
Failed Test Cases
Device List Timed out -30.851 seconds
Device Info Timed out -6.202 seconds
Reset Stat Timed out -6.205 seconds
Set Link Mode - ACCEPT Timed out -6.208 seconds
Set Pkt Type - DM Timed out -14.396 seconds
Set Pkt Type - DH Timed out -14.399 seconds
Set Pkt Type - HV Timed out -14.403 seconds
Set Pkt Type - 2-DH Timed out -14.406 seconds
Set Pkt Type - 2-DH Timed out -14.409 seconds
Set Pkt Type - ALL Timed out -14.412 seconds
Set ACL MTU - 1 Timed out -14.414 seconds
##############################
Test: TestRunner_userchan-tester - FAIL
Desc: Run userchan-tester with test-runner
Output:
No test result found
https://github.com/bluez/bluetooth-next/pull/142
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-05-04 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 15:06 [PATCH] sysfs: return -ENOENT from move/rename when kobj->sd is NULL Conor Kotwasinski
2026-04-16 16:39 ` bluez.test.bot
2026-04-28 22:31 ` [PATCH] " Danilo Krummrich
2026-05-04 5:07 ` [PATCH v2] " Conor Kotwasinski
2026-05-04 6:22 ` Greg Kroah-Hartman
2026-05-04 7:29 ` bluez.test.bot [this message]
2026-05-04 20:55 ` Danilo Krummrich
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=69f84af1.050a0220.2ef67e.53fe@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=conorkotwasinski2024@u.northwestern.edu \
--cc=linux-bluetooth@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