commit 26ef4260be1cd972a375081232af8bb543b6c5fc
author Jakob Juelich <jakobjuelich@chromium.org> Wed Sep 17 15:24:15 2014 -0700
committer chrome-internal-fetch <chrome-internal-fetch@google.com> Tue Sep 23 04:20:47 2014 +0000
tree 0a3aaf5c4802afc2b1d502c330d9b484de318ffe
parent efa95313e9886896e3fcf43f2ae0cd939ec3562c

[autotest] Set shard to NULL for completed jobs.

Completed job's shards are set to NULL to signal they should be
uploaded to the master again.

BUG=None
DEPLOY=scheduler
TEST=Run suites

Change-Id: Icd040c895ca6f2a5e3cfcc53e762a94f5b442f58
Reviewed-on: https://chromium-review.googlesource.com/218721
Reviewed-by: Prashanth B <beeps@chromium.org>
Commit-Queue: Jakob Jülich <jakobjuelich@chromium.org>
Tested-by: Jakob Jülich <jakobjuelich@chromium.org>

scheduler/scheduler_models.py

diff --git a/scheduler/scheduler_models.py b/scheduler/scheduler_models.py
index 004711c..6bb4b88 100644
--- a/scheduler/scheduler_models.py
+++ b/scheduler/scheduler_models.py
@@ -633,6 +633,9 @@
 
         if complete:
             self._on_complete(status)
+            if self.job.shard_id is not None:
+                # If shard_id is None, the job will be synced back to the master
+                self.job.update_field('shard_id', None)
             self._email_on_job_complete()
 
         should_email_status = (status.lower() in _notify_email_statuses or