[opensuse-buildservice] idle build and blocked by other packages ques processinq
Could the the idle build que's be used (when available), to find and process packages in the 'Blocked by other packages' que and build them ?. Perhaps it could shorten the waiting timefor packages that are blocked. Thanks Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2010-04-24 03:14:13 +0000, doiggl@velocitynet.com.au wrote:
Could the the idle build que's be used (when available), to find and process packages in the 'Blocked by other packages' que and build them ?. Perhaps it could shorten the waiting timefor packages that are blocked.
blocked means you wait for lower packages to finish. If you build blocked now, you will have to build it again once the dependency is done. That wouldnt make much sense as we could use that build time better elsewhere. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Could the 'lower packages to finish' be done on the current idle services
(if available) to shorten the time and allow previous blocked packages to
become ready for processing ?
-Glenn
On Sat, 24 Apr 2010 13:10:06 +0200, Marcus Rueckert
blocked means you wait for lower packages to finish. If you build blocked now, you will have to build it again once the dependency is done.
That wouldnt make much sense as we could use that build time better elsewhere.
darix
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 24/04/10 13:39, doiggl@velocitynet.com.au wrote:
Could the 'lower packages to finish' be done on the current idle services (if available) to shorten the time and allow previous blocked packages to become ready for processing ? -Glenn
That is already what is done. Packages enter a queue and are built as soon as is possible pretty much. What is the cause of your confusion? Is it that there are build hosts idle while packages are waiting to be built? Let me try to explain. First imagine a state where no packages exist. No jobs to do. All build hosts idle. Then someone adds some packages; say Qt4 and KDE SC which depends on it. Imagine Qt4 build doesn't need any dependencies. So no problem, one build host starts that job immediately. This might take say 2hours. Now the OBS starts considering all the other packages - they depend on libqt4. They will need to be built with the Qt4 package which is not yet available (it is still being built). So they enter the "blocked" state waiting for Qt4 build to finish. The UI displays "blocked: Qt4" and the number of blocked packages in statistics goes up. It doesn't matter how many idle build hosts you have, there is no way to begin the KDE SC build yet. So therefore you will quite often see there being packages in blocked state, and also build hosts being idle. Blocked means "dependencies are not ready yet". There is no way to speed this up except to make sure your packages do not have unnecessary dependencies. When the build dependencies are all ready, the package will move from a blocked to a scheduled state which means "ready to build; in build queue". The condition you should not see is packages in scheduled state and build hosts being idle. That would be an indicator of inefficiency. But I don't see that on the OBS. Regards, Tejas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
doiggl＠velocitynet.com.au -
Marcus Rueckert -
Tejas Guruswamy