qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 00/30] Rust, wasm changes for 2025-05-06
Date: Thu, 8 May 2025 18:08:09 +0200	[thread overview]
Message-ID: <70e9c1a7-b586-41f3-a500-347483f6c1d6@redhat.com> (raw)
In-Reply-To: <CAJSP0QX0wL1qJzfMoH6Di+QY3K9ML3HTLeY2gXZHNNJm_jDTTQ@mail.gmail.com>

On 5/8/25 16:26, Stefan Hajnoczi wrote:
> On Tue, May 6, 2025 at 11:30 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> The following changes since commit a9e0c9c0f14e19d23443ac24c8080b4708d2eab8:
>>
>>    Merge tag 'pull-9p-20250505' of https://github.com/cschoenebeck/qemu into staging (2025-05-05 11:26:59 -0400)
>>
>> are available in the Git repository at:
>>
>>    https://gitlab.com/bonzini/qemu.git tags/for-upstream
>>
>> for you to fetch changes up to e6b9b79c3076777b791f72ebdbc9d37ad8005fe9:
>>
>>    gitlab: Enable CI for wasm build (2025-05-06 16:02:04 +0200)
>>
>> ----------------------------------------------------------------
>> * ci: enable RISC-V cross jobs
>> * rust: bump minimum supported version to 1.77
>> * rust: enable uninlined_format_args lint
>> * initial Emscripten support
>> * small fixes
> 
> I'm not sure why, but the following CI failure seems to be caused by
> this pull request:
> https://gitlab.com/qemu-project/qemu/-/jobs/9974291215#L4684
> 
> Please take a look, thanks!

It is a transient failure; it reproduces 30% of the time with

    meson test --repeat 100 func-hppa-hppa_seabios

even without the pull request (commit 
a9e0c9c0f14e19d23443ac24c8080b4708d2eab8).

Before finding this I had already sent the first half (which should be 
safe since it's all Rust code that isn't compiled on that runner---and 
for hppa targets in general), but if you still have the merge commit 
perhaps you can push it?

Paolo



  reply	other threads:[~2025-05-08 16:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 15:28 [PULL 00/30] Rust, wasm changes for 2025-05-06 Paolo Bonzini
2025-05-06 15:28 ` [PULL 01/30] lcitool: use newer Rust for Debian and Ubuntu Paolo Bonzini
2025-09-03 13:54   ` Marc-André Lureau
2025-09-03 13:59     ` Paolo Bonzini
2025-09-04 19:38       ` Marc-André Lureau
2025-09-05  5:16         ` Paolo Bonzini
2025-09-05  5:17           ` Paolo Bonzini
2025-09-05 12:06         ` Alex Bennée
2025-05-06 15:28 ` [PULL 02/30] meson, cargo: require Rust 1.77.0 Paolo Bonzini
2025-05-06 15:28 ` [PULL 03/30] rust: use std::ffi instead of std::os::raw Paolo Bonzini
2025-05-06 15:28 ` [PULL 04/30] rust: let bilge use "let ... else" Paolo Bonzini
2025-05-06 15:29 ` [PULL 05/30] rust: qemu_api_macros: make pattern matching more readable and efficient Paolo Bonzini
2025-05-06 15:29 ` [PULL 06/30] rust: use MaybeUninit::zeroed() in const context Paolo Bonzini
2025-05-06 15:29 ` [PULL 07/30] rust: qom: fix TODO about zeroability of classes Paolo Bonzini
2025-05-06 15:29 ` [PULL 08/30] rust: enable clippy::ptr_cast_constness Paolo Bonzini
2025-05-06 15:29 ` [PULL 09/30] rust: remove offset_of replacement Paolo Bonzini
2025-05-06 15:29 ` [PULL 10/30] rust: replace c_str! with c"" literals Paolo Bonzini
2025-05-06 15:29 ` [PULL 11/30] docs: rust: update for newer minimum supported version Paolo Bonzini
2025-05-06 15:29 ` [PULL 12/30] target/i386/emulate: fix target_ulong format strings Paolo Bonzini
2025-05-06 15:29 ` [PULL 13/30] rust: clippy: enable uninlined_format_args lint Paolo Bonzini
2025-05-06 15:29 ` [PULL 14/30] ci: run RISC-V cross jobs by default Paolo Bonzini
2025-05-06 15:29 ` [PULL 15/30] docs: build-system: fix typo Paolo Bonzini
2025-05-06 15:29 ` [PULL 16/30] target/arm/helper.c: Fix type conflict of GLib function pointers Paolo Bonzini
2025-05-06 15:29 ` [PULL 17/30] target/i386/cpu.c: " Paolo Bonzini
2025-05-06 15:29 ` [PULL 18/30] target/ppc: " Paolo Bonzini
2025-05-06 15:29 ` [PULL 19/30] target/s390x: " Paolo Bonzini
2025-05-06 15:29 ` [PULL 20/30] include/glib-compat.h: Poison g_list_sort and g_slist_sort Paolo Bonzini
2025-05-06 15:29 ` [PULL 21/30] util/cacheflush.c: Update cache flushing mechanism for Emscripten Paolo Bonzini
2025-05-06 15:29 ` [PULL 22/30] block: Add including of ioctl header for Emscripten build Paolo Bonzini
2025-05-06 15:29 ` [PULL 23/30] block: Fix type conflict of the copy_file_range stub Paolo Bonzini
2025-05-06 15:29 ` [PULL 24/30] include/qemu/osdep.h: Add Emscripten-specific OS dependencies Paolo Bonzini
2025-05-06 15:29 ` [PULL 25/30] Disable options unsupported on Emscripten Paolo Bonzini
2025-05-06 15:29 ` [PULL 26/30] util: exclude mmap-alloc.c from compilation target " Paolo Bonzini
2025-05-06 15:29 ` [PULL 27/30] util: Add coroutine backend for emscripten Paolo Bonzini
2025-05-06 15:29 ` [PULL 28/30] meson: Add wasm build in build scripts Paolo Bonzini
2025-05-06 15:29 ` [PULL 29/30] tests: Add Dockerfile containing dependencies for Emscripten build Paolo Bonzini
2025-05-06 15:29 ` [PULL 30/30] gitlab: Enable CI for wasm build Paolo Bonzini
2025-05-08 14:26 ` [PULL 00/30] Rust, wasm changes for 2025-05-06 Stefan Hajnoczi
2025-05-08 16:08   ` Paolo Bonzini [this message]
2025-05-08 16:53     ` Stefan Hajnoczi
2025-05-08 17:05     ` Thomas Huth
2025-05-08 17:15       ` Paolo Bonzini
2025-05-09 14:11 ` Stefan Hajnoczi

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=70e9c1a7-b586-41f3-a500-347483f6c1d6@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).