treat out of space during fetch as out of space build failure

so that it gets sorted as spurrious instead of error and ends up in the retry-regressed-list.txt
and the crate gets a change at a retry

Author: Skgland

src/runner/worker.rs

@@ -2,7 +2,7 @@ use crate::agent::AgentApi;
 use crate::crates::Crate;
 use crate::experiments::{Experiment, Mode};
 use crate::prelude::*;
-use crate::results::{BrokenReason, TestResult};
+use crate::results::{BrokenReason, TestResult, FailureReason};
 use crate::runner::tasks::{Task, TaskStep};
 use crate::runner::test::detect_broken;
 use crate::runner::OverrideResult;
@@ -212,7 +212,9 @@ impl<'a> Worker<'a> {
                                     // this too often we'd replace the
                                     // machine, but it's not very clear
                                     // what "too often" means here.
-                                    return Err(e);
+                                    return Err(e.context(OverrideResult(TestResult::BuildFail(
+                                        FailureReason::NoSpace,
+                                    ))));
                                 } else {
                                     log::warn!(
                                         "Retrying crate fetch in 3 seconds (attempt {})",