From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, inga.stotland@intel.com
Subject: RE: Framework for non-interactive mesh test
Date: Wed, 24 Mar 2021 23:45:26 -0700 (PDT) [thread overview]
Message-ID: <605c3186.1c69fb81.142f5.5521@mx.google.com> (raw)
In-Reply-To: <20210319203825.459070-2-inga.stotland@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2423 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=451875
---Test result---
##############################
Test: CheckPatch - PASS
##############################
Test: CheckGitLint - PASS
##############################
Test: CheckBuild: Setup ELL - PASS
##############################
Test: CheckBuild: Setup - PASS
##############################
Test: CheckBuild - PASS
##############################
Test: MakeCheck - PASS
##############################
Test: CheckBuild w/external ell - FAIL
Output:
/usr/bin/ld: tools/mesh-cfgtest.o: in function `join_complete':
/github/workspace/src2/tools/mesh-cfgtest.c:703: undefined reference to `l_tester_get_stage'
/usr/bin/ld: tools/mesh-cfgtest.o: in function `dev_msg_recv_call':
/github/workspace/src2/tools/mesh-cfgtest.c:967: undefined reference to `l_tester_get_stage'
/usr/bin/ld: tools/mesh-cfgtest.o: in function `attach_node_reply':
/github/workspace/src2/tools/mesh-cfgtest.c:630: undefined reference to `l_tester_get_stage'
/usr/bin/ld: tools/mesh-cfgtest.o: in function `import_subnet_reply':
/github/workspace/src2/tools/mesh-cfgtest.c:579: undefined reference to `l_tester_get_stage'
/usr/bin/ld: tools/mesh-cfgtest.o: in function `create_appkey_reply':
/github/workspace/src2/tools/mesh-cfgtest.c:480: undefined reference to `l_tester_get_stage'
/usr/bin/ld: tools/mesh-cfgtest.o:/github/workspace/src2/tools/mesh-cfgtest.c:356: more undefined references to `l_tester_get_stage' follow
/usr/bin/ld: tools/mesh-cfgtest.o: in function `main':
/github/workspace/src2/tools/mesh-cfgtest.c:1411: undefined reference to `l_tester_add_full'
/usr/bin/ld: /github/workspace/src2/tools/mesh-cfgtest.c:1415: undefined reference to `l_tester_add_full'
/usr/bin/ld: /github/workspace/src2/tools/mesh-cfgtest.c:1419: undefined reference to `l_tester_add_full'
/usr/bin/ld: /github/workspace/src2/tools/mesh-cfgtest.c:1423: undefined reference to `l_tester_add_full'
/usr/bin/ld: /github/workspace/src2/tools/mesh-cfgtest.c:1427: undefined reference to `l_tester_add_full'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:5884: tools/mesh-cfgtest] Error 1
make: *** [Makefile:4058: all] Error 2
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-03-25 6:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 20:38 [PATCH BlueZ v4 0/2] Framework for non-interactive mesh test Inga Stotland
2021-03-19 20:38 ` [PATCH BlueZ v4 1/2] mesh: Add unit test IO Inga Stotland
2021-03-19 20:53 ` Framework for non-interactive mesh test bluez.test.bot
2021-03-25 6:45 ` bluez.test.bot [this message]
2021-04-05 17:05 ` bluez.test.bot
2021-03-19 20:38 ` [PATCH BlueZ v4 2/2] tools/mesh-cfgtest: Non-iteractive test for mesh Inga Stotland
2021-04-10 17:33 ` [PATCH BlueZ v4 0/2] Framework for non-interactive mesh test Gix, Brian
-- strict thread matches above, loose matches on Subject: below --
2021-02-06 5:50 [PATCH BlueZ v3 1/3] shared/tester: Create ell-based version of tester code Inga Stotland
2021-02-06 6:36 ` Framework for non-interactive mesh test bluez.test.bot
2021-02-06 4:43 [PATCH BlueZ v2 1/3] shared/tester: Create ell-based version of tester code Inga Stotland
2021-02-06 4:58 ` Framework for non-interactive mesh test bluez.test.bot
2021-02-06 1:31 [PATCH BlueZ 1/3] shared/tester: Create ell-based version of tester code Inga Stotland
2021-02-06 3:35 ` Framework for non-interactive mesh test 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=605c3186.1c69fb81.142f5.5521@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=inga.stotland@intel.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.