All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hj.tedd.an@gmail.com
Subject: RE: [BlueZ] tools/mgmt-tester: Add test cases for load_long_term_keys command
Date: Thu, 09 Sep 2021 15:53:56 -0700 (PDT)	[thread overview]
Message-ID: <613a9084.1c69fb81.f0418.e21b@mx.google.com> (raw)
In-Reply-To: <20210909223547.164560-1-hj.tedd.an@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.49 seconds
GitLint                       PASS      0.11 seconds
Prep - Setup ELL              PASS      40.41 seconds
Build - Prep                  PASS      0.09 seconds
Build - Configure             PASS      7.10 seconds
Build - Make                  PASS      176.54 seconds
Make Check                    PASS      8.72 seconds
Make Distcheck                PASS      208.03 seconds
Build w/ext ELL - Configure   PASS      7.16 seconds
Build w/ext ELL - Make        PASS      166.08 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
tools/mgmt-tester: Add test cases for load_long_term_keys command
WARNING:LONG_LINE: line length of 82 exceeds 80 columns
#330: FILE: tools/mgmt-tester.c:10927:
+				setup_load_ltks_20_count_1, test_command_generic);

WARNING:LONG_LINE_STRING: line length of 83 exceeds 80 columns
#334: FILE: tools/mgmt-tester.c:10931:
+	test_bredrle("asdf Load Long Term Keys - Success 5 (Power On and 20 keys)",

- total: 0 errors, 2 warnings, 323 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

"[PATCH] tools/mgmt-tester: Add test cases for load_long_term_keys" has style problems, please review.

NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.


##############################
Test: GitLint - PASS
Desc: Run gitlint with rule in .gitlint

##############################
Test: Prep - Setup ELL - PASS
Desc: Clone, build, and install ELL

##############################
Test: Build - Prep - PASS
Desc: Prepare environment for build

##############################
Test: Build - Configure - PASS
Desc: Configure the BlueZ source tree

##############################
Test: Build - Make - PASS
Desc: Build the BlueZ source tree

##############################
Test: Make Check - PASS
Desc: Run 'make check'

##############################
Test: Make Distcheck - PASS
Desc: Run distcheck to check the distribution

##############################
Test: Build w/ext ELL - Configure - PASS
Desc: Configure BlueZ source with '--enable-external-ell' configuration

##############################
Test: Build w/ext ELL - Make - PASS
Desc: Build BlueZ source with '--enable-external-ell' configuration



---
Regards,
Linux Bluetooth


  reply	other threads:[~2021-09-09 22:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 22:35 [BlueZ PATCH] tools/mgmt-tester: Add test cases for load_long_term_keys command Tedd Ho-Jeong An
2021-09-09 22:53 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-09 23:09 Tedd Ho-Jeong An
2021-09-09 23:34 ` [BlueZ] " 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=613a9084.1c69fb81.f0418.e21b@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hj.tedd.an@gmail.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.