ci: add SPDK/OCF test workflow - #233
Open
robertbaldyga wants to merge 2 commits into
Open
robertbaldyga wants to merge 2 commits into
robertbaldyga wants to merge 2 commits into
Conversation
karlatec
suggested changes
Sep 2, 2026
| contains(inputs.changed_files, '"module/bdev/ocf/') || | ||
| contains(inputs.changed_files, '"test/ocf/') | ||
| runs-on: [self-hosted, unvertical-ocf-vm] | ||
| timeout-minutes: 90 |
Contributor
There was a problem hiding this comment.
Drop it down to 60 like in spdk-common-test.yml? 60 is already very generous, I don't think we'd like to wait more than that.
Author
There was a problem hiding this comment.
This workflow is meant to be used for both per-patch tests (ocf.sh), which should easily fit under 30 minutes, and weekly tests (ocf_all.sh), which already take well over 60 minutes. I'll add parametrization depending on the script used.
| EOF | ||
| ./autobuild.sh ../ocf.conf | ||
|
|
||
| - name: Allocate hugepages |
Contributor
There was a problem hiding this comment.
Copy-paste from spdk-common-tests.yml. Consider moving the script into a file under .github/scripts and running with run: .github/scripts/allocate-hugepages.sh
Contributor
|
PR is in a failing state:
|
karlatec
suggested changes
Sep 2, 2026
karlatec
left a comment
karlatec
left a comment
Contributor
There was a problem hiding this comment.
Forgot to click "Request changes".
Signed-off-by: Robert Baldyga <robert.baldyga@unvertical.com>
Add a workflow which runs the SPDK OCF test suite on an Unvertical self-hosted runner, and hook it into the Gerrit webhook handler. The job only fires for patch sets touching module/bdev/ocf or test/ocf. We do not call autorun.sh, as we want to have control over test scope selection (per-PR vs nightly/weekly). The workflow does it best to be as compatible with autorun.sh as possible. The workflow needs the OCF test rework, which is still in review. Until it gets merged, there is a check that fails the workflow for all the patchsets other than the rework. Signed-off-by: Robert Baldyga <robert.baldyga@unvertical.com>
robertbaldyga
force-pushed
the
unvertical-ocf-workflow
branch
from
September 2, 2026 22:11
001deaf to
f8b625b
Compare
karlatec
approved these changes
Sep 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a workflow which runs the SPDK OCF test suite on an Unvertical self-hosted runner, and hook it into the Gerrit webhook handler. The job only fires for patch sets touching module/bdev/ocf or test/ocf.
We do not call autorun.sh, as we want to have control over test scope selection (per-PR vs nightly/weekly). The workflow does it best to be as compatible with autorun.sh as possible.
The workflow needs the OCF test rework, which is still in review. Until it gets merged, there is a check that fails the workflow for all the patchsets other than the rework.