Make callers of FromUTC(Local)Exploded in net/ use new time API.

net/disk_cache/blockfile/eviction.cc

Index: net/disk_cache/blockfile/eviction.cc
diff --git a/net/disk_cache/blockfile/eviction.cc b/net/disk_cache/blockfile/eviction.cc
index 52fca5fb7d0254ca1c0194bfd8a3268e9e48310e..68f65b4bdcbe434b7fffeb13f0d3376727003225 100644
--- a/net/disk_cache/blockfile/eviction.cc
+++ b/net/disk_cache/blockfile/eviction.cc
@@ -275,12 +275,10 @@ void Eviction::ReportTrimTimes(EntryImpl* entry) {
       backend_->FirstEviction();
     } else {
       // This is an old file, but we may want more reports from this user so
-      // lets save some create_time.
-      Time::Exploded old = {0};
-      old.year = 2009;
-      old.month = 3;
-      old.day_of_month = 1;
-      header_->create_time = Time::FromLocalExploded(old).ToInternalValue();
+      // lets save some create_time. Conversion cannot fail here.
+      const base::Time time_2009_3_1 =
+          base::Time::FromInternalValue(12985574400000000);
+      header_->create_time = time_2009_3_1.ToInternalValue();

[eroman, 2016/10/27 21:44:34]

For the record -- this is a bit different from what was happening before (it is
now using a fixed time stamp, whereas before it was using a timestamp based on
the user's timezone).

However I believe using a fixed timestamp as being done now is the correct
approach.

Also I wonder if we should simplify this to:

// 2009/03/01 (midnight UTC)
header_->create_time = 12985574400000000;

.. But on the other h and the documentation for |create_time| is pretty bad and
mentions nothing about the granularity or epoch of the timestamp, so perhaps
just using base::Time's "internal value" as you have done here is more
consistent with the surrounding code.

[maksims (do not use this acc), 2016/11/29 07:38:56]

Ok, thanks. Let it be like this.

     }
   }
 }