qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	qemu-devel@nongnu.org, "Willian Rampazzo" <willianr@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 0/6] tests/docker: Update Fedora containers
Date: Wed, 24 Nov 2021 12:19:04 +0000	[thread overview]
Message-ID: <YZ4tuO2tJKdT7FP3@redhat.com> (raw)
In-Reply-To: <20211103144844.1285634-1-jsnow@redhat.com>

On Wed, Nov 03, 2021 at 10:48:38AM -0400, John Snow wrote:
> Fedora 33 will be EOL before 6.2 ships; Fedora 35 was just
> released. Update our various containers to test on F34 and F35.
> 
> Fix a minor code warning issue that surfaces in a new version of Clang,
> and fix a small deprecation issue for the latest version of spice.
> 
> In testing, I found that oss-fuzz was more likely to time out on GitLab;
> it's unclear if this is a performance regression or just getting unlucky
> with when I test.

For me it times out every time on Fedora 35. In fact if I run it
locally, it doesnn't even finish after 24 hours ! There's a real
bug in there somewhere.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  parent reply	other threads:[~2021-11-24 12:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 14:48 [PATCH 0/6] tests/docker: Update Fedora containers John Snow
2021-11-03 14:48 ` [PATCH 1/6] spice: Update QXLInterface for spice >= 0.15.0 John Snow
2021-11-04  6:47   ` Gerd Hoffmann
2021-11-03 14:48 ` [PATCH 2/6] ui/clipboard: Don't use g_autoptr just to free a variable John Snow
2021-11-03 14:57   ` Marc-André Lureau
2021-11-03 14:58   ` Daniel P. Berrangé
2021-11-03 15:30     ` John Snow
2021-11-03 14:48 ` [PATCH 3/6] docker: update fedora container to Fedora 34 John Snow
2021-11-03 14:52   ` Philippe Mathieu-Daudé
2021-11-03 16:55   ` Willian Rampazzo
2021-11-03 14:48 ` [PATCH 4/6] docker: update Fedora-based cross-compiler containers " John Snow
2021-11-03 14:52   ` Philippe Mathieu-Daudé
2021-11-03 16:56   ` Willian Rampazzo
2021-11-03 14:48 ` [PATCH 5/6] docker: update 'python' dockerfile to use Fedora registry John Snow
2021-11-03 14:55   ` Philippe Mathieu-Daudé
2021-11-03 16:57   ` Willian Rampazzo
2021-11-03 14:48 ` [PATCH 6/6] docker: Add Fedora 35 container John Snow
2021-11-03 16:59   ` Daniel P. Berrangé
2021-11-03 17:51     ` John Snow
2021-11-03 18:53       ` Philippe Mathieu-Daudé
2021-11-24 12:19 ` Daniel P. Berrangé [this message]
2021-11-24 12:34   ` [PATCH 0/6] tests/docker: Update Fedora containers Philippe Mathieu-Daudé
2021-11-24 12:51     ` Alex Bennée
2021-11-24 12:59       ` Philippe Mathieu-Daudé

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=YZ4tuO2tJKdT7FP3@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=jsnow@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=willianr@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 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).