From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, tot0roprog@gmail.com
Subject: RE: [BlueZ] mesh: Add config for provisioning algorithms
Date: Tue, 10 Sep 2024 19:41:54 -0700 (PDT) [thread overview]
Message-ID: <66e10372.050a0220.22ea50.d904@mx.google.com> (raw)
In-Reply-To: <66e0e4e6.170a0220.de5c1.1970@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1617 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=889107
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint PASS 0.35 seconds
BuildEll PASS 26.18 seconds
BluezMake PASS 1880.05 seconds
MakeCheck PASS 13.93 seconds
MakeDistcheck FAIL 73.82 seconds
CheckValgrind PASS 269.96 seconds
CheckSmatch PASS 378.41 seconds
bluezmakeextell PASS 128.60 seconds
IncrementalBuild PASS 1651.58 seconds
ScanBuild PASS 1121.65 seconds
Details
##############################
Test: MakeDistcheck - FAIL
Desc: Run Bluez Make Distcheck
Output:
Package cups was not found in the pkg-config search path.
Perhaps you should add the directory containing `cups.pc'
to the PKG_CONFIG_PATH environment variable
No package 'cups' found
../../mesh/mesh-config-json.c:31:10: fatal error: mesh/missing.h: No such file or directory
31 | #include "mesh/missing.h"
| ^~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [Makefile:7857: mesh/mesh-config-json.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:4681: all] Error 2
make: *** [Makefile:12233: distcheck] Error 1
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2024-09-11 2:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 0:31 [PATCH BlueZ] mesh: Add config for provisioning algorithms Junho Lee
2024-09-11 2:41 ` 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=66e10372.050a0220.22ea50.d904@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=tot0roprog@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.