[opensuse-buildservice] Need to know morla1 cpu type.
Hello, I am trying to fix go issue related to SIGILL (Illegal instruction), unfortunately I happens only in OBS on some builders. Go developers want to know CPU type.
From buildlog I see:
[ 0s] morla1 started "build golang-org-x-crypto.spec" at Sat Dec 26 11:31:15 UTC 2015. Could I have /proc/cpuinfo of morla1? It may be really useful. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Saturday 26 December 2015 21.04:24 Matwey V. Kornilov wrote:
Hello,
I am trying to fix go issue related to SIGILL (Illegal instruction), unfortunately I happens only in OBS on some builders. Go developers want to know CPU type.
From buildlog I see:
[ 0s] morla1 started "build golang-org-x-crypto.spec" at Sat Dec 26 11:31:15 UTC 2015.
Could I have /proc/cpuinfo of morla1? It may be really useful.
Most of the build on obs are done in Virtual Machine for example you can see on which hypervisor it happen at the begining of the build log [ 0s] Doing xen build in /var/cache/obs/worker/root_1/root or [ 0s] Using BUILD_ROOT=/var/cache/obs/worker/root_16/.mount [ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386 [ 0s] Doing kvm build in /var/cache/obs/worker/root_16/root [ 0s] [ 0s] [ 1s] build20 started "build golang-org-x-crypto.spec" at Tue Dec 22 15:25:35 UTC 2015. etc ... -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
27.12.2015 00:46, Bruno Friedmann пишет:
On Saturday 26 December 2015 21.04:24 Matwey V. Kornilov wrote:
Hello,
I am trying to fix go issue related to SIGILL (Illegal instruction), unfortunately I happens only in OBS on some builders. Go developers want to know CPU type.
From buildlog I see:
[ 0s] morla1 started "build golang-org-x-crypto.spec" at Sat Dec 26 11:31:15 UTC 2015.
Could I have /proc/cpuinfo of morla1? It may be really useful.
Most of the build on obs are done in Virtual Machine
KVM just passes CPU to the guest, so any supported instructions are supported in guest, and unsupported are not supported.
for example you can see on which hypervisor it happen at the begining of the build log
[ 0s] Doing xen build in /var/cache/obs/worker/root_1/root or [ 0s] Using BUILD_ROOT=/var/cache/obs/worker/root_16/.mount [ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386 [ 0s] Doing kvm build in /var/cache/obs/worker/root_16/root [ 0s] [ 0s] [ 1s] build20 started "build golang-org-x-crypto.spec" at Tue Dec 22 15:25:35 UTC 2015.
etc ...
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
27.12.2015 00:46, Bruno Friedmann пишет:
On Saturday 26 December 2015 21.04:24 Matwey V. Kornilov wrote:
Hello,
I am trying to fix go issue related to SIGILL (Illegal instruction), unfortunately I happens only in OBS on some builders. Go developers want to know CPU type.
From buildlog I see:
[ 0s] morla1 started "build golang-org-x-crypto.spec" at Sat Dec 26 11:31:15 UTC 2015.
Could I have /proc/cpuinfo of morla1? It may be really useful.
Most of the build on obs are done in Virtual Machine
KVM just passes CPU to the guest, so any supported instructions are supported in guest, and unsupported are not supported.
Thus putting a "cat /proc/cpuinfo" in the spec file should be enough to see the current cpu flags. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
2015-12-27 13:13 GMT+03:00 Andreas Schwab <schwab@linux-m68k.org>:
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
27.12.2015 00:46, Bruno Friedmann пишет:
On Saturday 26 December 2015 21.04:24 Matwey V. Kornilov wrote:
Hello,
I am trying to fix go issue related to SIGILL (Illegal instruction), unfortunately I happens only in OBS on some builders. Go developers want to know CPU type.
From buildlog I see:
[ 0s] morla1 started "build golang-org-x-crypto.spec" at Sat Dec 26 11:31:15 UTC 2015.
Could I have /proc/cpuinfo of morla1? It may be really useful.
Most of the build on obs are done in Virtual Machine
KVM just passes CPU to the guest, so any supported instructions are supported in guest, and unsupported are not supported.
Thus putting a "cat /proc/cpuinfo" in the spec file should be enough to see the current cpu flags.
Thanks, but I cannot push build to the specific host using: <constraints> <hostlabel>morla1</hostlabel> </constraints> The package is in the state of 'scheduled'. Do I have to wait or I am wrong with constraints?
Andreas.
-- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
Thanks, but I cannot push build to the specific host using:
<constraints> <hostlabel>morla1</hostlabel> </constraints>
A hostlabel isn't a host name. It's an arbitrary string attached to the worker, usually for marking a group of workers. $ osc buildconfig openSUSE:Factory standard | grep hostlabel Constraint: hostlabel PPC64LE_HOST Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
2015-12-27 13:54 GMT+03:00 Andreas Schwab <schwab@linux-m68k.org>:
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
Thanks, but I cannot push build to the specific host using:
<constraints> <hostlabel>morla1</hostlabel> </constraints>
A hostlabel isn't a host name. It's an arbitrary string attached to the worker, usually for marking a group of workers.
$ osc buildconfig openSUSE:Factory standard | grep hostlabel Constraint: hostlabel PPC64LE_HOST
And where can I read whole the list? And how should I force building on the specific host?
Andreas.
-- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
And how should I force building on the specific host?
You can't. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
2015-12-27 14:12 GMT+03:00 Andreas Schwab <schwab@linux-m68k.org>:
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
And how should I force building on the specific host?
You can't.
Then cat /proc/cpuinfo won't help me
Andreas.
-- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
2015-12-27 14:12 GMT+03:00 Andreas Schwab <schwab@linux-m68k.org>:
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
And how should I force building on the specific host?
You can't.
Then cat /proc/cpuinfo won't help me
Sure it will. The next time it fails you won't have to ask here. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
2015-12-27 14:20 GMT+03:00 Andreas Schwab <schwab@linux-m68k.org>:
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
2015-12-27 14:12 GMT+03:00 Andreas Schwab <schwab@linux-m68k.org>:
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
And how should I force building on the specific host?
You can't.
Then cat /proc/cpuinfo won't help me
Sure it will. The next time it fails you won't have to ask here.
It won't fail next time, the probability that it will be built on the same host is negligible. There are hundreds of builders.
Andreas.
-- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
-- With best regards, Matwey V. Kornilov http://blog.matwey.name xmpp://0x2207@jabber.ru -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 27.12.2015 um 12:26 schrieb Matwey V. Kornilov:
2015-12-27 14:20 GMT+03:00 Andreas Schwab <schwab@linux-m68k.org>:
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
2015-12-27 14:12 GMT+03:00 Andreas Schwab <schwab@linux-m68k.org>:
"Matwey V. Kornilov" <matwey.kornilov@gmail.com> writes:
And how should I force building on the specific host?
You can't.
Then cat /proc/cpuinfo won't help me
Sure it will. The next time it fails you won't have to ask here.
It won't fail next time, the probability that it will be built on the same host is negligible. There are hundreds of builders.
You might be able to increase that probability by using as _constraints 8000 MB of physicalmemory or something like that. :) You can then also check the QEMU command line in the build log for any CPU options - as Andreas pointed out, KVM guests don't necessarily have the same CPUIDs as the host, and the QEMU version may further affect the exact outcome. Cheers, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Andreas Färber -
Andreas Schwab -
Bruno Friedmann -
Matwey V. Kornilov