All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org,
	Alexander von Gluck IV <kallisti5@unixzen.com>,
	John Snow <jsnow@redhat.com>,
	qemu-trivial@nongnu.org
Subject: Re: [PATCH] tests/vm: Drop the broken Haiku VM
Date: Thu, 17 Sep 2026 09:34:48 +0100	[thread overview]
Message-ID: <aqumKKh9rjksBnjC@redhat.com> (raw)
In-Reply-To: <20260917062615.783485-1-thuth@redhat.com>

On Thu, Sep 17, 2026 at 08:26:15AM +0200, Thomas Huth wrote:
> The Haiku VM has bitrotted again: At least since Haiku r1beta6 has
> been released, the image does not work anymore. I tried to update
> the script to use the r1beta6 repositories instead, but after the
> update, the Haiku kernel only crashes during reboot.
> 
> Given the fact that hardly anybody seems to use this image and
> that it is more often broken than working, let's stop wasting our
> time here and simply remove it.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  If somebody wants to see Haiku being tested more frequently again,
>  it might be better to look into alternatives like Github actions.
> 
>  tests/vm/haiku.x86_64 | 124 ------------------------------------------
>  1 file changed, 124 deletions(-)
>  delete mode 100755 tests/vm/haiku.x86_64

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>




With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|



      reply	other threads:[~2026-09-17  8:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  6:26 [PATCH] tests/vm: Drop the broken Haiku VM Thomas Huth
2026-09-17  8:34 ` Daniel P. Berrangé [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=aqumKKh9rjksBnjC@redhat.com \
    --to=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kallisti5@unixzen.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=thuth@redhat.com \
    /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.