Am 06.05.2015 um 12:22 schrieb Dirk Müller:
Hi Andreas,
Why wasn't it tested?
Good question. Why does this suddenly depend on Factory?
IIRC this was changed March 23rd based on your announcement that there
are issues with 2.3.0-rc0.
Then that was a clear miscommunication, as I
Hi Andreas,
Why wasn't it tested?
Good question. Why does this suddenly depend on Factory?
IIRC this was changed March 23rd based on your announcement that there
are issues with 2.3.0-rc0.
openSUSE:Factory:ARM uses qemu-linux-user from Virtualization, which
means that if there were a
Alexander Graf wrote:
so I do recommend to do an automated testing outside the buildservice
instead, which gives you notifications and enough time to fix so that
the stuff that enters Factory is working.
Would it be possible to cross compile a small arm binary on x86 and run
it through
Dirk Müller wrote:
Why wasn't it tested?
Good question. Why does this suddenly depend on Factory?
IIRC this was changed March 23rd based on your announcement that there
are issues with 2.3.0-rc0.
openSUSE:Factory:ARM uses qemu-linux-user from Virtualization, which
means that if there were a
On 06.05.15 14:30, Ludwig Nussel wrote:
Dirk Müller wrote:
Why wasn't it tested?
Good question. Why does this suddenly depend on Factory?
IIRC this was changed March 23rd based on your announcement that there
are issues with 2.3.0-rc0.
openSUSE:Factory:ARM uses qemu-linux-user from
Am 06.05.2015 um 14:59 schrieb Andreas Schwab:
Dirk Müller d...@dmllr.de writes:
Its unfortunately not immediately noticeable that qemu-linux-user is
broken, since packages never end up in the failed state (this was a
thinko from our discussion yesterday), since the build service thinks
its
HI Andreas,
its a bad worker and restarts the job on a different host, only to
fail there the same way. It is only noticed then by an admin seeing
You don't need to be admin to notice the problem.
well, either that or actively waiting for a job to start, reloading
the webui often enough so
Dirk Müller d...@dmllr.de writes:
well, either that or actively waiting for a job to start, reloading
the webui often enough so that you can catch the build log as it
Don't use the webui.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE
Dirk Müller d...@dmllr.de writes:
Its unfortunately not immediately noticeable that qemu-linux-user is
broken, since packages never end up in the failed state (this was a
thinko from our discussion yesterday), since the build service thinks
its a bad worker and restarts the job on a different
Andreas Färber afaer...@suse.de writes:
Virtualization I am able to run qemu-x86_64 /bin/ls just fine. So it
This is about qemu-arm.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
And now for something completely
On 06.05.15 23:02, Dirk Müller wrote:
Hi,
Dirk did not bother to CC me originally, and none of you have so far
pointed to any particular breakage.
There is no original mail other than this thread, really, so you're
not left out. I didn't bother to debug it further since it was broken
Am 06.05.2015 um 15:05 schrieb Andreas Schwab:
Andreas Färber afaer...@suse.de writes:
Virtualization I am able to run qemu-x86_64 /bin/ls just fine.
This is about qemu-arm.
You claimed yesterday that it has not been tested at all; I am thus
telling you that it does pass a smoke test on my
Hi Alex,
The easy fix is to s/g_new/g_new0/ to expose the same allocation
semantics as before. I've changed the code accordingly and submitted a
fixed qemu package to the Virtualization project.
Ah great, thanks for the quick fix. I've switched openSUSE:Factory:ARM
to that new version now!
Am 05.05.2015 um 10:59 schrieb Andreas Schwab:
Dirk Müller d...@dmllr.de writes:
it seems recently qemu-linux-user 2.3.0 has been accepted to factory,
which however immediately crashes on startup,
Why wasn't it tested?
Good question. Why does this suddenly depend on Factory?
I
Dirk Müller d...@dmllr.de writes:
it seems recently qemu-linux-user 2.3.0 has been accepted to factory,
which however immediately crashes on startup,
Why wasn't it tested?
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3
15 matches
Mail list logo
