Skip to content

Commit 9a69d4f

Browse files
kawasakikawasaki
committed
adding ci files
1 parent bc9ff19 commit 9a69d4f

File tree

6 files changed

+952
-0
lines changed

6 files changed

+952
-0
lines changed

‎.github/workflows/kernel_build.yml‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
# SPDX-License-Identifier: GPL-2.0-or-later
2+
#
3+
# Copyright (c) 2025 Western Digital Corporation or its affiliates.
4+
5+
name: blktests-ci
6+
7+
on:
8+
pull_request:
9+
10+
jobs:
11+
build-kernel:
12+
runs-on: ubuntu-latest
13+
steps:
14+
- name: Configure git
15+
run: |
16+
git config --global --add safe.directory '*'
17+
- name: Checkout git
18+
run: |
19+
sudo apt-get install -y libelf-dev
20+
mkdir -p linux
21+
cd linux
22+
git init
23+
git remote add origin https://github.com/${{ github.repository }}
24+
git fetch origin --depth=5 ${{ github.event.pull_request.head.sha }}
25+
git reset --hard ${{ github.event.pull_request.head.sha }}
26+
git log -1
27+
- name: Build kernel
28+
run: |
29+
cd linux
30+
make defconfig
31+
make -j 8
32+

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

Lines changed: 97 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,97 @@
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 (dennis.maisenbacher@wdc.com)
6+
7+
name: Run blktests
8+
9+
on:
10+
pull_request:
11+
12+
env:
13+
KERNEL_REF: "${{ github.event.pull_request.head.sha }}"
14+
KERNEL_TREE: "https://github.com/${{ github.repository }}"
15+
16+
#This workflow requires an actions-runner-controllers (ARC) to be active.
17+
#The k8s cluster of this ARC needs KubeVirt to be installed.
18+
jobs:
19+
build-and-test-kernel:
20+
#This step runs in a container in the k8s cluster
21+
runs-on: arc-vm-linux-blktests
22+
steps:
23+
- name: Checkout blktests-ci
24+
uses: actions/checkout@v4
25+
with:
26+
repository: linux-blktests/blktests-ci
27+
path: blktests-ci
28+
29+
- name: Build kernel and package it into a containerimage
30+
run: |
31+
cd blktests-ci/playbooks/roles/kernel-builder-k8s-job/templates
32+
docker build \
33+
--build-arg KERNEL_TREE=${KERNEL_TREE} \
34+
--build-arg KERNEL_REF=${KERNEL_REF} \
35+
-t linux-kernel-containerdisk \
36+
-f Dockerfile.linux-kernel-containerdisk . 2>&1 | tee build.log
37+
#Setting KERNEL_VERSION var which is latern needed for notifying the VM what kernel to pick up
38+
cat build.log | grep KERNEL_VERSION | awk '{print $3}' | grep KERNEL_VERSION >> $GITHUB_ENV
39+
40+
- name: Push the new Fedora containerimage with the freshly build kernel
41+
run: |
42+
docker tag linux-kernel-containerdisk registry-service.docker-registry.svc.cluster.local/linux-kernel-containerdisk:${KERNEL_VERSION}
43+
docker push registry-service.docker-registry.svc.cluster.local/linux-kernel-containerdisk:${KERNEL_VERSION}
44+
45+
- name: Run in VM
46+
uses: ./blktests-ci/.github/actions/kubevirt-action
47+
with:
48+
kernel_version: ${{ env.KERNEL_VERSION }}
49+
run_cmds: |
50+
#Print VM debug info
51+
uname -a
52+
cat /etc/os-release
53+
lsblk
54+
55+
#Install build dependencies for blktests
56+
sudo dnf install -y gcc \
57+
clang \
58+
make \
59+
util-linux \
60+
llvm \
61+
gawk \
62+
fio \
63+
udev \
64+
kmod \
65+
coreutils \
66+
gcc \
67+
gzip \
68+
e2fsprogs \
69+
xfsprogs \
70+
f2fs-tools \
71+
btrfs-progs \
72+
device-mapper-multipath \
73+
nbd \
74+
device-mapper \
75+
unzip \
76+
jq \
77+
nvme-cli \
78+
git \
79+
wget
80+
81+
git clone https://github.com/linux-blktests/blktests.git
82+
83+
cd blktests
84+
make
85+
86+
cat > config << EOF
87+
TEST_DEVS=(${ZBD0})
88+
DEVICE_ONLY=1
89+
EOF
90+
91+
#ATTENTION! This section formats all available NVMe devices. Be careful when changing the `runs-on` tag!
92+
#This step runs in a VM with the previously compiled kernel in the k8s cluster
93+
94+
# Run ZBD blktests
95+
96+
export RUN_ZONED_TESTS=1
97+
sudo ./check zbd

‎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+
opensource@wdc.com.
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)