[opensuse-buildservice] build loop without result and error
Hi, the "libreoffice" package in the "LibreOffice:Unstable" project and "openSUSE_12.3 x86_64" distro has been in some strange build loop for last few days. I am not sure what the problem is. I checked it several time. The status always was "building". The log was "only" few hours long => the build was automatically restarted several times. I wonder why. I do not see any build error and local build works. The i586 libreoffice package and x86_64 help packages have been built 7 days ago => it should not be caused by another commits in the openSUSE_12.3 or LibreOffice:Unstable repo. Do you have any idea, please? Do some errors trigger automatic rebuild? Is there any build time out? I think that it might help to force build on some more powerful hosts with more CPUs and more memory. Is it possible, please? Best Regards, Petr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Jul 16, 2013 at 02:03:10PM +0200, Petr Mladek wrote:
Hi,
the "libreoffice" package in the "LibreOffice:Unstable" project and "openSUSE_12.3 x86_64" distro has been in some strange build loop for last few days. I am not sure what the problem is.
I checked it several time. The status always was "building". The log was "only" few hours long => the build was automatically restarted several times. I wonder why. I do not see any build error and local build works. The i586 libreoffice package and x86_64 help packages have been built 7 days ago => it should not be caused by another commits in the openSUSE_12.3 or LibreOffice:Unstable repo.
Do you have any idea, please? Do some errors trigger automatic rebuild? Is there any build time out?
I think that it might help to force build on some more powerful hosts with more CPUs and more memory. Is it possible, please?
Such a automatic build restart would happen if the build runs out of memory. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 16. Juli 2013, 14:28:10 schrieb Marcus Meissner:
On Tue, Jul 16, 2013 at 02:03:10PM +0200, Petr Mladek wrote:
Hi,
the "libreoffice" package in the "LibreOffice:Unstable" project and "openSUSE_12.3 x86_64" distro has been in some strange build loop for last few days. I am not sure what the problem is.
I checked it several time. The status always was "building". The log was "only" few hours long => the build was automatically restarted several times. I wonder why. I do not see any build error and local build works. The i586 libreoffice package and x86_64 help packages have been built 7 days ago => it should not be caused by another commits in the openSUSE_12.3 or LibreOffice:Unstable repo.
Do you have any idea, please? Do some errors trigger automatic rebuild? Is there any build time out?
I think that it might help to force build on some more powerful hosts with more CPUs and more memory. Is it possible, please?
Such a automatic build restart would happen if the build runs out of memory.
Yes one possibility. I have marked the current running build instance (build16/7) to be disabled. So if the build ends there for any reason, I can check why it got stopped. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Adrian Schröter píše v Út 16. 07. 2013 v 14:45 +0200:
Am Dienstag, 16. Juli 2013, 14:28:10 schrieb Marcus Meissner:
On Tue, Jul 16, 2013 at 02:03:10PM +0200, Petr Mladek wrote:
Hi,
the "libreoffice" package in the "LibreOffice:Unstable" project and "openSUSE_12.3 x86_64" distro has been in some strange build loop for last few days. I am not sure what the problem is.
I checked it several time. The status always was "building". The log was "only" few hours long => the build was automatically restarted several times. I wonder why. I do not see any build error and local build works. The i586 libreoffice package and x86_64 help packages have been built 7 days ago => it should not be caused by another commits in the openSUSE_12.3 or LibreOffice:Unstable repo.
Do you have any idea, please? Do some errors trigger automatic rebuild? Is there any build time out?
I think that it might help to force build on some more powerful hosts with more CPUs and more memory. Is it possible, please?
Such a automatic build restart would happen if the build runs out of memory.
Yes one possibility. I have marked the current running build instance (build16/7) to be disabled. So if the build ends there for any reason, I can check why it got stopped.
Ah, in the mean time, Tomas Chvatal suggested to use constrains. So, I added the following into prjconf and restarted the build: %if %suse_version == 1230 %ifarch x86_64 Constraint: hardware:physicalmemory:size unit="M" 5000 %endif %endif Tomas says: The problem is that there are only very few machines with enough memory. There are more spec files in the libreoffice source dir. We do not know how to limit the constrain only to the "libreoffice" package. If we do the global limit, the build takes several days because of lack of machines. Tomas is pretty sure that problem is with memory. I am sorry that I was so fast and stopped the build. We are a bit in hurry. Tomas would like to promote the LibreOffice 4.1 test builds on the openSUSE conference and the most important 12.3 build is not ready. Best Regards, Petr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 16. Juli 2013, 14:45:53 schrieb Adrian Schröter:
Am Dienstag, 16. Juli 2013, 14:28:10 schrieb Marcus Meissner:
On Tue, Jul 16, 2013 at 02:03:10PM +0200, Petr Mladek wrote:
Hi,
the "libreoffice" package in the "LibreOffice:Unstable" project and "openSUSE_12.3 x86_64" distro has been in some strange build loop for last few days. I am not sure what the problem is.
I checked it several time. The status always was "building". The log was "only" few hours long => the build was automatically restarted several times. I wonder why. I do not see any build error and local build works. The i586 libreoffice package and x86_64 help packages have been built 7 days ago => it should not be caused by another commits in the openSUSE_12.3 or LibreOffice:Unstable repo.
Do you have any idea, please? Do some errors trigger automatic rebuild? Is there any build time out?
I think that it might help to force build on some more powerful hosts with more CPUs and more memory. Is it possible, please?
Such a automatic build restart would happen if the build runs out of memory. Yes one possibility. I have marked the current running build instance (build16/7) to be disabled. So if the build ends there for any reason, I can check why it got stopped.
Hm, interesting, there is NOT comming an external event to stop the build, but the build system suddenly stops and even process with PID 1 is not able to write the state back at all. That is the reason why it does loop. [28685s] [build CXX] chart2/source/controller/dialogs/dlg_ObjectProperties.cxx [28706s] [build CXX] chart2/source/controller/dialogs/dlg_ShapeFont.cxx [28721s] [build CXX] chart2/source/controller/dialogs/dlg_ShapeParagraph.cxx [28729s] No buildstatus set, either the base system is broken (glibc/bash/perl) [28729s] or the build host has a kernel or hardware problem... dead -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Dienstag, 16. Juli 2013, 15:11:09 schrieb Petr Mladek:
Adrian Schröter píše v Út 16. 07. 2013 v 14:45 +0200:
Am Dienstag, 16. Juli 2013, 14:28:10 schrieb Marcus Meissner:
On Tue, Jul 16, 2013 at 02:03:10PM +0200, Petr Mladek wrote:
Hi,
the "libreoffice" package in the "LibreOffice:Unstable" project and "openSUSE_12.3 x86_64" distro has been in some strange build loop for last few days. I am not sure what the problem is.
I checked it several time. The status always was "building". The log was "only" few hours long => the build was automatically restarted several times. I wonder why. I do not see any build error and local build works. The i586 libreoffice package and x86_64 help packages have been built 7 days ago => it should not be caused by another commits in the openSUSE_12.3 or LibreOffice:Unstable repo.
Do you have any idea, please? Do some errors trigger automatic rebuild? Is there any build time out?
I think that it might help to force build on some more powerful hosts with more CPUs and more memory. Is it possible, please?
Such a automatic build restart would happen if the build runs out of memory.> Yes one possibility. I have marked the current running build instance (build16/7) to be disabled. So if the build ends there for any reason, I can check why it got stopped.
Ah, in the mean time, Tomas Chvatal suggested to use constrains. So, I added the following into prjconf and restarted the build:
%if %suse_version == 1230 %ifarch x86_64 Constraint: hardware:physicalmemory:size unit="M" 5000 %endif %endif
Tomas says: The problem is that there are only very few machines with enough memory. There are more spec files in the libreoffice source dir. We do not know how to limit the constrain only to the "libreoffice" package. If we do the global limit, the build takes several days because of lack of machines.
Tomas is pretty sure that problem is with memory.
Might be. I thought I should have seen an OOM message then, which I did not saw. But it is worth to try.
I am sorry that I was so fast and stopped the build. We are a bit in hurry. Tomas would like to promote the LibreOffice 4.1 test builds on the openSUSE conference and the most important 12.3 build is not ready.
hm, you stopped it and I saw now line? grumbel, need to check the worker code :/ -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Adrian Schröter píše v Út 16. 07. 2013 v 15:16 +0200:
Am Dienstag, 16. Juli 2013, 15:11:09 schrieb Petr Mladek:
Ah, in the mean time, Tomas Chvatal suggested to use constrains. So, I added the following into prjconf and restarted the build:
%if %suse_version == 1230 %ifarch x86_64 Constraint: hardware:physicalmemory:size unit="M" 5000 %endif %endif
Tomas says: The problem is that there are only very few machines with enough memory. There are more spec files in the libreoffice source dir. We do not know how to limit the constrain only to the "libreoffice" package. If we do the global limit, the build takes several days because of lack of machines.
Tomas is pretty sure that problem is with memory.
Might be. I thought I should have seen an OOM message then, which I did not saw. But it is worth to try.
I am still lost. The build has been "automatically" restarted several times today. It was mostly scheduled to the host "cloud132:2". I have disabled the "debuginfo" flag to reduce the memory and disk usage but it did not help. I really need your help. Could you please disable the build on the host and send me the build log when it fails? Just for record, it is: + package: libreoffice + project: LibreOffice:Unstable + distro: openSUSE_12.3 + arch: x86_64 + current build host: cloud132:2 I promise, I will not stop the build myself this time :-) Best Regards, Petr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Mittwoch, 17. Juli 2013, 17:50:49 schrieb Petr Mladek:
Adrian Schröter píše v Út 16. 07. 2013 v 15:16 +0200:
Am Dienstag, 16. Juli 2013, 15:11:09 schrieb Petr Mladek:
Ah, in the mean time, Tomas Chvatal suggested to use constrains. So, I added the following into prjconf and restarted the build:
%if %suse_version == 1230 %ifarch x86_64 Constraint: hardware:physicalmemory:size unit="M" 5000 %endif %endif
Tomas says: The problem is that there are only very few machines with enough memory. There are more spec files in the libreoffice source dir. We do not know how to limit the constrain only to the "libreoffice" package. If we do the global limit, the build takes several days because of lack of machines.
Tomas is pretty sure that problem is with memory.
Might be. I thought I should have seen an OOM message then, which I did not saw. But it is worth to try.
I am still lost. The build has been "automatically" restarted several times today. It was mostly scheduled to the host "cloud132:2".
I have disabled the "debuginfo" flag to reduce the memory and disk usage but it did not help.
I really need your help. Could you please disable the build on the host and send me the build log when it fails?
Just for record, it is:
+ package: libreoffice + project: LibreOffice:Unstable + distro: openSUSE_12.3 + arch: x86_64 + current build host: cloud132:2
I promise, I will not stop the build myself this time :-)
marked as stopped. I dunno if I will have internet today though... -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Donnerstag, 18. Juli 2013, 06:35:35 schrieb Adrian Schröter:
Am Mittwoch, 17. Juli 2013, 17:50:49 schrieb Petr Mladek:
Adrian Schröter píše v Út 16. 07. 2013 v 15:16 +0200:
Am Dienstag, 16. Juli 2013, 15:11:09 schrieb Petr Mladek:
Ah, in the mean time, Tomas Chvatal suggested to use constrains. So, I added the following into prjconf and restarted the build:
%if %suse_version == 1230 %ifarch x86_64 Constraint: hardware:physicalmemory:size unit="M" 5000 %endif %endif
Tomas says: The problem is that there are only very few machines with enough memory. There are more spec files in the libreoffice source dir. We do not know how to limit the constrain only to the "libreoffice" package. If we do the global limit, the build takes several days because of lack of machines.
Tomas is pretty sure that problem is with memory.
Might be. I thought I should have seen an OOM message then, which I did not saw. But it is worth to try.
I am still lost. The build has been "automatically" restarted several times today. It was mostly scheduled to the host "cloud132:2".
I have disabled the "debuginfo" flag to reduce the memory and disk usage but it did not help.
I really need your help. Could you please disable the build on the host and send me the build log when it fails?
Just for record, it is: + package: libreoffice
+ project: LibreOffice:Unstable + distro: openSUSE_12.3 + arch: x86_64
+ current build host: cloud132:2
I promise, I will not stop the build myself this time :-)
marked as stopped. I dunno if I will have internet today though...
So, now it succeeded :) It was building on a system with 6000MB physical memory. You may want to requier 4-5GB <physicalmemory> in your constraints file. (The standard <memory> tag allows also to take swap) -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 18.07.2013 07:08, Adrian Schröter wrote:
I promise, I will not stop the build myself this time :-)
marked as stopped. I dunno if I will have internet today though...
So, now it succeeded :)
It was building on a system with 6000MB physical memory. You may want to requier 4-5GB <physicalmemory> in your constraints file.
(The standard <memory> tag allows also to take swap)
There is a similiar case in factory going on right now: # grep i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 dispatcher.log* assignjob i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 -> x86_64:build31:9 assignjob i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 -> x86_64:build31:9 assignjob i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 -> x86_64:build31:12 assignjob i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 -> x86_64:build31:2 assignjob i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 -> x86_64:build31:8 assignjob i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 -> x86_64:cloud133:1 assignjob i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 -> x86_64:cloud133:1 assignjob i586/openSUSE:Factory::standard::kernel-pae-4acba552ac54c40c002b10874660e082 -> x86_64:cloud110:4 Due to the lack of timestamps, I have no idea what's going on Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Adrian Schröter
-
Marcus Meissner
-
Petr Mladek
-
Stephan Kulow