From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Bluetooth: ISO: Handle PA sync when no BIGInfo reports are generated
Date: Tue, 02 Apr 2024 05:42:28 -0700 (PDT) [thread overview]
Message-ID: <660bfd34.050a0220.54a88.a53e@mx.google.com> (raw)
In-Reply-To: <20240402113931.3164-2-iulia.tanasescu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 2780 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=840593
---Test result---
Test Summary:
CheckPatch PASS 3.18 seconds
GitLint PASS 0.71 seconds
SubjectPrefix PASS 0.38 seconds
BuildKernel PASS 29.86 seconds
CheckAllWarning PASS 32.45 seconds
CheckSparse WARNING 38.07 seconds
CheckSmatch FAIL 41.55 seconds
BuildKernel32 PASS 28.85 seconds
TestRunnerSetup PASS 519.08 seconds
TestRunner_l2cap-tester PASS 17.95 seconds
TestRunner_iso-tester FAIL 38.42 seconds
TestRunner_bnep-tester PASS 4.69 seconds
TestRunner_mgmt-tester PASS 110.75 seconds
TestRunner_rfcomm-tester PASS 7.29 seconds
TestRunner_sco-tester PASS 14.86 seconds
TestRunner_ioctl-tester PASS 7.67 seconds
TestRunner_mesh-tester PASS 5.83 seconds
TestRunner_smp-tester PASS 7.54 seconds
TestRunner_userchan-tester PASS 10.42 seconds
IncrementalBuild PASS 51.97 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
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
##############################
Test: TestRunner_iso-tester - FAIL
Desc: Run iso-tester with test-runner
Output:
Total: 117, Passed: 116 (99.1%), Failed: 1, Not Run: 0
Failed Test Cases
ISO Connect2 Suspend - Success Failed 8.248 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-04-02 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 11:39 [PATCH 0/2] Bluetooth: ISO: Handle PA sync when no BIGInfo reports are generated Iulia Tanasescu
2024-04-02 11:39 ` [PATCH 1/2] Bluetooth: ISO: Make iso_get_sock_listen generic Iulia Tanasescu
2024-04-02 12:42 ` bluez.test.bot [this message]
2024-04-02 15:43 ` Luiz Augusto von Dentz
2024-04-02 11:39 ` [PATCH 2/2] Bluetooth: ISO: Handle PA sync when no BIGInfo reports are generated Iulia Tanasescu
2024-04-02 17:30 ` [PATCH 0/2] " 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=660bfd34.050a0220.54a88.a53e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=iulia.tanasescu@nxp.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 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).