revert unmeant previous change which caused errors to stay, even after successful evaluation of jobs

Dependencies

• [2] GA6XIXAN * Show the input bindings in evaluation error messages.
• [3] ZDENAYQI * email notification of evaluation errors to project owner (if desired)
• [4] FYO6NECE hydra
• [5] X27GNHDV * Basic job info in the database.
• [6] SHZLOM5M * eval-jobs -> hydra_eval_jobs.
• [7] QE253KG4 * Option to show the tail of a log.
• [8] LZO3C2KI * Hack around those SQLite timeouts: just retry the transaction.
• [9] NI5BVF2V * In job inputs of type "build", allow the project and jobset names of
• [*] N22GPKYT * Put info about logs / build products in the DB.
• [*] FDE3BJAP * Refactoring.

Change contents

• edit in src/script/hydra_scheduler.pl at line 47
  [3.612]

  [3.612]
  + print STDERR "\n" ;

  + print STDERR $errorMsg ;

  + print STDERR "\n" ;
• edit in src/script/hydra_scheduler.pl at line 51
  [3.670]

  [12.1179]
  + return if $errorMsg eq "";
• edit in src/script/hydra_scheduler.pl at line 167
  [2.608]→[5.893:899](∅→∅),[5.661]→[5.893:899](∅→∅),[5.893]→[5.893:899](∅→∅),[5.899]→[4.4925:4988](∅→∅)
  − }

  − if( !($msg eq "") ) {

  − setJobsetError($jobset, $msg);
• edit in src/script/hydra_scheduler.pl at line 168
  [4.4994]

  [5.9880]
  + setJobsetError($jobset, $msg);
• replacement in src/script/hydra_scheduler.pl at line 186
  [5.2437]→[4.4995:5088](∅→∅)
  − if( !($msg eq "") ) {

  − setJobsetError($jobset, $msg);

  − }
  [5.2437]

  [5.2480]
  + setJobsetError($jobset, $msg);