From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2] Bluetooth: btusb: Don't fail external suspend requests
Date: Mon, 08 Jul 2024 13:36:46 -0700 (PDT) [thread overview]
Message-ID: <668c4dde.170a0220.e4ee8.215b@mx.google.com> (raw)
In-Reply-To: <20240708191727.2775854-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1697 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=869402
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint PASS 0.19 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 30.03 seconds
CheckAllWarning PASS 32.32 seconds
CheckSparse PASS 38.31 seconds
CheckSmatch PASS 103.02 seconds
BuildKernel32 PASS 28.87 seconds
TestRunnerSetup PASS 527.00 seconds
TestRunner_l2cap-tester PASS 22.10 seconds
TestRunner_iso-tester PASS 35.16 seconds
TestRunner_bnep-tester PASS 4.78 seconds
TestRunner_mgmt-tester FAIL 113.18 seconds
TestRunner_rfcomm-tester PASS 7.43 seconds
TestRunner_sco-tester PASS 15.08 seconds
TestRunner_ioctl-tester PASS 7.99 seconds
TestRunner_mesh-tester PASS 6.00 seconds
TestRunner_smp-tester PASS 6.97 seconds
TestRunner_userchan-tester PASS 5.02 seconds
IncrementalBuild PASS 28.56 seconds
Details
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 492, Passed: 489 (99.4%), Failed: 1, Not Run: 2
Failed Test Cases
LL Privacy - Add Device 6 (RL is full) Failed 0.197 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2024-07-08 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 19:17 [PATCH v2] Bluetooth: btusb: Don't fail external suspend requests Luiz Augusto von Dentz
2024-07-08 20:36 ` bluez.test.bot [this message]
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=668c4dde.170a0220.e4ee8.215b@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).