Skip to content

Commit 5121c4d

Browse files
kawasakikawasaki
committed
adding ci files
1 parent e7c375b commit 5121c4d

File tree

5 files changed

+1005
-0
lines changed

5 files changed

+1005
-0
lines changed

‎.github/workflows/run-blktests.yml‎

Lines changed: 182 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,182 @@
1+
# SPDX-License-Identifier: GPL-2.0-or-later
2+
#
3+
# Copyright (c) 2025 Western Digital Corporation or its affiliates.
4+
#
5+
# Authors: Dennis Maisenbacher ([email protected])
6+
7+
name: Run blktests
8+
9+
on:
10+
pull_request:
11+
12+
concurrency:
13+
group: ci-test-${{ github.ref_name }}
14+
15+
env:
16+
KERNEL_REF: "${{ github.event.pull_request.head.sha }}"
17+
KERNEL_TREE: "https://github.com/${{ github.repository }}"
18+
19+
#This workflow requires an actions-runner-controllers (ARC) to be active.
20+
#The k8s cluster of this ARC needs KubeVirt to be installed.
21+
jobs:
22+
build-and-test-kernel:
23+
#This step runs in a container in the k8s cluster
24+
runs-on: arc-vm-linux-blktests
25+
steps:
26+
- name: Checkout blktests-ci
27+
uses: actions/checkout@v4
28+
with:
29+
repository: linux-blktests/blktests-ci
30+
path: blktests-ci
31+
32+
- name: Build kernel and package it into a containerimage
33+
run: |
34+
cd blktests-ci/playbooks/roles/kernel-builder-k8s-job/templates
35+
docker build \
36+
--build-arg KERNEL_TREE=${KERNEL_TREE} \
37+
--build-arg KERNEL_REF=${KERNEL_REF} \
38+
-t linux-kernel-containerdisk \
39+
-f Dockerfile.linux-kernel-containerdisk . 2>&1 | tee build.log
40+
#Setting KERNEL_VERSION var which is latern needed for notifying the VM what kernel to pick up
41+
cat build.log | grep KERNEL_VERSION | awk '{print $3}' | grep KERNEL_VERSION >> $GITHUB_ENV
42+
43+
- name: Push the new Fedora containerimage with the freshly build kernel
44+
run: |
45+
docker tag linux-kernel-containerdisk registry-service.docker-registry.svc.cluster.local/linux-kernel-containerdisk:${KERNEL_VERSION}
46+
docker push registry-service.docker-registry.svc.cluster.local/linux-kernel-containerdisk:${KERNEL_VERSION}
47+
48+
- name: Run in VM
49+
uses: ./blktests-ci/.github/actions/kubevirt-action
50+
with:
51+
kernel_version: ${{ env.KERNEL_VERSION }}
52+
vm_artifact_upload_dir: blktests/results
53+
run_cmds: |
54+
#Print VM debug info
55+
uname -a
56+
cat /etc/os-release
57+
lsblk
58+
59+
#Install build dependencies for blktests
60+
sudo dnf install -y gcc \
61+
clang \
62+
make \
63+
util-linux \
64+
llvm \
65+
gawk \
66+
fio \
67+
udev \
68+
kmod \
69+
coreutils \
70+
gcc \
71+
gzip \
72+
e2fsprogs \
73+
xfsprogs \
74+
f2fs-tools \
75+
btrfs-progs \
76+
device-mapper-multipath \
77+
blktrace \
78+
kernel-headers \
79+
liburing \
80+
liburing-devel \
81+
nbd \
82+
device-mapper \
83+
ktls-utils \
84+
dosfstools \
85+
bc \
86+
libnl3-cli \
87+
cryptsetup \
88+
sg3_utils \
89+
pciutils \
90+
unzip \
91+
jq \
92+
nvme-cli \
93+
git \
94+
wget \
95+
pkgconf \
96+
libudev-devel
97+
98+
git clone https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git
99+
cd mdadm
100+
git checkout d764c4829947923142a83251296d04edaee7d2f7
101+
make -j$(nproc)
102+
sudo make install
103+
104+
cd -
105+
git clone https://github.com/linux-blktests/blktests.git
106+
107+
cd blktests
108+
git checkout ci
109+
make
110+
111+
#ATTENTION! This section formats all available NVMe devices. Be careful when changing the `runs-on` tag!
112+
#This step runs in a VM with the previously compiled kernel in the k8s cluster
113+
114+
failed=0
115+
rm -f all_failures
116+
117+
# Run blktests block group
118+
cat > config << EOF
119+
TEST_DEVS=(${BDEV0})
120+
EOF
121+
export RUN_ZONED_TESTS=1
122+
sudo ./check block || failed=1
123+
test -f results/failures && cat results/failures >> all_failures
124+
125+
# Run blktests nvme group
126+
#cat > config << EOF
127+
#TEST_DEVS=(${BDEV0})
128+
#NVMET_TRTYPES="loop rdma"
129+
#EXCLUDE=(nvme/014 nvme/038 nvme/057 nvme/058)
130+
#EOF
131+
#sudo ./check nvme || failed=1
132+
#test -f results/failures && cat results/failures >> all_failures
133+
134+
# Run blktests scsi group
135+
cat > config << EOF
136+
TEST_DEVS=()
137+
export RUN_ZONED_TESTS=1
138+
EOF
139+
sudo ./check scsi || failed=1
140+
test -f results/failures && cat results/failures >> all_failures
141+
142+
# Run blktests misc groups
143+
cat > config << EOF
144+
TEST_DEVS=()
145+
EOF
146+
sudo ./check dm loop md throtl ublk || failed=1
147+
test -f results/failures && cat results/failures >> all_failures
148+
149+
# Run ZBD blktests without TEST_DEVS
150+
cat > config << EOF
151+
TEST_DEVS=()
152+
EXCLUDE=(zbd/009)
153+
EOF
154+
export RUN_ZONED_TESTS=1
155+
sudo ./check zbd || failed=1
156+
test -f results/failures && cat results/failures >> all_failures
157+
158+
# Run ZBD blktests with TEST_DEVS
159+
cat > config << EOF
160+
TEST_DEVS=(${ZBD0})
161+
DEVICE_ONLY=1
162+
EOF
163+
164+
export RUN_ZONED_TESTS=1
165+
sudo ./check zbd || failed=1
166+
test -f results/failures && cat results/failures >> all_failures
167+
168+
# Run blktests srp group
169+
#cat > config << EOF
170+
#TEST_DEVS=()
171+
#EOF
172+
#sudo ./check srp || failed=1
173+
#test -f results/failures && cat results/failures >> all_failures
174+
175+
# Mark blktests completion for KPD report
176+
echo "KPD: blktests completed"
177+
178+
# Output failures for KPD report
179+
test -f all_failures && echo "KPD: Failures:" && cat all_failures
180+
181+
echo "KPD: blktests status: ${failed}"
182+
exit $failed

‎CODE_OF_CONDUCT.md‎

Lines changed: 134 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
2+
# Contributor Covenant Code of Conduct
3+
4+
## Our Pledge
5+
6+
We as members, contributors, and leaders pledge to make participation in our
7+
community a harassment-free experience for everyone, regardless of age, body
8+
size, visible or invisible disability, ethnicity, sex characteristics, gender
9+
identity and expression, level of experience, education, socio-economic status,
10+
nationality, personal appearance, race, caste, color, religion, or sexual
11+
identity and orientation.
12+
13+
We pledge to act and interact in ways that contribute to an open, welcoming,
14+
diverse, inclusive, and healthy community.
15+
16+
## Our Standards
17+
18+
Examples of behavior that contributes to a positive environment for our
19+
community include:
20+
21+
* Demonstrating empathy and kindness toward other people
22+
* Being respectful of differing opinions, viewpoints, and experiences
23+
* Giving and gracefully accepting constructive feedback
24+
* Accepting responsibility and apologizing to those affected by our mistakes,
25+
and learning from the experience
26+
* Focusing on what is best not just for us as individuals, but for the overall
27+
community
28+
29+
Examples of unacceptable behavior include:
30+
31+
* The use of sexualized language or imagery, and sexual attention or advances of
32+
any kind
33+
* Trolling, insulting or derogatory comments, and personal or political attacks
34+
* Public or private harassment
35+
* Publishing others' private information, such as a physical or email address,
36+
without their explicit permission
37+
* Other conduct which could reasonably be considered inappropriate in a
38+
professional setting
39+
40+
## Enforcement Responsibilities
41+
42+
Community leaders are responsible for clarifying and enforcing our standards of
43+
acceptable behavior and will take appropriate and fair corrective action in
44+
response to any behavior that they deem inappropriate, threatening, offensive,
45+
or harmful.
46+
47+
Community leaders have the right and responsibility to remove, edit, or reject
48+
comments, commits, code, wiki edits, issues, and other contributions that are
49+
not aligned to this Code of Conduct, and will communicate reasons for moderation
50+
decisions when appropriate.
51+
52+
## Scope
53+
54+
This Code of Conduct applies within all community spaces, and also applies when
55+
an individual is officially representing the community in public spaces.
56+
Examples of representing our community include using an official email address,
57+
posting via an official social media account, or acting as an appointed
58+
representative at an online or offline event.
59+
60+
## Enforcement
61+
62+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
63+
reported to the community leaders responsible for enforcement at
64+
[email protected].
65+
All complaints will be reviewed and investigated promptly and fairly.
66+
67+
All community leaders are obligated to respect the privacy and security of the
68+
reporter of any incident.
69+
70+
## Enforcement Guidelines
71+
72+
Community leaders will follow these Community Impact Guidelines in determining
73+
the consequences for any action they deem in violation of this Code of Conduct:
74+
75+
### 1. Correction
76+
77+
**Community Impact**: Use of inappropriate language or other behavior deemed
78+
unprofessional or unwelcome in the community.
79+
80+
**Consequence**: A private, written warning from community leaders, providing
81+
clarity around the nature of the violation and an explanation of why the
82+
behavior was inappropriate. A public apology may be requested.
83+
84+
### 2. Warning
85+
86+
**Community Impact**: A violation through a single incident or series of
87+
actions.
88+
89+
**Consequence**: A warning with consequences for continued behavior. No
90+
interaction with the people involved, including unsolicited interaction with
91+
those enforcing the Code of Conduct, for a specified period of time. This
92+
includes avoiding interactions in community spaces as well as external channels
93+
like social media. Violating these terms may lead to a temporary or permanent
94+
ban.
95+
96+
### 3. Temporary Ban
97+
98+
**Community Impact**: A serious violation of community standards, including
99+
sustained inappropriate behavior.
100+
101+
**Consequence**: A temporary ban from any sort of interaction or public
102+
communication with the community for a specified period of time. No public or
103+
private interaction with the people involved, including unsolicited interaction
104+
with those enforcing the Code of Conduct, is allowed during this period.
105+
Violating these terms may lead to a permanent ban.
106+
107+
### 4. Permanent Ban
108+
109+
**Community Impact**: Demonstrating a pattern of violation of community
110+
standards, including sustained inappropriate behavior, harassment of an
111+
individual, or aggression toward or disparagement of classes of individuals.
112+
113+
**Consequence**: A permanent ban from any sort of public interaction within the
114+
community.
115+
116+
## Attribution
117+
118+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119+
version 2.1, available at
120+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121+
122+
Community Impact Guidelines were inspired by
123+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124+
125+
For answers to common questions about this code of conduct, see the FAQ at
126+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127+
[https://www.contributor-covenant.org/translations][translations].
128+
129+
[homepage]: https://www.contributor-covenant.org
130+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131+
[Mozilla CoC]: https://github.com/mozilla/diversity
132+
[FAQ]: https://www.contributor-covenant.org/faq
133+
[translations]: https://www.contributor-covenant.org/translations
134+

0 commit comments

Comments
 (0)