All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wzhmmmmm@gmail.com
Subject: RE: Bluetooth: Fix double free in hci_conn_cleanup
Date: Thu, 09 Mar 2023 02:02:10 -0800 (PST)	[thread overview]
Message-ID: <6409aea2.050a0220.6601f.8ca4@mx.google.com> (raw)
In-Reply-To: <20230309093442.74618-1-wzhmmmmm@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.76 seconds
GitLint                       FAIL      0.76 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      39.46 seconds
CheckAllWarning               PASS      43.50 seconds
CheckSparse                   PASS      48.67 seconds
CheckSmatch                   PASS      129.92 seconds
BuildKernel32                 PASS      39.50 seconds
TestRunnerSetup               PASS      543.39 seconds
TestRunner_l2cap-tester       PASS      18.91 seconds
TestRunner_iso-tester         PASS      24.66 seconds
TestRunner_bnep-tester        PASS      7.19 seconds
TestRunner_mgmt-tester        FAIL      130.80 seconds
TestRunner_rfcomm-tester      PASS      10.79 seconds
TestRunner_sco-tester         PASS      10.10 seconds
TestRunner_ioctl-tester       FAIL      12.00 seconds
TestRunner_mesh-tester        PASS      9.13 seconds
TestRunner_smp-tester         PASS      9.75 seconds
TestRunner_userchan-tester    PASS      7.58 seconds
IncrementalBuild              PASS      36.34 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: Fix double free in hci_conn_cleanup

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
32: B1 Line exceeds max length (87>80): "Link: https://syzkaller.appspot.com/bug?id=1bb51491ca5df96a5f724899d1dbb87afda61419 [1]"
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 494, Passed: 489 (99.0%), Failed: 5, Not Run: 0

Failed Test Cases
Read Ext Controller Info 1                           Failed       0.144 seconds
Read Ext Controller Info 2                           Failed       0.176 seconds
Read Ext Controller Info 3                           Failed       0.148 seconds
Read Ext Controller Info 4                           Failed       0.144 seconds
Read Ext Controller Info 5                           Failed       0.180 seconds
##############################
Test: TestRunner_ioctl-tester - FAIL
Desc: Run ioctl-tester with test-runner
Output:
No test result found


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-03-09 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09  9:34 [PATCH] Bluetooth: Fix double free in hci_conn_cleanup ZhengHan Wang
2023-03-09 10:02 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-30 22:03 Luiz Augusto von Dentz
2023-03-30 22:32 ` bluez.test.bot
2023-03-30 22:02 [PATCH] " Luiz Augusto von Dentz
2023-03-30 22:32 ` bluez.test.bot
2023-03-09  7:46 [PATCH] " ZhengHan Wang
2023-03-09  8:43 ` 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=6409aea2.050a0220.6601f.8ca4@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=wzhmmmmm@gmail.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.