From 8f9417f8225063cbe8dfd6ed2c2479e670450748 Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Mon, 19 Oct 2009 12:36:15 +0000 Subject: [PATCH] * Be a bit less aggressive in rescheduling builds that have already been done. --- src/script/hydra_scheduler.pl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/script/hydra_scheduler.pl b/src/script/hydra_scheduler.pl index 3122cb40..0ab3e81a 100755 --- a/src/script/hydra_scheduler.pl +++ b/src/script/hydra_scheduler.pl @@ -280,10 +280,10 @@ sub checkJob { # cached result from the first). This ensures that the builds # with the highest ID will always be the ones that we want in # the channels. - # !!! Checking $drvPath doesn't take meta-attributes into + # !!! Checking $outPath doesn't take meta-attributes into # account. For instance, do we want a new build to be # scheduled if the meta.maintainers field is changed? - my @previousBuilds = $jobInDB->builds->search({drvPath => $drvPath, isCurrent => 1}); + my @previousBuilds = $jobInDB->builds->search({outPath => $outPath, isCurrent => 1}); if (scalar(@previousBuilds) > 0) { print "already scheduled/built\n"; $currentBuilds->{$_->id} = 1 foreach @previousBuilds;