From: Denys Fedoryshchenko <denys.f@collabora.com>
To: kernelci@lists.linux.dev
Subject: KernelCI Weekly Newsletter (Week 3)
Date: Wed, 15 Jan 2025 13:35:27 +0200 [thread overview]
Message-ID: <8b00de79dda2b1aebc01e9e62ace74053be76da0.camel@collabora.com> (raw)
**Summary**
This week, we focused on the following:
- Enabling full support for the GRUB bootloader, including NFS-rootfs
support.
- Enabling kselftests on the Aaeon x86 platform.
- Fixing kselftest build issues caused by missing environment
variables.
- Enabling net/kselftest on x86 (amd64) and arm64 platforms.
**Sysadmin**
Except regular production updates, we have been working on:
- Separating storage tokens for Kubernetes build clusters to allow
testing of new storage solutions without impacting production.
**kci-dev**
As kci-dev continues to evolve, we released version 0.1.1. A special
thanks to Arisu!
We have been utilizing kci-dev for various purposes, and here are some
examples of how it can be used:
- **Running a Single Test on a Specific Platform in Real-Time**
```
kci-dev checkout --giturl
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --
branch master --tipoftree --jobfilter kbuild-gcc-12-x86-chromeos-intel
--jobfilter tast-power-x86-intel --test tast-power-x86-intel --
platformfilter acer-cb317-1h-c3z6-dedede --watch
```
This command checks out the latest kernel from the master branch,
builds it with GCC-12, runs the `tast-power` test on the `acer-cb317-
1h-c3z6-dedede` platform, and monitors the results in real-time. Such
combinations are often used to verify the consistency of test results
on specific platforms.
- **Testing a Specific Tree on Staging After Configuration Changes**
```
kci-dev checkout --giturl
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
--branch fixes --tipoftree
```
This command checks out the latest kernel from the `fixes` branch of
the `linux-kselftest` repository and builds it with the default
configuration. It invokes the same builds and tests as in production
when a new revision is pushed to the `linux-kselftest` repository.
- **Initiating Bisection (Early Stage)**
```
kci-dev bisect --giturl
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --
branch master --jobfilter kbuild-gcc-12-x86-chromeos-intel --jobfilter
tast-power-x86-intel --test tast-power-x86-intel --platformfilter acer-
cb317-1h-c3z6-dedede --good 2f27fce67173bbb05d5a0ee03dae5c021202c912 --
bad 2d5404caa8c7bb5c4e0435f94b28834ae5456623
```
Using this command, we can initiate a bisection on a specific
platform and test, while monitoring the results in real-time. The `--
good` and `--bad` parameters correspond to Git commit hashes, following
the same procedure as the `git bisect` command.
We will share more examples of how to use kci-dev in the next
newsletter.
**Planned Work**
Next week, we plan to update the production server. As a result, there
will be some downtime for `storage.kernelci.org` and
`docs.kernelci.org`. We will strive to minimize the downtime as much as
possible.
reply other threads:[~2025-01-15 11:35 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=8b00de79dda2b1aebc01e9e62ace74053be76da0.camel@collabora.com \
--to=denys.f@collabora.com \
--cc=kernelci@lists.linux.dev \
/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