From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, avkrasnov@salutedevices.com
Subject: RE: [v1] Bluetooth: hci_uart: fix race during initialization
Date: Wed, 27 Nov 2024 05:21:07 -0800 (PST) [thread overview]
Message-ID: <67471cc3.c80a0220.25d60c.b7d3@mx.google.com> (raw)
In-Reply-To: <a1db0c90-1803-e01c-3e23-d18e4343a4eb@salutedevices.com>
[-- Attachment #1: Type: text/plain, Size: 2308 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=912808
---Test result---
Test Summary:
CheckPatch PENDING 0.28 seconds
GitLint PENDING 0.25 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 24.87 seconds
CheckAllWarning PASS 27.04 seconds
CheckSparse PASS 30.44 seconds
BuildKernel32 PASS 24.55 seconds
TestRunnerSetup PASS 435.17 seconds
TestRunner_l2cap-tester PASS 20.15 seconds
TestRunner_iso-tester FAIL 28.03 seconds
TestRunner_bnep-tester PASS 4.81 seconds
TestRunner_mgmt-tester PASS 122.28 seconds
TestRunner_rfcomm-tester PASS 7.51 seconds
TestRunner_sco-tester PASS 9.32 seconds
TestRunner_ioctl-tester PASS 8.01 seconds
TestRunner_mesh-tester FAIL 8.07 seconds
TestRunner_smp-tester PASS 7.44 seconds
TestRunner_userchan-tester PASS 5.00 seconds
IncrementalBuild PENDING 0.46 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
WARNING: possible circular locking dependency detected
Total: 124, Passed: 120 (96.8%), Failed: 0, Not Run: 4
##############################
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: 33 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.103 seconds
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-11-27 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 12:38 [PATCH v1] Bluetooth: hci_uart: fix race during initialization Arseniy Krasnov
2024-11-27 13:21 ` bluez.test.bot [this message]
2024-12-16 11:58 ` Arseniy Krasnov
2024-12-16 14:52 ` Luiz Augusto von Dentz
2024-12-16 15:06 ` Arseniy Krasnov
-- strict thread matches above, loose matches on Subject: below --
2025-02-12 9:52 Arseniy Krasnov
2025-02-12 16:02 ` [v1] " bluez.test.bot
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=67471cc3.c80a0220.25d60c.b7d3@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=avkrasnov@salutedevices.com \
--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.