qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/6] gdbstub, avocado and gitlab updates
Date: Fri, 01 Dec 2023 17:50:44 +0000	[thread overview]
Message-ID: <874jh16ccr.fsf@draig.linaro.org> (raw)
In-Reply-To: <0ac3a8ef-894f-4405-b816-c06dbb62e051@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Fri, 1 Dec 2023 17:52:33 +0100")

Philippe Mathieu-Daudé <philmd@linaro.org> writes:

> On 1/12/23 17:50, Philippe Mathieu-Daudé wrote:
>> Hi Alex,
>> On 1/12/23 16:12, Alex Bennée wrote:
>>> The following changes since commit
>>> abf635ddfe3242df907f58967f3c1e6763bbca2d:
>>>
>>>    Update version for v8.2.0-rc2 release (2023-11-28 16:31:16 -0500)
>>>
>>> are available in the Git repository at:
>>>
>>>    https://gitlab.com/stsquad/qemu.git tags/pull-more-8.2-fixes-011223-1
>>>
>>> for you to fetch changes up to a7a740cce1ec49568e7ebd8e776279e59e2fb5b6:
>>>
>>>    gitlab: add optional job to run flaky avocado tests (2023-12-01
>>> 14:12:05 +0000)
>>>
>>> ----------------------------------------------------------------
>>> Flaky avocado tests, gdbstub and gitlab tweaks
>>>
>>>    - gdbstub, properly halt when QEMU is having IO issues
>>>    - convert skipIf(GITLAB_CI) to skipUnless(QEMU_TEST_FLAKY_TESTS)
>>>    - drop mips malta cpio test as assets expire in Debian archive
>>>    - tag sbsa-ref tests as TCG only
>>>    - build the correct microblaze for avocado-system-ubuntu
>>>    - add optional flaky tests job to CI
>>>
>>> ----------------------------------------------------------------
>>> Alex Bennée (6):
>>>        gdbstub: use a better signal when we halt for IO reasons
>>>        docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS
>>>        tests/avocado: drop BootLinuxConsole.test_mips_malta_cpio test
>> This patch has been posted 5h ago and we are still discussing it...
>> I'm quite surprised you include it in your PR.
>
> Do you mind re-posting your PR without this patch? I don't
> mind to work on it during the WE and merge it let's say
> Sunday, if you want it in before this Monday.

I've sent v2 of the PR without the mips changes.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      reply	other threads:[~2023-12-01 17:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 15:12 [PULL 0/6] gdbstub, avocado and gitlab updates Alex Bennée
2023-12-01 15:12 ` [PULL 1/6] gdbstub: use a better signal when we halt for IO reasons Alex Bennée
2023-12-01 15:12 ` [PULL 2/6] docs/devel: rationalise unstable gitlab tests under FLAKY_TESTS Alex Bennée
2023-12-01 15:12 ` [PULL 3/6] tests/avocado: drop BootLinuxConsole.test_mips_malta_cpio test Alex Bennée
2023-12-01 16:49   ` Philippe Mathieu-Daudé
2023-12-01 17:46     ` Alex Bennée
2023-12-01 15:12 ` [PULL 4/6] tests/avocado: tag sbsa tests as tcg only Alex Bennée
2023-12-01 15:12 ` [PULL 5/6] gitlab: build the correct microblaze target Alex Bennée
2023-12-01 15:12 ` [PULL 6/6] gitlab: add optional job to run flaky avocado tests Alex Bennée
2023-12-01 16:50 ` [PULL 0/6] gdbstub, avocado and gitlab updates Philippe Mathieu-Daudé
2023-12-01 16:52   ` Philippe Mathieu-Daudé
2023-12-01 17:50     ` Alex Bennée [this message]

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=874jh16ccr.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=philmd@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).