From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>,
Cedric Hombourger <cedric.hombourger@siemens.com>
Subject: [PATCH 9/9] ci: Add github test job to github workflow
Date: Mon, 23 Mar 2026 09:30:39 +0100 [thread overview]
Message-ID: <d528838790f311583bbd3724d3e6b86e01e38e3f.1774254639.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1774254639.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
Decompose the dev-tagged tests into two sets that can be run
independently and execute them as public github actions. This exercise
might be expendable to fast-tagged tests in the future, though likely
not to the full set due to limits of the public runners.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.github/workflows/main.yml | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index e9dd039e..1c54eba2 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -18,10 +18,10 @@ jobs:
contents: read
attestations: write
artifact-metadata: write
- if: github.ref == 'refs/heads/next'
steps:
- name: Check out repo
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+ if: github.ref == 'refs/heads/next'
- name: Check for pre-existing container version
run: |
@@ -32,6 +32,7 @@ jobs:
echo "KAS_VERSION=$KAS_CONTAINER_SCRIPT_VERSION" >> $GITHUB_ENV
echo "BUILD_CONTAINER=true" >> $GITHUB_ENV
fi
+ if: github.ref == 'refs/heads/next'
- name: Set up QEMU
uses: docker/setup-qemu-action@ce360397dd3f832beb865e1373c09c0e9f86d70a # v4.0.0
@@ -70,3 +71,31 @@ jobs:
subject-digest: ${{ steps.push.outputs.digest }}
push-to-registry: true
if: ${{ env.BUILD_CONTAINER }}
+
+ test:
+ name: Run tests
+ runs-on: ubuntu-latest
+ needs: container
+ strategy:
+ matrix:
+ tests: [
+ {name: 'test_dev',
+ spec: 'testsuite/citest.py:test_dev$ testsuite/citest.py:test_dev_run_arm_'},
+ {name: 'test_dev_apps',
+ spec: 'testsuite/citest.py:test_dev_apps testsuite/citest.py:test_dev_rebuild testsuite/citest.py:test_dev_run_amd64_ testsuite/citest.py:test_dev_run_arm64_'}
+ ]
+ steps:
+ - name: Check out repo
+ uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+ - name: Execute run-tests.sh
+ run: |
+ scripts/run-tests.sh --debug ${{ matrix.tests.spec }}
+ - name: Upload logs
+ uses: actions/upload-artifact@bbbca2ddaa5d8feaa63e36b76fdaad77386f024f # v7.0.0
+ if: always()
+ with:
+ name: logs-${{ matrix.tests.name }}
+ path: |
+ build/testsuite/tmp*/work/*/*/*/temp
+ build/testsuite/job-results
+ build/testsuite/vm_start
--
2.47.3
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/d528838790f311583bbd3724d3e6b86e01e38e3f.1774254639.git.jan.kiszka%40siemens.com.
prev parent reply other threads:[~2026-03-23 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 8:30 [PATCH 0/9] Improve testsuite executability, basic GitHub CI 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 1/9] Update kas-container to 5.2 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 2/9] testsuite: Provide a new kas-based test container and wrapper script 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 3/9] testsuite: Install avocado-framework-plugin-varianter-yaml-to-mux in test-container 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 4/9] testsuite: Add squid to test-container 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 5/9] ci: Add github workflow for building and deploying test-container 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 6/9] ci: Switch gitlab-ci to new test-container 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 7/9] CONTRIBUTING: Switch to new run-tests.sh 'Jan Kiszka' via isar-users
2026-03-26 17:01 ` Zhihang Wei
2026-03-26 18:41 ` 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` [PATCH 8/9] testsuite: Drop KFAIL from trixie tests 'Jan Kiszka' via isar-users
2026-03-23 8:30 ` 'Jan Kiszka' via isar-users [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=d528838790f311583bbd3724d3e6b86e01e38e3f.1774254639.git.jan.kiszka@siemens.com \
--to=isar-users@googlegroups.com \
--cc=cedric.hombourger@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox