linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: Yun-hao Chung <howardchung@google.com>
Subject: Re: [Bluez,v2] gatt-db: fix service in range check
Date: Wed, 28 Jul 2021 10:38:35 -0700	[thread overview]
Message-ID: <CABBYNZL0R_1XENCaUkn-+vQp6sSh-8A+5Afx7otmhHVzzQv9Bw@mail.gmail.com> (raw)
In-Reply-To: <61015f06.1c69fb81.1f3ca.029a@mx.google.com>

Hi Howard,

On Wed, Jul 28, 2021 at 6:45 AM <bluez.test.bot@gmail.com> wrote:
>
> 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=522683
>
> ---Test result---
>
> Test Summary:
> CheckPatch                    PASS      0.29 seconds
> GitLint                       PASS      0.11 seconds
> Prep - Setup ELL              PASS      40.81 seconds
> Build - Prep                  PASS      0.09 seconds
> Build - Configure             PASS      7.35 seconds
> Build - Make                  PASS      176.55 seconds
> Make Check                    FAIL      8.72 seconds
> Make Distcheck                FAIL      190.86 seconds

These will need to be fixed, I suspect removing the check completely
is wrong since the condition svc_start < foreach_data->start is not
tested.

> Build w/ext ELL - Configure   PASS      7.24 seconds
> Build w/ext ELL - Make        PASS      165.61 seconds
>
> Details
> ##############################
> Test: CheckPatch - PASS
> Desc: Run checkpatch.pl script with rule in .checkpatch.conf
>
> ##############################
> 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 - FAIL
> Desc: Run 'make check'
> Output:
> ./test-driver: line 107: 28579 Aborted                 (core dumped) "$@" > $log_file 2>&1
> make[3]: *** [Makefile:9910: test-suite.log] Error 1
> make[2]: *** [Makefile:10018: check-TESTS] Error 2
> make[1]: *** [Makefile:10412: check-am] Error 2
> make: *** [Makefile:10414: check] Error 2
>
>
> ##############################
> Test: Make Distcheck - FAIL
> Desc: Run distcheck to check the distribution
> Output:
> ../../test-driver: line 107: 47458 Aborted                 (core dumped) "$@" > $log_file 2>&1
> make[4]: *** [Makefile:9910: test-suite.log] Error 1
> make[3]: *** [Makefile:10018: check-TESTS] Error 2
> make[2]: *** [Makefile:10412: check-am] Error 2
> make[1]: *** [Makefile:10414: check] Error 2
> make: *** [Makefile:10335: distcheck] Error 1
>
>
> ##############################
> 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
>


-- 
Luiz Augusto von Dentz

      reply	other threads:[~2021-07-28 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 13:23 [Bluez PATCH v2] gatt-db: fix service in range check Howard Chung
2021-07-28 13:43 ` [Bluez,v2] " bluez.test.bot
2021-07-28 17:38   ` Luiz Augusto von Dentz [this message]

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=CABBYNZL0R_1XENCaUkn-+vQp6sSh-8A+5Afx7otmhHVzzQv9Bw@mail.gmail.com \
    --to=luiz.dentz@gmail.com \
    --cc=howardchung@google.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).