From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pav@iki.fi
Subject: RE: [v2] Bluetooth: fix connection setup in l2cap_connect
Date: Sun, 09 Jun 2024 08:32:05 -0700 (PDT) [thread overview]
Message-ID: <6665caf5.050a0220.eefa4.6b4f@mx.google.com> (raw)
In-Reply-To: <ad69720e0ba720209cb04240fbc3c5ff059accbc.1717945321.git.pav@iki.fi>
[-- Attachment #1: Type: text/plain, Size: 2849 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=860256
---Test result---
Test Summary:
CheckPatch PASS 0.79 seconds
GitLint FAIL 0.54 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 30.75 seconds
CheckAllWarning PASS 33.22 seconds
CheckSparse PASS 39.03 seconds
CheckSmatch FAIL 35.74 seconds
BuildKernel32 PASS 28.69 seconds
TestRunnerSetup PASS 520.59 seconds
TestRunner_l2cap-tester PASS 20.24 seconds
TestRunner_iso-tester PASS 32.85 seconds
TestRunner_bnep-tester PASS 4.74 seconds
TestRunner_mgmt-tester PASS 112.00 seconds
TestRunner_rfcomm-tester PASS 7.42 seconds
TestRunner_sco-tester PASS 14.92 seconds
TestRunner_ioctl-tester PASS 7.73 seconds
TestRunner_mesh-tester PASS 5.82 seconds
TestRunner_smp-tester PASS 6.79 seconds
TestRunner_userchan-tester PASS 4.90 seconds
IncrementalBuild PASS 27.56 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v2] Bluetooth: fix connection setup in l2cap_connect
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
18: B2 Line has trailing whitespace: " "
##############################
Test: CheckSmatch - FAIL
Desc: Run smatch tool with source
Output:
Segmentation fault (core dumped)
make[4]: *** [scripts/Makefile.build:244: net/bluetooth/hci_core.o] Error 139
make[4]: *** Deleting file 'net/bluetooth/hci_core.o'
make[3]: *** [scripts/Makefile.build:485: net/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:485: net] Error 2
make[2]: *** Waiting for unfinished jobs....
Segmentation fault (core dumped)
make[4]: *** [scripts/Makefile.build:244: drivers/bluetooth/bcm203x.o] Error 139
make[4]: *** Deleting file 'drivers/bluetooth/bcm203x.o'
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:485: drivers/bluetooth] Error 2
make[2]: *** [scripts/Makefile.build:485: drivers] Error 2
make[1]: *** [/github/workspace/src/src/Makefile:1919: .] Error 2
make: *** [Makefile:240: __sub-make] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-06-09 15:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 20:46 Bluetooth Kernel Bug: After connecting either HFP/HSP or A2DP is not available (Regression in 6.9.3, 6.8.12) Timo Schröder
2024-06-06 21:23 ` Luiz Augusto von Dentz
2024-06-07 6:10 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-07 21:43 ` Timo Schröder
2024-06-07 22:00 ` Luiz Augusto von Dentz
2024-06-08 12:24 ` Timo Schröder
2024-06-07 3:55 ` Paul Menzel
2024-06-08 12:23 ` Timo Schröder
2024-06-08 21:59 ` [PATCH] Bluetooth: fix connection setup in l2cap_connect Pauli Virtanen
2024-06-08 22:31 ` bluez.test.bot
2024-06-09 12:49 ` [PATCH] " Timo Schröder
2024-06-09 15:01 ` Pauli Virtanen
2024-06-09 15:06 ` [PATCH v2] " Pauli Virtanen
2024-06-09 15:32 ` bluez.test.bot [this message]
2024-06-09 16:29 ` Timo Schröder
2024-06-09 17:41 ` Luiz Augusto von Dentz
2024-06-10 14:03 ` patchwork-bot+bluetooth
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=6665caf5.050a0220.eefa4.6b4f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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).