From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, chharry@chromium.org
Subject: RE: Bluetooth: Allow reset via sysfs
Date: Thu, 02 Jan 2025 19:45:47 -0800 (PST) [thread overview]
Message-ID: <67775d6b.d40a0220.600e1.a63e@mx.google.com> (raw)
In-Reply-To: <20250103112019.1.I8342291b757b20cd4cdbbfe658dc58ed5df46565@changeid>
[-- Attachment #1: Type: text/plain, Size: 2086 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=921922
---Test result---
Test Summary:
CheckPatch PENDING 0.26 seconds
GitLint PENDING 0.21 seconds
SubjectPrefix PASS 0.70 seconds
BuildKernel PASS 24.84 seconds
CheckAllWarning PASS 27.05 seconds
CheckSparse PASS 30.62 seconds
BuildKernel32 PASS 24.57 seconds
TestRunnerSetup PASS 443.19 seconds
TestRunner_l2cap-tester PASS 22.93 seconds
TestRunner_iso-tester PASS 32.42 seconds
TestRunner_bnep-tester PASS 4.97 seconds
TestRunner_mgmt-tester PASS 118.65 seconds
TestRunner_rfcomm-tester PASS 8.41 seconds
TestRunner_sco-tester PASS 9.47 seconds
TestRunner_ioctl-tester PASS 8.23 seconds
TestRunner_mesh-tester FAIL 8.27 seconds
TestRunner_smp-tester PASS 7.13 seconds
TestRunner_userchan-tester PASS 5.10 seconds
IncrementalBuild PENDING 0.61 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_mesh-tester - FAIL
Desc: Run mesh-tester with test-runner
Output:
BUG: KASAN: slab-use-after-free in run_timer_softirq+0x76c/0x7d0
WARNING: CPU: 0 PID: 64 at kernel/workqueue.c:2257 __queue_work+0x687/0xb40
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Mesh - Send cancel - 1 Failed 0.110 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-01-03 3:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 3:20 [PATCH] Bluetooth: Allow reset via sysfs Hsin-chen Chuang
2025-01-03 3:45 ` bluez.test.bot [this message]
2025-01-06 16:29 ` Luiz Augusto von Dentz
2025-01-07 7:21 ` Hsin-chen Chuang
2025-01-07 16:51 ` Luiz Augusto von Dentz
2025-01-08 12:33 ` Greg KH
2025-01-08 15:06 ` Luiz Augusto von Dentz
2025-01-08 15:10 ` Greg KH
2025-01-08 15:33 ` Luiz Augusto von Dentz
2025-01-08 16:13 ` Greg KH
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=67775d6b.d40a0220.600e1.a63e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=chharry@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.