qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL for 9.0 0/8] final maintainer updates (testing, gdbstub)
Date: Tue, 12 Mar 2024 15:01:08 +0000	[thread overview]
Message-ID: <87jzm7o5or.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAFEAcA_Vok6GcphdFv_NZv7iCeLpebS9JWZW5yHeRx1w9EY00g@mail.gmail.com> (Peter Maydell's message of "Tue, 12 Mar 2024 13:42:32 +0000")

Peter Maydell <peter.maydell@linaro.org> writes:

> On Tue, 12 Mar 2024 at 11:26, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> The following changes since commit 7489f7f3f81dcb776df8c1b9a9db281fc21bf05f:
>>
>>   Merge tag 'hw-misc-20240309' of https://github.com/philmd/qemu into staging (2024-03-09 20:12:21 +0000)
>>
>> are available in the Git repository at:
>>
>>   https://gitlab.com/stsquad/qemu.git tags/pull-maintainer-final-120324-1
>>
>> for you to fetch changes up to 0532045e8112c13a8a949e696576672e64c6fa14:
>>
>>   gdbstub: Fix double close() of the follow-fork-mode socket (2024-03-12 10:48:35 +0000)
>>
>> ----------------------------------------------------------------
>> final updates for 9.0 (testing, gdbstub):
>>
>>   - avoid transferring pointless git data
>>   - fix the over rebuilding of test VMs
>>   - support Xfer:siginfo:read in gdbstub
>>   - fix double close() in gdbstub
>>
>
> This makes the s390 CI jobs fail:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/6374182015
> https://gitlab.com/qemu-project/qemu/-/jobs/6374182020
>
> fatal: --filter can only be used when extensions.partialClone is set

That's annoying - I thought I had the s390 jobs in my matrix but it
seems they don't appear anymore. That said I see:

  root@qemu01 ~# cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"

And as 24.04 is just round the corner maybe its time I update the system
to a more recent ubuntu (with I assume a more recent git)?

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2024-03-12 15:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 11:25 [PULL for 9.0 0/8] final maintainer updates (testing, gdbstub) Alex Bennée
2024-03-12 11:25 ` [PULL 1/8] gitlab: aggressively avoid extra GIT data Alex Bennée
2024-03-12 11:25 ` [PULL 2/8] tests/vm: ensure we build everything by default Alex Bennée
2024-03-12 11:25 ` [PULL 3/8] gdbstub: Rename back gdb_handlesig Alex Bennée
2024-03-12 11:25 ` [PULL 4/8] linux-user: Move tswap_siginfo out of target code Alex Bennée
2024-03-12 11:25 ` [PULL 5/8] gdbstub: Save target's siginfo Alex Bennée
2024-03-12 11:25 ` [PULL 6/8] gdbstub: Add Xfer:siginfo:read stub Alex Bennée
2024-03-12 11:25 ` [PULL 7/8] tests/tcg: Add multiarch test for " Alex Bennée
2024-03-12 11:25 ` [PULL 8/8] gdbstub: Fix double close() of the follow-fork-mode socket Alex Bennée
2024-03-12 13:42 ` [PULL for 9.0 0/8] final maintainer updates (testing, gdbstub) Peter Maydell
2024-03-12 15:01   ` Alex Bennée [this message]
2024-03-12 15:19     ` Peter Maydell

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=87jzm7o5or.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).