Am Donnerstag, 30. Juli 2009 schrieb Dominique Leuenberger:

...

...

...

On 7/30/2009 at 18:05, "Hans-Peter Jansen" wrote:

Hi,

Shouldn't the scheduled jobs appear in http://build.opensuse.org/monitor?

The monitor shows the currently running hobs and a table of 'what's more to do" at the bottom.

Dominique,call me blind, please, but neither konqueror nor firefox show such a thing. A webpage archive is attached. Are you able to locate it there? Pete

Hello It would be nice to know X percent in the blocked queue are waiting for packageY. Then perhaps pick packageY that is blocking the most to get compiled sooner rather than later, in the hope to decrease the total waiting time in the blocked queue. Glenn On Thu, 30 Jul 2009 18:59:47 +0200, "Dominique Leuenberger" wrote:

The "What's more table" only contains numbers, how many jobs more are to be be done. At the moment it shows for:

i586: 2175 waiting queue, 16979 blocked x86_64: 1817 waiting queue; 16264 blocked.

I hope nobody ever comes to the idea to show the entire list with package names :) The list of all scheduled packages is internal to the scheduler and is not put on the page. Sorry for not being clear in my last mail.

Dominique

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Dominique wrote

The only way to reduce the waiting time is throwing more build power at it.

If you have 200 packages, each taking 30 minutes to compile, it's going to take 100 hours, no matter in what order you build them. Except in the rare case that all packages are waiting for a single build (example gcc). But then, this also won't change, as it would block everything else, anyhow it's 'the only' possibility to start with, as everything is blocked.

So in short: I guess to get shorter cycles, just more build hosts need to be connected. (which of course summarizes down to somebody needing to

Hello Thanks Dominique, is there any possibility of utilizing the idle hosts to help out even though it is a different platform e.g ppc64 [37 out of 197] https://build.opensuse.org/monitor Cheers Glenn throw

money in).

A 'distributed' approach might be interesting, but I understand that the question of trusting RPMs built in such a way would be very very high up on the list (no guarantee a remote worker is not tampering the created RPMs).

Dominique

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org