From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, thomas@t-8ch.de
Subject: RE: [BlueZ] tools/mpris-proxy: Ship systemd unit file
Date: Tue, 11 May 2021 06:46:08 -0700 (PDT) [thread overview]
Message-ID: <609a8aa0.1c69fb81.f42f4.fe63@mx.google.com> (raw)
In-Reply-To: <20210511132213.150076-1-thomas@t-8ch.de>
[-- Attachment #1: Type: text/plain, Size: 2377 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=480411
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint FAIL 0.13 seconds
Prep - Setup ELL PASS 45.42 seconds
Build - Prep PASS 0.14 seconds
Build - Configure PASS 8.03 seconds
Build - Make PASS 197.02 seconds
Make Check PASS 8.78 seconds
Make Dist PASS 11.48 seconds
Make Dist - Configure PASS 4.92 seconds
Make Dist - Make PASS 79.31 seconds
Build w/ext ELL - Configure PASS 8.09 seconds
Build w/ext ELL - Make PASS 185.67 seconds
Details
##############################
Test: CheckPatch - PASS
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
tools/mpris-proxy: Ship systemd unit file
3: B6 Body message is missing
##############################
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 Dist - PASS
Desc: Run 'make dist' and build the distribution tarball
##############################
Test: Make Dist - Configure - PASS
Desc: Configure the source from distribution tarball
##############################
Test: Make Dist - Make - PASS
Desc: Build the source from distribution tarball
##############################
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
prev parent reply other threads:[~2021-05-11 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 13:22 [PATCH BlueZ] tools/mpris-proxy: Ship systemd unit file Thomas Weißschuh
2021-05-11 13:46 ` bluez.test.bot [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=609a8aa0.1c69fb81.f42f4.fe63@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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