All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, iulia.tanasescu@nxp.com
Subject: RE: Add additional Broadcast tests/options
Date: Wed, 19 Apr 2023 08:30:07 -0700 (PDT)	[thread overview]
Message-ID: <644008ff.9d0a0220.dfbca.1c74@mx.google.com> (raw)
In-Reply-To: <20230419134354.61950-2-iulia.tanasescu@nxp.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.38 seconds
GitLint                       PASS      0.86 seconds
BuildEll                      PASS      27.03 seconds
BluezMake                     PASS      805.57 seconds
MakeCheck                     PASS      10.96 seconds
MakeDistcheck                 PASS      153.72 seconds
CheckValgrind                 PASS      247.22 seconds
CheckSmatch                   WARNING   328.39 seconds
bluezmakeextell               PASS      98.60 seconds
IncrementalBuild              PASS      1890.85 seconds
ScanBuild                     WARNING   995.64 seconds

Details
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
monitor/packet.c: note: in included file:monitor/display.h:82:26: warning: Variable length array is used.monitor/packet.c:1800:26: warning: Variable length array is used.monitor/packet.c: note: in included file:monitor/bt.h:3552:52: warning: array of flexible structuresmonitor/bt.h:3540:40: warning: array of flexible structuresemulator/btdev.c:413:29: warning: Variable length array is used.emulator/bthost.c:584:28: warning: Variable length array is used.emulator/bthost.c:741:28: warning: Variable length array is used.
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
emulator/btdev.c:1074:10: warning: Although the value stored to 'conn' is used in the enclosing expression, the value is never actually read from 'conn'
        while ((conn = queue_find(dev->conns, match_handle,
                ^      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
emulator/btdev.c:1386:13: warning: Access to field 'dev' results in a dereference of a null pointer (loaded from variable 'conn')
        send_event(conn->dev, BT_HCI_EVT_AUTH_COMPLETE, &ev, sizeof(ev));
                   ^~~~~~~~~
2 warnings generated.



---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-04-19 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 13:43 [PATCH BlueZ 0/3] Add additional Broadcast tests/options Iulia Tanasescu
2023-04-19 13:43 ` [PATCH BlueZ 1/3] monitor/packet: Fix BIG encryption decoding Iulia Tanasescu
2023-04-19 15:30   ` bluez.test.bot [this message]
2023-04-19 13:43 ` [PATCH BlueZ 2/3] tools/isotest: Add BIG encryption options Iulia Tanasescu
2023-04-19 13:43 ` [PATCH BlueZ 3/3] tools/iso-tester: Add Broadcast tests for encrypted BIG Iulia Tanasescu
2023-04-19 21:20 ` [PATCH BlueZ 0/3] Add additional Broadcast tests/options 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=644008ff.9d0a0220.dfbca.1c74@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 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.