From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, johan+linaro@kernel.org
Subject: RE: Bluetooth: fix bdaddr quirks
Date: Wed, 31 May 2023 02:34:42 -0700 (PDT) [thread overview]
Message-ID: <647714b2.4a0a0220.add82.cee2@mx.google.com> (raw)
In-Reply-To: <20230531090424.3187-2-johan+linaro@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2012 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=752646
---Test result---
Test Summary:
CheckPatch PASS 1.31 seconds
GitLint PASS 0.62 seconds
SubjectPrefix PASS 0.20 seconds
BuildKernel PASS 34.55 seconds
CheckAllWarning PASS 37.25 seconds
CheckSparse PASS 42.93 seconds
CheckSmatch PASS 114.27 seconds
BuildKernel32 PASS 33.57 seconds
TestRunnerSetup PASS 471.26 seconds
TestRunner_l2cap-tester PASS 17.27 seconds
TestRunner_iso-tester FAIL 24.23 seconds
TestRunner_bnep-tester PASS 5.78 seconds
TestRunner_mgmt-tester PASS 117.97 seconds
TestRunner_rfcomm-tester PASS 9.13 seconds
TestRunner_sco-tester PASS 8.52 seconds
TestRunner_ioctl-tester PASS 9.87 seconds
TestRunner_mesh-tester PASS 7.24 seconds
TestRunner_smp-tester PASS 8.32 seconds
TestRunner_userchan-tester PASS 6.05 seconds
IncrementalBuild PASS 36.67 seconds
Details
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 80, Passed: 75 (93.8%), Failed: 5, Not Run: 0
Failed Test Cases
ISO AC 6(i) - Success Failed 0.239 seconds
ISO AC 7(i) - Success Failed 0.237 seconds
ISO AC 8(i) - Success Failed 0.238 seconds
ISO AC 9(i) - Success Failed 0.243 seconds
ISO AC 11(i) - Success Failed 0.238 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-05-31 9:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:04 [PATCH RESEND 0/2] Bluetooth: fix bdaddr quirks Johan Hovold
2023-05-31 9:04 ` [PATCH RESEND 1/2] Bluetooth: fix invalid-bdaddr quirk for non-persistent setup Johan Hovold
2023-05-31 9:34 ` bluez.test.bot [this message]
2023-05-31 9:04 ` [PATCH RESEND 2/2] Bluetooth: fix use-bdaddr-property quirk Johan Hovold
[not found] ` <CGME20230601220156eucas1p21caabcf02509fce7eb26f973704980f9@eucas1p2.samsung.com>
2023-06-01 22:01 ` Marek Szyprowski
2023-06-01 23:43 ` Luiz Augusto von Dentz
2023-06-02 8:21 ` Johan Hovold
2023-07-07 9:41 ` Amit Pundir
2023-07-07 11:08 ` Johan Hovold
2023-07-07 13:42 ` Amit Pundir
2023-07-10 11:44 ` Johan Hovold
2023-07-10 12:22 ` Amit Pundir
2023-07-25 9:41 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-25 14:24 ` Amit Pundir
2023-07-08 14:12 ` Linux regression tracking #adding (Thorsten Leemhuis)
-- strict thread matches above, loose matches on Subject: below --
2023-04-24 13:35 [PATCH 1/2] Bluetooth: fix invalid-bdaddr quirk for non-persistent setup Johan Hovold
2023-04-24 14:33 ` Bluetooth: fix bdaddr quirks 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=647714b2.4a0a0220.add82.cee2@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=johan+linaro@kernel.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 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).