All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, surban@surban.net
Subject: RE: l2cap: do not return LE flow credits when buf full
Date: Fri, 05 Apr 2024 03:33:15 -0700 (PDT)	[thread overview]
Message-ID: <660fd36b.050a0220.311bf.27d9@mx.google.com> (raw)
In-Reply-To: <20240405093834.63666-1-surban@surban.net>

[-- Attachment #1: Type: text/plain, Size: 2479 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=841735

---Test result---

Test Summary:
CheckPatch                    PASS      1.13 seconds
GitLint                       PASS      0.29 seconds
SubjectPrefix                 FAIL      0.36 seconds
BuildKernel                   PASS      29.62 seconds
CheckAllWarning               PASS      32.32 seconds
CheckSparse                   PASS      37.84 seconds
CheckSmatch                   FAIL      34.71 seconds
BuildKernel32                 PASS      28.82 seconds
TestRunnerSetup               PASS      517.48 seconds
TestRunner_l2cap-tester       PASS      22.31 seconds
TestRunner_iso-tester         PASS      32.29 seconds
TestRunner_bnep-tester        PASS      4.77 seconds
TestRunner_mgmt-tester        PASS      108.24 seconds
TestRunner_rfcomm-tester      PASS      7.13 seconds
TestRunner_sco-tester         PASS      14.91 seconds
TestRunner_ioctl-tester       PASS      7.51 seconds
TestRunner_mesh-tester        PASS      5.65 seconds
TestRunner_smp-tester         PASS      6.60 seconds
TestRunner_userchan-tester    PASS      4.86 seconds
IncrementalBuild              PASS      27.56 seconds

Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
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


  parent reply	other threads:[~2024-04-05 10:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05  9:38 [PATCH] l2cap: do not return LE flow credits when buf full Sebastian Urban
2024-04-05 10:25 ` [PATCH v2] Bluetooth: keep LE flow credits when recvbuf full Sebastian Urban
2024-04-05 10:56   ` [v2] " bluez.test.bot
2024-04-05 15:30   ` [PATCH v2] " Luiz Augusto von Dentz
2024-04-07 18:57     ` Sebastian Urban
2024-04-05 10:33 ` bluez.test.bot [this message]
2024-04-08  0:56 ` [PATCH v3] Bluetooth: compute LE flow credits based on recvbuf space Sebastian Urban
2024-04-08  1:47   ` [v3] " bluez.test.bot
2024-04-08  9:41   ` [PATCH v4] " Sebastian Urban
2024-04-08 10:35     ` [v4] " 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=660fd36b.050a0220.311bf.27d9@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=surban@surban.net \
    /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.