--archive_dir will now serve existing update.gz

autoupdate.py

Index: autoupdate.py
diff --git a/autoupdate.py b/autoupdate.py
index 2addd2c760976eeaa6382ed0b911d5f2b9a2088e..cc84c9613e5e56fb0f572c73665440170708c678 100644
--- a/autoupdate.py
+++ b/autoupdate.py
@@ -22,8 +22,9 @@ class Autoupdate(BuildObject):
   """Class that contains functionality that handles Chrome OS update pings.
 
   Members:
-    serve_only: Serve images from a pre-built image.zip file.  static_dir
-      must be set to the location of the image.zip.
+    serve_only: Serve updates from a pre-built image.zip file. If an update.gz

[sosa, 2010/11/23 19:50:36]

is newer*

+      newer than the extracted image exists in the static_dir, it will be

[sosa, 2010/11/23 19:50:36]

This is a little confusing.  Can you make another pass at this docstring.

+      served instead. static_dir must be set to the location of the image.zip.
     factory_config: Path to the factory config file if handling factory
       requests.
     use_test_image: Use chromiumos_test_image.bin rather than the standard.
@@ -545,6 +546,15 @@ class Autoupdate(BuildObject):
           self.forced_image,
           static_image_dir=static_image_dir)
     elif self.serve_only:
+      image_path = os.path.join(static_image_dir, self._GetImageName())
+      update_path = os.path.join(static_image_dir, UPDATE_FILE)
+
+      # If a valid update already exists, no need to generate.
+      if (os.path.exists(image_path) and os.path.exists(update_path) and
+          os.path.getmtime(image_path) < os.path.getmtime(update_path)):

[sosa, 2010/11/23 19:50:36]

Can you fold this into GenerateImageFromZip and remove Don's TODO?  That seems
like the better place.  Also, why not use MD5 hash's versus timestamps?

[DaleCurtis, 2010/11/23 20:11:20]

I can if you really want to. I think it's confusing to put it into
GenerateImageFromZip though unless we want to change the method.

Alternatively, does anyone actually use the ZIP generation? If not lets just
remove it and change serve_only to actually mean serve_only. Meaning, update.gz
and stateful.tgz must always be in the static_dir. No more 0-byte
chromiumos_test_image.bin's or hard to explain time stamp/md5 checks.

Going this route would also remove any of the caching concerns noted in Don's
TODO.

On 2010/11/23 19:50:36, sosa wrote:

[sosa, 2010/11/23 20:45:57]

I'm ok with removing the logic but you many want to email chromium-os-dev in
case.  I don't know of anyone who uses it as it was specifically added to
support test automation.

On 2010/11/23 20:11:20, dalec wrote:

[DaleCurtis, 2010/11/23 21:02:37]

Sent, I'll give it until next week before making any changes. We've already got
a patch in place to keep our Dev Server running.

On 2010/11/23 20:45:57, sosa wrote:

+        _LogMessage('Existing update found to serve.')
+        return UPDATE_FILE
+
       return self.GenerateImageFromZip(static_image_dir)
     else:
       if board_id: