Autotest change SSP failure to test ABORT

Since the *test* is not really failing, a hard fail is confusing for
owners. It makes more sense for the test to be aborted than to have
failed if SSP cannot be created.

BUG=b:184304822
TEST=cq/stub_Pass

Change-Id: Ia51ea41993550b9de083e17081224b4cfb457549
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/3157755
Tested-by: Derek Beckett <dbeckett@chromium.org>
Auto-Submit: Derek Beckett <dbeckett@chromium.org>
Reviewed-by: Otabek Kasimov <otabek@google.com>
Commit-Queue: Derek Beckett <dbeckett@chromium.org>
diff --git a/server/autoserv b/server/autoserv
index dbb85c6..d3bf31e 100755
--- a/server/autoserv
+++ b/server/autoserv
@@ -207,7 +207,7 @@
                                            job_folder=_LXC_JOB_FOLDER,
                                            dut_name=dut_name)
     except Exception as e:
-        job.record('FAIL', None, None,
+        job.record('ABORT', None, None,
                    'Failed to setup container for test: %s. Check logs in '
                    'ssp_logs folder for more details.' % e)
         raise