All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Tom Rini" <trini@konsulko.com>
Cc: u-boot@lists.denx.de, "Simon Glass" <sjg@chromium.org>,
	"Alper Nebi Yasak" <alpernebiyasak@gmail.com>,
	"Heinrich Schuchardt" <xypron.glpk@gmx.de>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Aaron Williams" <awilliams@marvell.com>
Subject: Re: [PATCH 16/20] CI: Dockerfile: Bump various software version
Date: Wed, 12 Jun 2024 17:19:38 +0100	[thread overview]
Message-ID: <b8076240-8b63-4921-9cbd-ec74ed14c127@app.fastmail.com> (raw)
In-Reply-To: <20240612160109.GV68077@bill-the-cat>



在2024年6月12日六月 下午5:02,Tom Rini写道:
[...]
>> --- a/tools/docker/Dockerfile
>> +++ b/tools/docker/Dockerfile
>> @@ -2,7 +2,7 @@
>>  # This Dockerfile is used to build an image containing basic stuff to be used
>>  # to build U-Boot and run our test suites.
>>  
>> -FROM ubuntu:jammy-20240227
>> +FROM ubuntu:noble
>>  MAINTAINER Tom Rini <trini@konsulko.com>
>>  LABEL Description=" This image is for building U-Boot inside a container"
>>  
>
> For reproducibility I keep us on date-tags and not just the raw
> release tag/latest. Also, I'm not yet ready to move us past Jammy
> without a big reason. Once 24.04.1 comes out, perhaps. So it's good to
> know at least this wasn't too much work to move forward. Also, we should
> keep the bumping of various tools to their own commit, each.

Ok, I'll add tag back.

My purpose to move CI to noble is to test against all new pieces of software.
I was hit by those issues when I was trying to run tests locally with my ArchLinux
PC, so I decided to fix them and bump CI to ensure we don't introduce more in future.

I think as we can pass all CI runs it's good to move forward :-)

Thanks
>
> -- 
> Tom
>
> 附件:
> * signature.asc

-- 
- Jiaxun

  reply	other threads:[~2024-06-12 16:20 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 21:03 [PATCH 00/20] New CI image and fixes Jiaxun Yang
2024-06-11 21:04 ` [PATCH 01/20] py: Replace deprecated unittest APIs Jiaxun Yang
2024-06-11 21:04 ` [PATCH 02/20] binman: Replace pkg_resources with importlib.resources Jiaxun Yang
2024-06-11 21:04 ` [PATCH 03/20] py: Replace distutils.core with setuptools Jiaxun Yang
2024-06-11 21:04 ` [PATCH 04/20] py: Replace usage of configparser.read_fp Jiaxun Yang
2024-06-11 21:04 ` [PATCH 05/20] doc/sphinx: Remove usage of six Jiaxun Yang
2024-06-11 21:04 ` [PATCH 06/20] py: Remove unused entries in requirements.txt Jiaxun Yang
2024-06-11 21:04 ` [PATCH 07/20] py: Bump requirements versions Jiaxun Yang
2024-06-11 21:04 ` [PATCH 08/20] py: Bump pylint version and clear warnings Jiaxun Yang
2024-06-11 21:04 ` [PATCH 09/20] binman: Workaround lz4 cli padding in test cases Jiaxun Yang
2024-06-11 21:04 ` [PATCH 10/20] tests/test_event_dump: Relax match rule for output Jiaxun Yang
2024-06-11 21:04 ` [PATCH 11/20] lib/charset & efi: Fix possible unaligned accesses Jiaxun Yang
2024-06-11 21:04 ` [PATCH 12/20] cyclic: Rise default CYCLIC_MAX_CPU_TIME_US to 5000 Jiaxun Yang
2024-06-12 16:00   ` Tom Rini
2024-06-12 16:13     ` Jiaxun Yang
2024-06-12 16:50       ` Tom Rini
2024-06-14 14:13         ` Stefan Roese
2024-06-17 23:29           ` Tom Rini
2024-06-18 14:00             ` Jiaxun Yang
2024-06-18 14:24               ` Stefan Roese
2024-06-18 14:31               ` Tom Rini
2024-06-18 21:03                 ` Tim Harvey
2024-06-19  8:21                   ` Rasmus Villemoes
2024-06-19 15:20                     ` Tom Rini
2024-06-18 14:01             ` Stefan Roese
2024-06-11 21:04 ` [PATCH 13/20] CI: Ensure pip install is always performed in venv Jiaxun Yang
2024-06-12 16:00   ` Tom Rini
2024-06-11 21:04 ` [PATCH 14/20] CI: GitLab: Split build_world tasks Jiaxun Yang
2024-06-12 16:01   ` Tom Rini
2024-06-12 16:14     ` Jiaxun Yang
2024-06-12 17:07       ` Tom Rini
2024-06-12 20:24         ` Simon Glass
2024-06-13 15:32           ` Tom Rini
2024-06-11 21:04 ` [PATCH 15/20] CI: Dockerfile: Set global git name & email config Jiaxun Yang
2024-06-11 21:04 ` [PATCH 16/20] CI: Dockerfile: Bump various software version Jiaxun Yang
2024-06-12 16:02   ` Tom Rini
2024-06-12 16:19     ` Jiaxun Yang [this message]
2024-06-11 21:04 ` [PATCH 17/20] CI: Dockerfile: Add LoongArch64 support Jiaxun Yang
2024-06-11 21:04 ` [PATCH 18/20] doc: ci: Document how to run pipeline on gitlab.com Jiaxun Yang
2024-06-11 21:04 ` [PATCH NFC 19/20] Use Jiaxun's CI Image Jiaxun Yang
2024-06-11 21:04 ` [PATCH NFC 20/20] CI: Dockerfile: Replace some URL with mirror sites Jiaxun Yang
2024-06-12 16:00 ` [PATCH 00/20] New CI image and fixes Tom Rini

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=b8076240-8b63-4921-9cbd-ec74ed14c127@app.fastmail.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=alpernebiyasak@gmail.com \
    --cc=awilliams@marvell.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.