https://bugzilla.suse.com/show_bug.cgi?id=1202260 Li Zhang <li.zhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|li.zhang@suse.com |kvm-bugs@suse.de -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1202260 https://bugzilla.suse.com/show_bug.cgi?id=1202260#c1 Dario Faggioli <dfaggioli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(schwab@suse.de) --- Comment #1 from Dario Faggioli <dfaggioli@suse.com> --- Ok, looking into this. What's the best way to reproduce this locally? Ideally outside of osc, but even with osc would at least be a start... For now, I've branched the package: https://build.opensuse.org/package/show/home:dfaggioli:bug1202260:RISCV:ALP/... And I'm doing:

osc build --vm-type=qemu standard riscv64

But it's telling me this:

unresolvable: nothing provides gdb nothing provides vim nothing provides strace nothing provides less nothing provides rzsz

Even if I try: osc build --vm-type=qemu standard aarch64 it's still unresolvable, even if that seems to work on OBS. What am I doing wrong? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1202260 https://bugzilla.suse.com/show_bug.cgi?id=1202260#c3 Dario Faggioli <dfaggioli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |KVM --- Comment #3 from Dario Faggioli <dfaggioli@suse.com> --- (In reply to Dario Faggioli from comment #2)

(In reply to Andreas Schwab from comment #0)

...

FAIL: test-free ===============

***MEMORY-ERROR***: qemu-riscv64[11423]: GSlice: failed to allocate 496 bytes (alignment: 512): Cannot allocate memory

FAIL test-free (exit status: 139)

Mmmm... I don't think I'm getting what it is, in qemu, that calls the GSlice memory allocation function (that's why I'm trying to reproduce this locally, and see if I can get something like a call-trace, etc).

Maybe something inside glib itself.

Despite this, setting the component to 'KVM' for now, as we're currently treating it as a QEMU bug. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1202260 https://bugzilla.suse.com/show_bug.cgi?id=1202260#c5 --- Comment #5 from Dario Faggioli <dfaggioli@suse.com> --- (In reply to Andreas Schwab from comment #4)

https://build.opensuse.org/package/show/Base:System/findutils

Right. What about this? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1202260 https://bugzilla.suse.com/show_bug.cgi?id=1202260#c7 Dario Faggioli <dfaggioli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(schwab@suse.de) --- Comment #7 from Dario Faggioli <dfaggioli@suse.com> --- Hey, sorry if this bug is taking a bit long, but it can really only be addressed in background :-( For now, a question, can you check if 7.1, that we have now in Tumbleweed, is failing in the same way? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1202260 https://bugzilla.suse.com/show_bug.cgi?id=1202260#c10 Dario Faggioli <dfaggioli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Dario Faggioli <dfaggioli@suse.com> --- Ok, I'm assuming that this now can be closed, and I'll do that. Ping me if that wasn't the case! -- You are receiving this mail because: You are on the CC list for the bug.