public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <denys.f@collabora.com>
To: kernelci@lists.linux.dev
Subject: KernelCI Weekly Newsletter (Week 49)
Date: Thu, 05 Dec 2024 12:10:44 +0200	[thread overview]
Message-ID: <30f74795dad7fa3d8e6ca302ad77d86f72a68bf5.camel@collabora.com> (raw)

**KernelCI Weekly Newsletter (Week 49)**  

**Summary:**  
This week, we are investigating an issue with KCIDB submissions. We
identified that the volume of tests being generated exceeds the
capacity that the KCIDB-Bridge can handle. Addressing this bottleneck
is a top priority, and we are actively working on a solution. In
parallel, we are implementing additional features to enhance the
functionality of the KernelCI Maestro.  

As always, maintaining the reliability and stability of the KernelCI
service remains our highest priority, and we are treating this issue
with the utmost urgency.  

**Known issues**
KCIDB submissions are currently experiencing a bottleneck due to the
volume of tests being generated. We are actively working on a solution
to address this issue.

### Key Updates:  

- **Legacy Sunset:**  
  Both instances of Jenkins have been fully decommissioned. These
instances were removed from staging and production scripts.
Additionally, the MongoDB database has been archived and shut down.  

- **Production Updates:**  
  Several critical production updates were deployed out of band this
week to address and resolve important issues swiftly.  

- **Trees Updates:**  
  The 4.9 stable tree has been removed from the list of supported trees
as it reaches its end-of-life (EOL).  

- **Website Updates:**  
  - The ELISA project is now listed on the KernelCI website as an
Associate Member.  
  - Minor updates were made to improve the website and its deployment
scripts.  

- **KCI Command:**  
  A new command, `findfast`, has been added to the `kci` command-line
tool. This command leverages a new API endpoint to enable non-paginated
searches, enhancing efficiency.  

- **API Enhancements:**  
  A new safeguard has been added to the `/nodes/fast` API endpoint.
This ensures that long-running queries are limited to prevent the API
from being blocked by resource-intensive operations.  

- **Tast Test Updates:**  
  The `tast-ui` tests have been re-enabled to allow observation of
their results.  

- **KCIDB Bridge Improvements:**  
  The KCIDB-Bridge now ignores incomplete builds and checkouts, as
these are designed to be retried automatically. This reduces
unnecessary processing and improves throughput.  

- **KCIDB updates:**
  Researching ways to unlock more query and ORM performance.
  Refactoring ORM caching to better handle issue-related queries, so we
can implement issue notifications.
  Fixing empty codec reports, But have we broken them more, instead?
Where are they?


### Planned Discussions for the KernelCI Weekly Meeting:  

- **MongoDB Archive Management:**  
  - Where should the archived MongoDB data (approximately 100GB of
compressed data) be stored?  
  - How can access to this archive be provided to those who need it?  

- **KCIDB**
  - Discussion: how to hide already-seen issues for result reviewers
(Usama and others)


                 reply	other threads:[~2024-12-05 10:10 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=30f74795dad7fa3d8e6ca302ad77d86f72a68bf5.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