From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/action-ci] b6dd0b: Add instructions for localci usage
Date: Mon, 14 Sep 2026 07:44:23 -0700 [thread overview]
Message-ID: <bluez/action-ci/push/refs/heads/main/fa1938-e0b8a6@github.com> (raw)
Branch: refs/heads/main
Home: https://github.com/bluez/action-ci
Commit: b6dd0b29c7e56b829b62f33377e321298a0c8358
https://github.com/bluez/action-ci/commit/b6dd0b29c7e56b829b62f33377e321298a0c8358
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-14 (Mon, 14 Sep 2026)
Changed paths:
M README.md
Log Message:
-----------
Add instructions for localci usage
Commit: f0821a6828397be6a7062910be3d6071ddcb5e29
https://github.com/bluez/action-ci/commit/f0821a6828397be6a7062910be3d6071ddcb5e29
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-14 (Mon, 14 Sep 2026)
Changed paths:
M entrypoint.sh
Log Message:
-----------
entrypoint: adjust expected bluez source dir for localci
For the localci local dry run mode of entrypoint.sh, make bluez source
dir the same in kernel and user modes.
Commit: ba88cf65ea0ff1d48662e6b960cf163550291778
https://github.com/bluez/action-ci/commit/ba88cf65ea0ff1d48662e6b960cf163550291778
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-14 (Mon, 14 Sep 2026)
Changed paths:
M ci.py
Log Message:
-----------
Log full errors in test runner
Make debugging the CI runners easier by logging any exceptions raised.
Commit: 3bbb6fe6c03d1bc467d230d2114f47c5c1b19697
https://github.com/bluez/action-ci/commit/3bbb6fe6c03d1bc467d230d2114f47c5c1b19697
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-14 (Mon, 14 Sep 2026)
Changed paths:
M ci/__init__.py
A ci/testfunctional.py
Log Message:
-----------
Add hook for running test/test-functional tester
Commit: e0b8a65c986560e21d609b5d75792e214d72b8fa
https://github.com/bluez/action-ci/commit/e0b8a65c986560e21d609b5d75792e214d72b8fa
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-14 (Mon, 14 Sep 2026)
Changed paths:
M ci.py
Log Message:
-----------
ci.py: add TestFunctional to user tests
Add TestFunctional to user tests. This includes kernel build.
Compare: https://github.com/bluez/action-ci/compare/fa19384d4c70...e0b8a65c9865
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/action-ci/settings/notifications
reply other threads:[~2026-09-14 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/action-ci/push/refs/heads/main/fa1938-e0b8a6@github.com \
--to=noreply@github.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.