$previous_rec needed wider scope. I had accidentally narrowed the

scope when tixing the 'building' issue.

webtools/tinderbox2/src/lib/TinderDB/Build.pm

@@ -7,8 +7,8 @@
 # the build was and display a link to the build log.
 
 
-# $Revision: 1.11 $ 
-# $Date: 2001-01-06 01:30:37 $ 
+# $Revision: 1.12 $ 
+# $Date: 2001-01-09 15:43:39 $ 
 # $Author: kestes%staff.mail.com $ 
 # $Source: /home/jrmuizel/cvs-mirror/mozilla/webtools/tinderbox2/src/lib/TinderDB/Build.pm,v $ 
 # $Name:  $ 
@@ -757,6 +757,10 @@ sub apply_db_updates {
     my ($starttime) = $record->{'starttime'};
     my ($timenow) =  $record->{'timenow'};
 
+    # The time which the previous build started
+    my ($previous_rec) = $DATABASE{$tree}{$build}{'recs'}[0];
+
+
     # sanity check the record, taint checks are done in processmail.
     {
       BuildStatus::is_status_valid($buildstatus) ||
@@ -785,9 +789,6 @@ sub apply_db_updates {
 
     if ( defined($DATABASE{$tree}{$build}{'recs'}) ) {
       
-      # The time which the previous build started
-      my ($previous_rec) = $DATABASE{$tree}{$build}{'recs'}[0];
-
       # Why are we ignoring out of order recipts?  This came from the
       # original tinderbox?