[opensuse-buildservice] Jobs running and scheduling all the time
Hi, on our local instance we have an ARM worker integrated. This worker builds packages for Debian 8/9 and Ubuntu 16.04. However the buildprocess for debian9 never stops. It builds the package successfully and schedules it afterwards. Any suggestion what and where to check why this happens? Cheers -- Mathias Radtke --- http://uib.de/de/support-schulung/schulung/ --- uib gmbh Bonifaziusplatz 1B 55118 Mainz Tel. 06131 / 27561-16 phone:061312756116 Fax 06131 / 27561-22 phone:061312756122 E-Mail: m.radtke@uib.de Internet: www.uib.de Geschäftsführer: dr. detlef oertel & erol ueluekmen Handelsregister: Amtsgericht Mainz HRB 6942 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 4. Oktober 2017, 10:30:50 CEST wrote Mathias Radtke:
Hi,
on our local instance we have an ARM worker integrated. This worker builds packages for Debian 8/9 and Ubuntu 16.04.
However the buildprocess for debian9 never stops. It builds the package successfully and schedules it afterwards. Any suggestion what and where to check why this happens?
Check via "osc triggerreason" what is the cause of the build. It may be that there is a miss-match of packages which should be used in POV of the scheduler and is actually used as reported by the worker. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, 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 Mittwoch, 4. Oktober 2017, 10:30:50 CEST wrote Mathias Radtke:
Hi,
on our local instance we have an ARM worker integrated. This worker builds packages for Debian 8/9 and Ubuntu 16.04.
However the buildprocess for debian9 never stops. It builds the package successfully and schedules it afterwards. Any suggestion what and where to check why this happens? Check via "osc triggerreason" what is the cause of the build.
It may be that there is a miss-match of packages which should be used in POV of the scheduler and is actually used as reported by the worker. osc -v triggerreason Debian_9.0 armv7l https://obs.uib.local home:uibmz:opsi:opsi41-experimental opsi-linux-bootimage Debian_9.0 armv7l makeurl: https://obs.uib.local ['build', 'home:uibmz:opsi:opsi41-experimental', 'Debian_9.0', 'armv7l', 'opsi-linux-bootimage', '_reason'] []
Hi On 04.10.2017 10:41, Adrian Schröter wrote: meta change changed keys: md5sum autoconf md5sum automake md5sum autopoint md5sum autotools-dev md5sum binutils ... This list continues. The dispatcher.log seems to be ok. Sometimes I see a rpc timeout but nothin unusual there. Suggestions on what to do with the changed md5sums? Cheers -- Mathias Radtke --- http://uib.de/de/support-schulung/schulung/ --- uib gmbh Bonifaziusplatz 1B 55118 Mainz Tel. 06131 / 27561-16 phone:061312756116 Fax 06131 / 27561-22 phone:061312756122 E-Mail: m.radtke@uib.de Internet: www.uib.de Geschäftsführer: dr. detlef oertel & erol ueluekmen Handelsregister: Amtsgericht Mainz HRB 6942 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi, this problem of mine still exists. Packages are never build as .deb files. As soon as they finish the build process they get scheduled immediateley. Even with an disabled scheduler the packages are never build on the repos. Any suggestions? Cheers On 05.10.2017 08:35, Mathias Radtke wrote:
Hi
On Mittwoch, 4. Oktober 2017, 10:30:50 CEST wrote Mathias Radtke:
Hi,
on our local instance we have an ARM worker integrated. This worker builds packages for Debian 8/9 and Ubuntu 16.04.
However the buildprocess for debian9 never stops. It builds the package successfully and schedules it afterwards. Any suggestion what and where to check why this happens? Check via "osc triggerreason" what is the cause of the build.
It may be that there is a miss-match of packages which should be used in POV of the scheduler and is actually used as reported by the worker. osc -v triggerreason Debian_9.0 armv7l https://obs.uib.local home:uibmz:opsi:opsi41-experimental opsi-linux-bootimage Debian_9.0 armv7l makeurl: https://obs.uib.local ['build', 'home:uibmz:opsi:opsi41-experimental', 'Debian_9.0', 'armv7l', 'opsi-linux-bootimage', '_reason'] []
On 04.10.2017 10:41, Adrian Schröter wrote: meta change changed keys: md5sum autoconf md5sum automake md5sum autopoint md5sum autotools-dev md5sum binutils ...
This list continues. The dispatcher.log seems to be ok. Sometimes I see a rpc timeout but nothin unusual there.
Suggestions on what to do with the changed md5sums?
Cheers
-- Mathias Radtke --- http://uib.de/de/support-schulung/schulung/ --- uib gmbh Bonifaziusplatz 1B 55118 Mainz Tel. 06131 / 27561-16 phone:061312756116 Fax 06131 / 27561-22 phone:061312756122 E-Mail: m.radtke@uib.de Internet: www.uib.de Geschäftsführer: dr. detlef oertel & erol ueluekmen Handelsregister: Amtsgericht Mainz HRB 6942 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Okt 04 2017, Mathias Radtke <m.radtke@uib.de> wrote:
However the buildprocess for debian9 never stops. It builds the package successfully and schedules it afterwards. Any suggestion what and where to check why this happens?
Any notes in the dispatcher log? Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "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
participants (3)
-
Adrian Schröter -
Andreas Schwab -
Mathias Radtke