From: Denys Fedoryshchenko <denys.f@collabora.com>
To: kernelci <kernelci@lists.linux.dev>
Subject: KernelCI Weekly Newsletter (Week 48)
Date: Thu, 28 Nov 2024 11:54:51 +0200 [thread overview]
Message-ID: <d2233efc5b6a4c4e4ed73cd572c277b3fa93f7a9.camel@collabora.com> (raw)
Welcome to the first edition of the KernelCI Weekly Newsletter!
As our community continues to grow, we recognize the need to keep
everyone informed about the latest developments, regardless of their
ability to attend our weekly video meetings. This newsletter aims to
bridge that gap by providing regular updates on project progress,
upcoming discussions, and community highlights.
A Note on This First Edition
As with any new initiative, we're learning as we go. This first
newsletter might have room for improvement in terms of format, content,
or delivery. We're committed to making this newsletter as valuable as
possible for our community, and your feedback will be instrumental in
shaping future editions. Please don't hesitate to share your
suggestions, point out areas for improvement, or tell us what you'd
like to see more of. We see this as a collaborative effort to create a
truly useful resource for the KernelCI community.
1. What to Expect.
Each week, you'll receive:
- A digest of key development updates and milestones
- Preview of topics for the upcoming weekly meeting
- Community contributions and achievements
- Important announcements and project updates
- Opportunities to get involved
2. Why a Weekly Newsletter?
We believe that frequent, consistent communication is key to
maintaining a vibrant open-source community. By sharing weekly updates,
we hope to:
- Keep everyone aligned with project goals and progress
- Enable asynchronous participation in project discussions
- Highlight contributions from our community members
- Make it easier for newcomers to stay informed and engaged
- Provide a historical record of project development
KernelCI Newsletter (Week 48)
Summary:
This week's development activities focused on infrastructure
improvements and build system optimizations:
- Infrastructure Updates:
We expanded our Kubernetes builder capacity to handle increased
workloads. However, this led to temporary build congestion as we needed
to rebalance the load across our builder network.
- Production Updates:
Some production deployments were delayed due to bugs discovered during
testing. Our team worked diligently to address these issues before
proceeding with the updates.
- KernelCI Enhancements:
We added additional build configurations (allmodconfig to stable-rc
trees) in KernelCI to improve our testing coverage. While this
enhancement provides better testing capabilities, it initially
contributed to the build system congestion as we worked to optimize the
new configurations.
Known issues:
- Some checkouts were failing due '/' symbol in git describe. Fix
deployed into production at 2024-11-27
- Some builds are failing on new capacity and become "incomplete",
issue is under active investigation.
- There is some hiccups at 25-27 November due changes in k8s build
capacity
New features, changes and fixes:
- Add legacy build capacity, multiple k8s build clusters
- Add minimal support for k8s load-balancing
- Reconfiguring build k8s clusters from legacy to Maestro
- tarball filename creation is fixed for the case when git describe
contains invalid symbols
- Pydantic fixes from Jeny Sadadia
- CONFIG_CPUSETS_V1 added back to chromebook configuration, as ChromeOS
requires it (regression introduced by
1abab1ba0775036bb67c6c57945c637be644c04f)
- logspec is being built for staging/production images from it's own
repository
- send_kcidb bugfix for nodes that have missing some of job metadata
- src/send_kcidb: get lava labs from config, dynamically, remove
hardcoded values
- Enable v6.12 stable-rc branch
- Disable baseline tests for ARM Android (as devices fail to boot)
- Start documenting pipeline configuration file
- Add allmodconfig to stable-rc builds, as suggested by Todd Kjos they
greatly improve build coverage
Planned changes / Discussion at weekly meeting:
- Archiving legacy repositories
- Archiving mongodb database
- Pinning Maestro and KCIDB repositories to main github (org) page:
kcidb, kernelci-pipeline, kernelci-api, dashboard, kernelci-project,
kci-dev
- Discord bot development (newsletter reminder, github actions
notifications)
reply other threads:[~2024-11-28 9:54 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=d2233efc5b6a4c4e4ed73cd572c277b3fa93f7a9.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).