hydra-evaluator: Fix error handling in fetching inputs
[?]
Sep 11, 2015, 11:49 AM
7OBWA6AZZ4THWIIJE5HZUPDFZ3Z5XKE6BSQ3I623PJVN6ZTKIAYQCDependencies
- [2]
NS7SND6Rhydra-evaluator: Send statistics to statsd - [3]
7ZYBTNJJrevert unmeant previous change which caused errors to stay, even after successful evaluation of jobs - [4]
RFE6T5LG* Store jobset evaluations in the database explicitly. This includes - [5]
SS4TZXNUDistinguish between permanent evaluation errors and transient input errors - [6]
53PW36WShydra-evaluator: When evaluating a single jobset, exit with a failure code if evaluation fails - [7]
WQXF2T3Dhydra-evaluator: Don't require $HYDRA_CONFIG - [8]
LZO3C2KI* Hack around those SQLite timeouts: just retry the transaction. - [9]
FYO6NECEhydra - [10]
PCKLFRT5Support push notification of repository changes - [11]
NI5BVF2V* In job inputs of type "build", allow the project and jobset names of - [12]
RXVJFQ5AEvaluator cleanups - [13]
WVD3YYONhydra-evaluator: Add some debug code - [*]
N22GPKYT* Put info about logs / build products in the DB.
Change contents
- edit in src/script/hydra-evaluator at line 111
my $fetchError = $@; - replacement in src/script/hydra-evaluator at line 117
if ($@) {if ($fetchError) { - replacement in src/script/hydra-evaluator at line 119
my $msg = $@;print STDERR $msg;print STDERR $fetchError; - replacement in src/script/hydra-evaluator at line 121
$jobset->update({ lastcheckedtime => time, fetcherrormsg => $msg }) if !$dryRun;$jobset->update({ lastcheckedtime => time, fetcherrormsg => $fetchError }) if !$dryRun; - edit in src/script/hydra-evaluator at line 293
my $checkError = $@; - replacement in src/script/hydra-evaluator at line 299[3.20]→[3.2252:2288](∅→∅),[3.1454]→[3.2252:2288](∅→∅),[3.2252]→[3.2252:2288](∅→∅),[3.2288]→[3.1273:1300](∅→∅)
if ($@) {my $msg = $@;print STDERR $msg;if ($checkError) {print STDERR $checkError; - replacement in src/script/hydra-evaluator at line 303
setJobsetError($jobset, $msg);setJobsetError($jobset, $checkError);