Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Knop, Ryszard" <ryszard.knop@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"I915-ci-infra@lists.freedesktop.org"
	<I915-ci-infra@lists.freedesktop.org>
Subject: LGCI Ubuntu 24.04 Upgrade Notice
Date: Mon, 26 Aug 2024 13:45:27 +0000	[thread overview]
Message-ID: <50e68389802664375db12eeeb0f5b2c79713d1ef.camel@intel.com> (raw)

Hello everyone,

The kernel graphics CI system is currently running primarily on Ubuntu
20.04, with some libraries held on 18.04 for compatibility reasons.
This means outdated toolchains, missing features required by some IGT
tests (mainly around HDR) and generally a mismatch between what we're
testing and where the Linux ecosystem currently is. To amend all this,
we are planning to upgrade the entire CI system to Ubuntu 24.04 this
quarter, on 23.09.2024.

- On 23.09 (Monday), the CI system will stop accepting jobs for about a
day. All DUTs will be wiped clean – Ubuntu Server 24.04 will be
reinstalled from scratch. (If you have any handy scripts or tools left
on those machines for debugging, now would be a good time to contact
the CI team to fetch them before they’re gone.)
- All infra servers running builds, services and developer terminals
will be upgraded to 24.04. All LGCI services will be available
intermittently until all upgrade issues are resolved.
- Our systems are not prepared for a partial migration with 20.04/24.04
builds and testing being run side by side. All testing will be switched
to 24.04 at once.
- While we expect to resolve most issues on Monday, this is the largest
OS bump we have had in a long time – be aware that the CI system may
misbehave for the entire week after the upgrade.

If you have any questions, respond to this email.

Thanks, Ryszard

                 reply	other threads:[~2024-08-28  8:01 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=50e68389802664375db12eeeb0f5b2c79713d1ef.camel@intel.com \
    --to=ryszard.knop@intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    /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