Context:
Ofborg should eval using hydra-eval-jobs, for an in-depth evaluation.
Though, with that particular failure (b3ef282fd5c37d98b550e04c596136db8a9e978b), hydra-eval-jobs did not return the error. The only output was:
hydra-eval-jobs returned exit code 1:
error: unexpected EOF reading a line
An strace of this revealed that something transmitted the error, but also something read all of the error.
For appropriate CI use, the error would have to be available, otherwise, it's a wild goose chase. (This is actually an Hydra issue though.)
Another concern, is that this evaluation takes quite a long time. At least it does on my 2012-era Xeon workstation. I wonder if that would cause additional undue load on ofborg.
Context:
Ofborg should eval using
hydra-eval-jobs, for an in-depth evaluation.Though, with that particular failure (
b3ef282fd5c37d98b550e04c596136db8a9e978b),hydra-eval-jobsdid not return the error. The only output was:An
straceof this revealed that something transmitted the error, but also somethingreadall of the error.For appropriate CI use, the error would have to be available, otherwise, it's a wild goose chase. (This is actually an Hydra issue though.)
Another concern, is that this evaluation takes quite a long time. At least it does on my 2012-era Xeon workstation. I wonder if that would cause additional undue load on ofborg.