From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, youwan@nfschina.com
Subject: RE: [v3] Bluetooth: btusb: Add return error code
Date: Thu, 19 Oct 2023 19:15:50 -0700 (PDT) [thread overview]
Message-ID: <6531e2d6.620a0220.dd5b2.2a2d@mx.google.com> (raw)
In-Reply-To: <20231020012233.223650-1-youwan@nfschina.com>
[-- Attachment #1: Type: text/plain, Size: 2346 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=794914
---Test result---
Test Summary:
CheckPatch FAIL 1.09 seconds
GitLint PASS 0.23 seconds
SubjectPrefix PASS 0.06 seconds
BuildKernel PASS 40.95 seconds
CheckAllWarning PASS 45.05 seconds
CheckSparse PASS 51.37 seconds
CheckSmatch PASS 137.07 seconds
BuildKernel32 PASS 39.47 seconds
TestRunnerSetup PASS 617.66 seconds
TestRunner_l2cap-tester PASS 35.72 seconds
TestRunner_iso-tester PASS 64.46 seconds
TestRunner_bnep-tester PASS 12.46 seconds
TestRunner_mgmt-tester FAIL 255.30 seconds
TestRunner_rfcomm-tester PASS 19.88 seconds
TestRunner_sco-tester PASS 22.28 seconds
TestRunner_ioctl-tester PASS 21.75 seconds
TestRunner_mesh-tester PASS 16.15 seconds
TestRunner_smp-tester PASS 17.19 seconds
TestRunner_userchan-tester PASS 13.59 seconds
IncrementalBuild PASS 38.04 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3] Bluetooth: btusb: Add return error code
WARNING: Missing commit description - Add an appropriate one
total: 0 errors, 1 warnings, 11 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/src/13429962.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 497, Passed: 496 (99.8%), Failed: 1, Not Run: 0
Failed Test Cases
LL Privacy - Unpair 1 Timed out 1.936 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-10-20 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 1:22 [PATCH v3] Bluetooth: btusb: Add return error code Youwan Wang
2023-10-20 2:15 ` 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=6531e2d6.620a0220.dd5b2.2a2d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=youwan@nfschina.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 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.