Setting max TTL for upstream GCM messages to 1 day to match server side

chrome/test/data/extensions/api_test/gcm/functions/send/send.js

Index: chrome/test/data/extensions/api_test/gcm/functions/send/send.js
diff --git a/chrome/test/data/extensions/api_test/gcm/functions/send/send.js b/chrome/test/data/extensions/api_test/gcm/functions/send/send.js
index 3ea1728654e85db21ae582c65531fba428b2984b..8749ec4591527c8a092229b2f0972666b8bbb042 100644
--- a/chrome/test/data/extensions/api_test/gcm/functions/send/send.js
+++ b/chrome/test/data/extensions/api_test/gcm/functions/send/send.js
@@ -6,7 +6,7 @@ function createMessage() {
   return {
     messageId: "message-id",
     destinationId: "destination-id",
-    timeToLive: 2419200,
+    timeToLive: 86400,
     data: {
       "key1": "value1",
       "key2": "value"
@@ -61,7 +61,7 @@ chrome.test.runTests([
     expectFailureWhen(function(message) { message.timeToLive = -1; });
   },
   function failureWhenTtlIsTooLarge() {
-    expectFailureWhen(function(message) { message.timeToLive = 24192001; });
+    expectFailureWhen(function(message) { message.timeToLive = 86401; });
   },
   function failureWhenMessageIdMissing() {
     expectFailureWhen(function(message) { delete message.messageId; });