)]}' { "log": [ { "commit": "669eea2a46e94b245668df89904173f31ea4c248", "tree": "111abecd973d734a477f5294c653fd09378003eb", "parents": [ "532774e20467dda807018956c761ba6dd054f325" ], "author": { "name": "Hung-Te Lin", "email": "hungte@chromium.org", "time": "Fri Jul 04 02:15:40 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Jul 09 05:32:28 2014" }, "message": "Allow early initialization for factory test mode.\n\nWe want to allow some initialization procedure in startup stage (before\nboot-services starts running UI) so we can customize UI default settings and\nupstart jobs for factory test mode.\n\nTo do that, the is_factory_mode (which reports true for both factory test and\ninstaller mode) must be divided into two new functions: is_factory_test_mode and\nis_factory_installer_mode.\n\nThe new factory-init.conf job is executed when boot-services starts, and runs\ninitialization script if it is available.\n\nBUG\u003dchrome-os-partner:30239\nTEST\u003dManual: Built a Link test image, boots in factory and non-factory mode.\n Built a factory installer image and boots correctly.\n\nChange-Id: I153baecb8bc66fa0199e9fb8bcf3c50a543f1c2c\nReviewed-on: https://chromium-review.googlesource.com/206676\nTested-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nCommit-Queue: Hung-Te Lin \u003chungte@chromium.org\u003e\n" }, { "commit": "532774e20467dda807018956c761ba6dd054f325", "tree": "9c81cbb43d2429c7fc38ac917cd0bc097dc74369", "parents": [ "eff387a2c292817aa77a074b2ccbb3f497ece80d" ], "author": { "name": "Hung-Te Lin", "email": "hungte@chromium.org", "time": "Tue Jul 08 04:12:15 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Jul 08 17:31:22 2014" }, "message": "factory: Graceful start and better UI integration.\n\nCurrently factory starts \"after\" UI (Chrome) being started, and needs to kill it\nfor a new session with appropriate parameters (with Telemetry). However, the\nfactory test environment is now always using Chrome and should start at the same\ntiming when UI (Chrome) is started -- no matter if we are using Telemetry mode\nor not.\n\nBy this change, we can reduce transition time and make a seamless integration\n(if not using Telemetry).\n\nNote the chvt and messages were made long ago when we were still using unstable\nX+GTK environment, and should be pretty safe to be dropped now.\n\nBUG\u003dchrome-os-partner:30239\nTEST\u003dManual: Built a Link factory test image, boots in Telemetry and\n Non-Telemetry modes correctly. Passed reboot tests.\n\nChange-Id: I4afcf97b625178ae4eaaa028673ee44bfde21618\nReviewed-on: https://chromium-review.googlesource.com/206796\nReviewed-by: Jon Salz \u003cjsalz@chromium.org\u003e\nCommit-Queue: Hung-Te Lin \u003chungte@chromium.org\u003e\nTested-by: Hung-Te Lin \u003chungte@chromium.org\u003e\n" }, { "commit": "eff387a2c292817aa77a074b2ccbb3f497ece80d", "tree": "c4ab00de6085c1549e0cb5be05867bf96d28339a", "parents": [ "f2792ecdb51ce9c87c476ee074f861baf14f2570" ], "author": { "name": "Ricky Liang", "email": "jcliang@chromium.org", "time": "Thu Jul 03 09:37:21 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Jul 08 17:30:54 2014" }, "message": "Add inhibit job for cros-disks in test image\n\nWe want auto-mount disabled in factory test image so that it will not\nconfuse our test programs.\n\nBUG\u003dchrome-os-partner:24798\nTEST\u003dBoot factory test image and verify cros-disks is inhibited.\n\nChange-Id: Iebcffab66e0a0f568f8cdef84cfbe5ad80c574bc\nReviewed-on: https://chromium-review.googlesource.com/206628\nReviewed-by: Vic Yang \u003cvictoryang@chromium.org\u003e\nReviewed-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nReviewed-by: Ben Chan \u003cbenchan@chromium.org\u003e\nCommit-Queue: Ricky Liang \u003cjcliang@chromium.org\u003e\nTested-by: Ricky Liang \u003cjcliang@chromium.org\u003e\n" }, { "commit": "f2792ecdb51ce9c87c476ee074f861baf14f2570", "tree": "7209ee56608954a848c71188586f239b6a007f3b", "parents": [ "9a97c848d238671e6ce839b796020efae7667863" ], "author": { "name": "Steve Fung", "email": "stevefung@chromium.org", "time": "Tue Jun 24 07:17:37 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Jun 25 01:31:38 2014" }, "message": "Move mounting of debugfs back to chromeos_startup script\n\nSince boards built without debugd do not have debugfs-access user and\ngroup, the mount command for debugfs will fail, causing the script to\nexit early before /run is mounted as tmpfs. Move the mount command\nback to chromeos_startup, which will continue execution after the\nmount.\n\nBUG\u003dchromium:388394\nTEST\u003dpanther boots with debugfs mounted.\nTEST\u003dduck boots, /run is mounted as tmpfs.\n\nChange-Id: I86a9aa99790d4692184a202c99c848c55469a1ab\nReviewed-on: https://chromium-review.googlesource.com/205353\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nCommit-Queue: Steve Fung \u003cstevefung@chromium.org\u003e\nTested-by: Steve Fung \u003cstevefung@chromium.org\u003e\n" }, { "commit": "9a97c848d238671e6ce839b796020efae7667863", "tree": "862fe640ba8913174155ccd201a72bf1c5e435ea", "parents": [ "ee065d0e1a1c0d03a0894c2ea7bd9756f4234c6e" ], "author": { "name": "mukesh agrawal", "email": "quiche@chromium.org", "time": "Fri Jun 20 23:35:05 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Mon Jun 23 21:48:20 2014" }, "message": "chromeos-init: rsyslog: include PID in log messages\n\nIncluding timestamps will make it more obvious when messages\ncome from different instances of a program. In particular,\nthis will be useful in cases where a daemon restarts.\n\nBUG\u003dchromium:387206\nTEST\u003dmanual\n\nManual test\n-----------\n1. boot with new config file installed\n2. grep shill /var/log/net.log | tail -1\n3. observer that log line includes shill\u0027s process id\n\nChange-Id: I35fe6fa71e108d2a9e8156c9af4e300cdd3b9462\nReviewed-on: https://chromium-review.googlesource.com/204961\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nCommit-Queue: mukesh agrawal \u003cquiche@chromium.org\u003e\n" }, { "commit": "ee065d0e1a1c0d03a0894c2ea7bd9756f4234c6e", "tree": "17d98fc384f112de8edfde28ad13b37ba3bfa30b", "parents": [ "8174b8279f6634431c39738dce7c8221f090a126" ], "author": { "name": "Alex Miller", "email": "milleral@chromium.org", "time": "Tue Feb 11 19:26:59 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sun Jun 22 00:24:06 2014" }, "message": "[init] Migrate to /run.\n\nIn preparation for a udev uprev, we need to mount /run as a tmpfs as one\nof the first things we do in the boot process. /run is meant to replace\n/var/run and related temporary storage areas, so we also symlink a\ncouple directories to their new names in /run.\n\nCQ-DEPEND\u003dIa5d124ba81997ba40c6c6a822c22bb5c90f1b613\nBUG\u003dchromium:320868\nTEST\u003dlumpy still boots\n\nChange-Id: If98e9b956536e1b35e22cb9ecb19fdd14974735a\nReviewed-on: https://chromium-review.googlesource.com/186240\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Steve Fung \u003cstevefung@chromium.org\u003e\nCommit-Queue: Steve Fung \u003cstevefung@chromium.org\u003e\n" }, { "commit": "8174b8279f6634431c39738dce7c8221f090a126", "tree": "20256a5b0d8abd6493e0dbb203b01b11ecdb2455", "parents": [ "ea4efd0d233bec1306194e611c95e74f03c951e4" ], "author": { "name": "mukesh agrawal", "email": "quiche@chromium.org", "time": "Wed Jun 11 01:25:14 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Jun 12 04:31:10 2014" }, "message": "chromeos-init: improve kernel logging\n\nSome messages were appearing in the kernel ring-buffer (as examined\nby dmesg), but not in /var/log/messages. It turns out that rsyslogd\ndefaults to filtering messages read from /proc/kmsg, so that only\nkernel messages are candidates for logging.\n\nThis default is bad for us, since init (upstart) logs to the kernel\nring buffer. Resolve the problem, by disabling rsyslogd\u0027s filtering\nof these messages.\n\nBUG\u003dchromium:383075\nTEST\u003dplatform_LogNonKernelKmsg\nCQ-DEPEND\u003dCL:203319\n\nChange-Id: I73075dcb12e1a37ea93f9bb690c68862849bd9ba\nReviewed-on: https://chromium-review.googlesource.com/203332\nTested-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: mukesh agrawal \u003cquiche@chromium.org\u003e\n" }, { "commit": "ea4efd0d233bec1306194e611c95e74f03c951e4", "tree": "ed31c48571cc603fef120a990598eec97ddd985d", "parents": [ "a989005e23e5aabc751f2d7d8ce5e6a2cdc6840e" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue Jun 10 17:50:02 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Jun 11 22:08:02 2014" }, "message": "Convert disableecho to an upstart job\n\nEcho on tty1 should be disabled in an upstart job and live in platform/init\ninstead of a C program.\n\nBUG\u003dchromium:360193\nTEST\u003demerge-lumpy chromeos-init. disable_echo.conf is now owned by\nchromeos-init.\nTEST\u003dRemove disable_echo.conf from a lumpy. During startup, hit random keys:\n -\u003e characters get printed on the splash screen.\nTEST\u003dUnmerge chromeos-disableecho and deploy chromeos-init on a lumpy. Hit\nrandom keys during startup: no character appear on the screen.\n\nCQ-DEPEND\u003dCL:203187\n\nChange-Id: I0085c58dcaa3c37b0dff882e191af352510ea60f\nReviewed-on: https://chromium-review.googlesource.com/203195\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: Daniel Erat \u003cderat@chromium.org\u003e\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "a989005e23e5aabc751f2d7d8ce5e6a2cdc6840e", "tree": "7027158c51091bca3b09c54e49b29e04c7c391b9", "parents": [ "cf0d6d4fb44045280c8e749527ad013a97f48f26" ], "author": { "name": "Mattias Nissler", "email": "mnissler@chromium.org", "time": "Mon May 26 12:53:59 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Jun 11 03:34:58 2014" }, "message": "Enforce block_devmode flag in chromeos_startup.\n\nWhen the block_devmode crossystem flag has been set by the device\nowner, we should block boots in developer mode.\n\nBUG\u003dchromium:375775\nTEST\u003dManual.\nCQ-DEPEND\u003dCL:201640\n\nChange-Id: I6ec90bf6377794f22ed08b40b750c3329eb183e6\nReviewed-on: https://chromium-review.googlesource.com/201650\nReviewed-by: Mattias Nissler \u003cmnissler@chromium.org\u003e\nTested-by: Mattias Nissler \u003cmnissler@chromium.org\u003e\nCommit-Queue: Julian Pastarmov \u003cpastarmovj@chromium.org\u003e\n" }, { "commit": "cf0d6d4fb44045280c8e749527ad013a97f48f26", "tree": "e4fe16647475e4bdc5415c45e6604e9ffe52f9c7", "parents": [ "6b8247e36acdca8da87d9fa0e1aaa66463c9970e" ], "author": { "name": "Alexander Alekseev", "email": "alemate@google.com", "time": "Mon Jun 02 14:00:38 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Jun 03 20:42:56 2014" }, "message": "Report Login.UsersActiveWeekly.Percent UMA metric.\n\nBUG\u003dchromium:365352\nTEST\u003dnone\n\nChange-Id: Id1d95d052e32eff438d97685ff6c74d356b19aa4\nReviewed-on: https://chromium-review.googlesource.com/202370\nReviewed-by: Alexander Alekseev \u003calemate@chromium.org\u003e\nTested-by: Alexander Alekseev \u003calemate@chromium.org\u003e\nReviewed-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Alexander Alekseev \u003calemate@chromium.org\u003e\n" }, { "commit": "6b8247e36acdca8da87d9fa0e1aaa66463c9970e", "tree": "d32d4819d220e2107b97b03d8c9d51e30353bda7", "parents": [ "010f56b0619253858f2d1e1a559e5160210b52f9" ], "author": { "name": "Alexander Alekseev", "email": "alemate@google.com", "time": "Fri May 30 17:11:07 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sat May 31 01:46:57 2014" }, "message": "Add Login.UsersActiveWeekly UMA metric.\n\nBUG\u003dchromium:365352\nTEST\u003dmanual\n\nChange-Id: Idfa406308ea4b37b89c82d97f1091bcee950017e\nReviewed-on: https://chromium-review.googlesource.com/202280\nReviewed-by: Alexander Alekseev \u003calemate@chromium.org\u003e\nTested-by: Alexander Alekseev \u003calemate@chromium.org\u003e\nReviewed-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Alexander Alekseev \u003calemate@chromium.org\u003e\n" }, { "commit": "010f56b0619253858f2d1e1a559e5160210b52f9", "tree": "271c98b9afb4301a1a669a49c8b01d0124d4ed09", "parents": [ "dfc77a0a49aae459f23bc8da375fe15fb1514348" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Thu May 29 01:26:47 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu May 29 23:14:19 2014" }, "message": "periodic_scheduler: allow test to work in out-of-tree builds\n\nIn order to speed up the init build, we want to enable out-of-tree\nbuilding. Tweak the unittest to support that.\n\nBUG\u003dchromium:375989\nTEST\u003d`FEATURES\u003dtest emerge-amd64-generic chromeos-init` passes (out of tree)\nTEST\u003d`FEATURES\u003dtest emerge-amd64-generic chromeos-init` passes (in tree)\nTEST\u003d`./periodic_scheduler_unittest` passes\n\nChange-Id: I7b66ce7194bd7b644b594c4e024a67356465a95f\nReviewed-on: https://chromium-review.googlesource.com/202000\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "dfc77a0a49aae459f23bc8da375fe15fb1514348", "tree": "c1be56450ed84edf73de5bd289b625993364ae3e", "parents": [ "fc78e140ef4402c05222fd4396f2edf361f5748d" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Tue May 27 16:00:09 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed May 28 23:58:35 2014" }, "message": "periodic_scheduler: add a basic sanity test\n\nBUG\u003dchromium:375989\nTEST\u003d`FEATURES\u003dtest emerge-amd64-generic chromeos-init` passes\nTEST\u003d`./periodic_scheduler_unittest` with older periodic_scheduler fails\n\nChange-Id: I2aa91022baf8215862ec7de81300ef1c71520525\nReviewed-on: https://chromium-review.googlesource.com/201496\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "fc78e140ef4402c05222fd4396f2edf361f5748d", "tree": "39a1a1d2d03d39af1a8740fc6c97208c3d7f5192", "parents": [ "fddc60c1dc874514e8d4d1d818ac83ad004c85f8" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Tue May 27 20:30:55 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed May 28 04:51:51 2014" }, "message": "periodic_scheduler: move timeout value to the jobs themselves\n\nRather than clamp the runtime of the job to 5 minutes, let the job\ndeclare its max timeout value. Some jobs want to run for more than\n5 minutes (like crash_sender).\n\nBUG\u003dchromium:377981\nTEST\u003d`./periodic_scheduler_unittest` passes\nCQ-DEPEND\u003dCL:201404\n\nChange-Id: If411bf01e96007ee8a4a83e144f5b8306c48103c\nReviewed-on: https://chromium-review.googlesource.com/201719\nCommit-Queue: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\n" }, { "commit": "fddc60c1dc874514e8d4d1d818ac83ad004c85f8", "tree": "1ac831f1c7a89a82ccca446c74b0e450df988517", "parents": [ "11967e04e4efbf069c01bc470175b95eff748e68" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Fri May 23 19:10:37 2014" }, "committer": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Fri May 23 19:38:11 2014" }, "message": "periodic_scheduler: fix timeout invocation\n\nThe current code forgets to pass a time spec to the -k param leading\nit to barf whenever it tries to run a job:\n + timeout -k 300 sh -c \"$@\" -- /sbin/crash_sender\n timeout: invalid time interval \u0027sh\u0027\n Try \u0027timeout --help\u0027 for more information.\n\nSet the kill fallback to 10 seconds. This will fire after the main\ntimeout has been sent to the code.\n\nWhile we\u0027re here, drop the shell indirection. None of our jobs are\nusing it, and it\u0027s not clear whether we want to let people run shell\ncode directly rather than just invoke a program. This saves us from\nspawning the shell and leaving it running for the life of the job.\n\nBUG\u003dchromium:375989\nTEST\u003dmanual; loaded onto a dev device and watched crash_sender get run\n\nChange-Id: I4cb6dc752c415803047bb4c3eb310589ab444d0d\nReviewed-on: https://chromium-review.googlesource.com/201350\nReviewed-by: Ben Chan \u003cbenchan@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "11967e04e4efbf069c01bc470175b95eff748e68", "tree": "12d27f32bc3792e99018026c7977ad42f26e086e", "parents": [ "60dc226ebc681a284634163afb272f0b6ab9ebeb" ], "author": { "name": "Hung-Te Lin", "email": "hungte@chromium.org", "time": "Tue May 20 09:14:22 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed May 21 04:22:17 2014" }, "message": "clobber-state: Ensure active kernel still boots after wiping.\n\nWhen an auto update is in progress, there is a period that system will start\nwith a kernel without GPT \"successful\" bit set. If we do wiping (ex, power-wash)\nat that time, system may run out of trial counter and fall to recovery mode.\n\nTo prevent that, we should always set \"successful\" bit and set priority to\npositive number before wiping inactive partitions.\n\nBUG\u003dchrome-os-partner:28996\nTEST\u003dmanual: cgpt set /dev/sda2 -S 0 -T 3 -P 3; # simulate an AU\n cgpt set /dev/sda4 -S 1 -T 0 -P 2; # simulate an AU\n Reboot, power-wash\n cgpt show /dev/sda # see sda2.S\u003d1, still boots.\n\nChange-Id: I1e3dfd391db2e4aafdb7929b9f3d2b02d4bd14c8\nReviewed-on: https://chromium-review.googlesource.com/200528\nTested-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nReviewed-by: Rong Chang \u003crongchang@chromium.org\u003e\nCommit-Queue: Hung-Te Lin \u003chungte@chromium.org\u003e\n" }, { "commit": "60dc226ebc681a284634163afb272f0b6ab9ebeb", "tree": "3acf3aabc6139684f366c73ac9f317c6490ef756", "parents": [ "b3dc2815501fafcbcff9b12131547ae20e6bfb5b" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Mon May 19 18:37:35 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue May 20 07:34:03 2014" }, "message": "periodic_scheduler: tweak logging style slightly\n\nThe current log output looks like:\n2014-05-19T14:23:28.824566-04:00 localhost periodic_scheduler: running /sbin/crash_sender for crash_sender\n2014-05-19T14:23:28.827682-04:00 localhost periodic_scheduler: crash_sender completed\n\nThe new output is more consistent:\n2014-05-19T14:23:28.824566-04:00 localhost periodic_scheduler: crash_sender: running /sbin/crash_sender\n2014-05-19T14:23:28.827682-04:00 localhost periodic_scheduler: crash_sender: job completed\n\nBUG\u003dNone\nTEST\u003dran it\n\nChange-Id: I0a542d63c15c5c3a9d10683f424b2190c983269d\nReviewed-on: https://chromium-review.googlesource.com/200382\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nCommit-Queue: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "b3dc2815501fafcbcff9b12131547ae20e6bfb5b", "tree": "28013a6def8b12301d323f114dc857c979914ea4", "parents": [ "655189a755d09e3071a3ba41f8fecf92ffef5a8c" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue May 06 21:11:10 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed May 07 19:58:57 2014" }, "message": "Remove crash-sender.conf\n\nPart of a three CLs commit that moves crash-sender.conf from platform/init to\nplatform/crash-reporter.\n\nBUG\u003dchromium:346449\nTEST\u003dBuild chromeos-init. crash-sender.conf is no longer owned by chromeos-init.\n\nCQ-DEPEND\u003dI1f536361e4089a38c70ee9b77f126b1b9881abd8\nCQ-DEPEND\u003dI7e8da8b755f531bf1987c369692cf570eb7a5548\n\nChange-Id: If4ed3501dc7764515eee5284b608859b97652625\nReviewed-on: https://chromium-review.googlesource.com/198584\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "655189a755d09e3071a3ba41f8fecf92ffef5a8c", "tree": "12f0240c80679887c608f7ec9c8b1bef1e1492bb", "parents": [ "defdfbeb3633a09b7ed6cd1c6554d43f45512409" ], "author": { "name": "Mattias Nissler", "email": "mnissler@chromium.org", "time": "Fri May 02 10:50:25 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Mon May 05 15:16:07 2014" }, "message": "Guarantee udev processing is complete on started system-services\n\nChange udev-trigger to be a task job so it needs to complete before the\nstarted event for system-services gets emitted. Update documentation in\nsystem-services to call this out.\n\nBUG\u003dchromium:358213\nTEST\u003dSystem boots up properly.\n\nChange-Id: Ie078526d60b7c869f44e795d8a3c2f3073ddac0e\nReviewed-on: https://chromium-review.googlesource.com/198000\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nReviewed-by: Mattias Nissler \u003cmnissler@chromium.org\u003e\nCommit-Queue: Mattias Nissler \u003cmnissler@chromium.org\u003e\nTested-by: Mattias Nissler \u003cmnissler@chromium.org\u003e\n" }, { "commit": "defdfbeb3633a09b7ed6cd1c6554d43f45512409", "tree": "7b4550c8251dd61c0e43fec524cfc364f876ce0c", "parents": [ "461af8b7455db81d2f3962a655500b61ab7cc5c6" ], "author": { "name": "Gaurav Shah", "email": "gauravsh@chromium.org", "time": "Tue Apr 29 23:26:59 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Apr 30 23:37:38 2014" }, "message": "period_scheduler: Fix arguments to logger\n\nA previous cleanup change, incorrectly passes the log message\nas a tag for the logger command.\n\nBUG\u003dchromium:368402\nTEST\u003dRun periodic_scheduler with a small CHECK_DELAY and verify log\n messages in /var/log/messages.\n\nChange-Id: I70478007f39aa83f44c10f28eb50db9cd4e3e4a7\nReviewed-on: https://chromium-review.googlesource.com/197582\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nTested-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nCommit-Queue: Gaurav Shah \u003cgauravsh@chromium.org\u003e\n" }, { "commit": "461af8b7455db81d2f3962a655500b61ab7cc5c6", "tree": "1e0052b2ffbb4b83c1645c3ef84658dac067b45a", "parents": [ "4ef552b3020513906f1a2ec06d690dab61296c4a" ], "author": { "name": "Gaurav Shah", "email": "gauravsh@google.com", "time": "Sat Apr 19 01:22:19 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Apr 24 21:58:10 2014" }, "message": "init: clean up periodic_scheduler script and upstart jobs that use it\n\n- Remove script stanzas from upstart scripts. They are unnecesary.\n- Properly quote variable names where it makes sense.\n- EXTRA! EXTRA! New Curly Braces around variables!\n\nBUG\u003dnone\nTEST\u003dmanual\n\nChange-Id: Iaafb639d6c76b01e94c70f5213a8e432bb1b57dc\nReviewed-on: https://chromium-review.googlesource.com/195689\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nCommit-Queue: Gaurav Shah \u003cgauravsh@chromium.org\u003e\n" }, { "commit": "4ef552b3020513906f1a2ec06d690dab61296c4a", "tree": "20ac5d4cdd5e3503bb90165a6044621d25af97d8", "parents": [ "48a886537231b684b6b97d0a4efd1c9bcf68fd10" ], "author": { "name": "mukesh agrawal", "email": "quiche@chromium.org", "time": "Fri Apr 18 00:46:30 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Apr 18 21:32:42 2014" }, "message": "rsyslog: enable duplicate message suppression\n\nWe\u0027ve had a couple of bugs recently, where processes filled up the\ndisk with log messages. In both cases, a single message was repeated\nover and over, thousands of times per second.\n\nTo resolve this, enable the RepeatedMsgReduction option for rsyslogd.\nThe RepeatedMsgReduction option will suppress consecutive duplicate\nmessages. When a non-duplicate message arrives, rsyslogd will output\na count of the duplicates, and then the new message. Alteratively,\nif no new non-duplicate message within 60 seconds, rsyslogd will\noutput the repeat count at the end of the 60 seconds.\n\nBUG\u003dchromium:363224\nTEST\u003dplatform_LogDupSuppression\n\nChange-Id: I8c6ecf3404d5e5f439155e90a60ae5f83a68a3f7\nReviewed-on: https://chromium-review.googlesource.com/195513\nTested-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: mukesh agrawal \u003cquiche@chromium.org\u003e\n" }, { "commit": "48a886537231b684b6b97d0a4efd1c9bcf68fd10", "tree": "23d97d5fc388401a4154754d4cc8903853732133", "parents": [ "32e65e3ea01247f45783341c04b5b637310a4939" ], "author": { "name": "Gaurav Shah", "email": "gauravsh@google.com", "time": "Wed Apr 09 00:39:01 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Apr 18 09:22:23 2014" }, "message": "chromeos-init: Move cron-lite logic to a common script\n\nMove the cron jobs into separate upstart jobs that use the\nscript to run their tasks periodically.\n\nBUG\u003dchromium:339924\nTEST\u003dmanually run job with lower time durations and verify from logs.\nCQ-DEPEND\u003dCL:195245\n\nChange-Id: Ie1358a3fbdb58cec1c9e60c1ad54703b4ab3c1c2\nReviewed-on: https://chromium-review.googlesource.com/195244\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nCommit-Queue: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nTested-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\n" }, { "commit": "32e65e3ea01247f45783341c04b5b637310a4939", "tree": "3168c89b93bf959ea9c9988ffb1de80266654c86", "parents": [ "f0799a0f767486da074b5b8df95c64752cff98d4" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Thu Apr 10 18:27:35 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Apr 17 16:27:33 2014" }, "message": "Remove crash-reporter specific init scripts\n\nPart of a three CLs commit that moves crash-reporter from platform/init to\nplatform/crash-reporter.\n\nBUG\u003dchromium:346449\nTEST\u003dbuild chromeos-init. The scripts are no longer owned by chromeos-init.\n\nCQ-DEPEND\u003dIcaad09443e60ff8dd4527d426cc11204a65c5f96\nCQ-DEPEND\u003dIb74673a38ef3886b9b23e2f152dd796a3e29855a\n\nChange-Id: I079759d0a096c50600c292cc37d3486b1c44e56a\nReviewed-on: https://chromium-review.googlesource.com/194288\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "f0799a0f767486da074b5b8df95c64752cff98d4", "tree": "60a4e56d475f55ef4f03d6cc712ee765e4ccadc4", "parents": [ "8bf7520c1a5bb9398e537874c0a806a970d34f5a" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue Mar 18 00:18:37 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sat Apr 12 01:49:20 2014" }, "message": "Remove boot-complete from chromeos-init\n\nboot-complete will now be define by the product and should no longer be\ninstalled by chromeos-init. boot-complete.conf will now be installed by the\nvirtual chromeos-bootcomplete.\n\nFor embedded, we no longer need the login-prompt-visible.conf hack so we will\nremove it.\n\nBUG\u003dchromium:190120\nTEST\u003dBuild chromeos-init for daisy and beaglebone.\nDaisy: boot-complete is no longer owned by chromeos-init.\nBeaglebone: boot-complete and login-prompt-visible are no longer owned by\nchromeos-init.\n\nCQ-DEPEND\u003dIc72b0973140fa2783fd385f051f1e9699b7f2eba\n\nChange-Id: I3fdb03e36451ed1febfac430c73c2ed7fef7bf1b\nReviewed-on: https://chromium-review.googlesource.com/191746\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "8bf7520c1a5bb9398e537874c0a806a970d34f5a", "tree": "8b160296db9f59be2828fb0984ed97275011f3f2", "parents": [ "44599a6d3b2d0e9d90a64f0589b3d0f7f82af37a" ], "author": { "name": "Gwendal Grignou", "email": "gwendal@chromium.org", "time": "Mon Apr 07 18:47:04 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Apr 10 00:59:40 2014" }, "message": "Move chromeos-common.sh to /usr/share/misc\n\nBUG\u003dchromium:348619\nCQ-DEPEND\u003dCL:193424,CL:193425,CL:193426,CL:193428,CL:193429,CL:193449,CL:193452,CL:193453,CL:193454,CL:193455,CL:193470,CL:193471,CL:193473,CL:193474,CL:193490\nTEST\u003dRan Powerwash, check it is not stuck\nTEST\u003dRecheck whole set of changes, include install via factory install.\n\nChange-Id: Iee84663fd62ba10c6c801fe04b53d78e626a6998\nReviewed-on: https://chromium-review.googlesource.com/193451\nReviewed-by: Gwendal Grignou \u003cgwendal@chromium.org\u003e\nTested-by: Gwendal Grignou \u003cgwendal@chromium.org\u003e\nCommit-Queue: Puthikorn Voravootivat \u003cputhik@chromium.org\u003e\n" }, { "commit": "44599a6d3b2d0e9d90a64f0589b3d0f7f82af37a", "tree": "e5df514ee45cf465753f90e2d9b53527275fa65c", "parents": [ "2c58cc636aea95432e072d58436dce9e0594105e" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Fri Mar 21 18:59:33 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Apr 09 02:25:23 2014" }, "message": "Remove tty2.conf from platform/init\n\ntty2.conf will now be installed by chromeos-base/tty.\nAlso extract the logic that disable screen diming of tty2 for test image\nwith factory toolkit into test-init/factory.conf\n\nBUG\u003dchromium:354667\nTEST\u003dBuild chromeos-init. tty2.conf is now owned by chromeos-base/tty\nTEST\u003dBuild a factory test image for daisy. Boot. Change to VT2.\nWait more than 10 minutes -\u003e screen is not blank.\ncat /sys/module/kernel/parametes/consoleblank returns 0\n\nCQ-DEPEND\u003dIf31617bc97f17ae6d5ef5adbef353759857347d5\n\nChange-Id: Ieaa26aeb1503d12087f12c7eead20fd036850db0\nReviewed-on: https://chromium-review.googlesource.com/191906\nReviewed-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "2c58cc636aea95432e072d58436dce9e0594105e", "tree": "12f9afb6e958abce71049c836382dcd9cb72f6f2", "parents": [ "691f22dccd0d43ae659bdfa33c6c8a1528f7e8e9" ], "author": { "name": "Paul Stewart", "email": "pstew@chromium.org", "time": "Thu Apr 03 23:45:07 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Apr 04 23:59:57 2014" }, "message": "Add RU to strict regdomains\n\nAdd RU due to bandwidth requirements and strict prohibition\non some 5GHz frequencies.\n\nBUG\u003dchrome-os-partner:26747\nTEST\u003dBoot system with \"region\u003dru\" in the VPD, then do\n\"iw reg get\"\n\nChange-Id: Ia76c1887ac1641bcbf3fdc09596358674abeda93\nReviewed-on: https://chromium-review.googlesource.com/193155\nReviewed-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nCommit-Queue: Paul Stewart \u003cpstew@chromium.org\u003e\nTested-by: Paul Stewart \u003cpstew@chromium.org\u003e\n" }, { "commit": "691f22dccd0d43ae659bdfa33c6c8a1528f7e8e9", "tree": "b4182c2b2dbef7295f3d727e1bb33bbb0d828c1c", "parents": [ "48fafcdded6e8b306f4704c377005756689840e2" ], "author": { "name": "Stéphane Marchesin", "email": "marcheu@chromium.org", "time": "Mon Mar 31 20:10:49 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Apr 01 00:47:46 2014" }, "message": "Call ply-image with the new monitor flag\n\nWe want the splash screen to configure the monitors, so let\u0027s add the\nflag which triggers that.\n\nBUG\u003dchrome-os-partner:26957\nTEST\u003dboot Chrome OS on link\nCQ-DEPEND\u003dCL:192392\n\nChange-Id: I5344d52c28448dd435ebce9e0d50b23f059481c5\nReviewed-on: https://chromium-review.googlesource.com/192393\nReviewed-by: Daniel Erat \u003cderat@chromium.org\u003e\nCommit-Queue: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\nTested-by: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\n" }, { "commit": "48fafcdded6e8b306f4704c377005756689840e2", "tree": "1c5151915fff7d15994b870db8a68d78f4439e97", "parents": [ "47bd5897e8647769c6f5f49ecaaa9f805e1f7a3a" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue Mar 25 00:04:32 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Mar 28 23:10:40 2014" }, "message": "Remove swap initialization scripts.\n\nPart of a two CLs change that moves swap.conf into its own package,\nchromeos-base/swap-init.\nAs swap-exp.conf is not used anymore, remove it in this CL too.\n\nBUG\u003dchromium:353797\nTEST\u003dBuild chromeos-init. swap.conf and swap-exp.conf are not owned by\nchromeos-init anymore.\nCQ-DEPEND\u003dCL:191458\n\nChange-Id: I8168f29eaa0f0a4d63cdb31b2a9c98671e2fc658\nReviewed-on: https://chromium-review.googlesource.com/191479\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "47bd5897e8647769c6f5f49ecaaa9f805e1f7a3a", "tree": "413cd98954221575f684e7ba0bf1cbd525e7f387", "parents": [ "8289f617d05ebe88c1e6ee894925c1c9ac353b20" ], "author": { "name": "Hung-Te Lin", "email": "hungte@chromium.org", "time": "Thu Mar 27 03:15:28 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Mar 27 18:46:54 2014" }, "message": "chromeos-boot-alert: Support new initial_locale VPD data format.\n\nThe initial_locale in VPD has changed from single locale to a list separated by\n\u0027,\u0027, and the first value is the \"primary\" default one for display.\n\nBUG\u003dchromium:325389\nTEST\u003dchromeos-boot-alert leave_dev # see correct locale displayed\n\nChange-Id: I2e485bba2e8c042130fcacbde5cb55bad0adf316\nReviewed-on: https://chromium-review.googlesource.com/191789\nTested-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nReviewed-by: Jon Salz \u003cjsalz@chromium.org\u003e\nCommit-Queue: Hung-Te Lin \u003chungte@chromium.org\u003e\n" }, { "commit": "8289f617d05ebe88c1e6ee894925c1c9ac353b20", "tree": "d62a6a4d56c2646cfddaf89caa2adbdd12c4c54c", "parents": [ "12293dfb81ed434fe363a1585d2fb947c66f3192" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Thu Mar 13 17:45:28 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Mar 26 05:29:14 2014" }, "message": "Extract bootstat\u0027s boot-complete marker into its job\n\nWe want boot-complete.conf to be a boot marker.\nThe task to report the boot-complete mark to bootstat should be in its\nown job.\n\nBUG\u003dchromium:190120\nTEST\u003dBuild chromeos-init in beaglebone and daisy. Both init scripts get\ninstalled.\nTEST\u003dDeployed on a Chromebook. and check:\n* report-boot-complete is ran and record the boot time\n* boot-complete is started\n* system-services is started\nTEST\u003dTrybot run on daisy, mario, link, duck.\n\nCQ-DEPEND\u003dI7e1b8d166fc06cb9c955ebb70a7dcc8c5cf3d933\n\nChange-Id: I13b3e4f4cbb2c2f97e1f634c8a469d527a828b23\nReviewed-on: https://chromium-review.googlesource.com/189911\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "12293dfb81ed434fe363a1585d2fb947c66f3192", "tree": "9e9c7b31bccb0dc588f3fad0b442299257bca48c", "parents": [ "3588243751b8b2a999f4deb707fcbff3918ff25d" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue Mar 18 18:47:57 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sun Mar 23 00:11:03 2014" }, "message": "Remove hotkey-access.conf from platform/init\n\nPart of a two CLs change that moves hotkey-access.conf into\nthe chromeos-auth-config package.\n\nBUG\u003dchromium:353657\nTEST\u003dBuild chromeos-init. hotkey-access.conf is no longer owned by\nchromeos-init.\n\nCQ-DEPEND\u003dI4d0c4f7343ae94a0bc669ab2aeb210c0461e1900\n\nChange-Id: I0aec5ca870e3279b20dcc34ceb4d76a1b59a5b2b\nReviewed-on: https://chromium-review.googlesource.com/190557\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "3588243751b8b2a999f4deb707fcbff3918ff25d", "tree": "c275652033436dec6057aeb9aa467e6e4d9f063f", "parents": [ "3dc182e1ba83da9cd23dcc01cd0470ac9d0eff78" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Thu Feb 27 23:11:32 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sat Mar 22 10:45:09 2014" }, "message": "Remove vpd-log.conf\n\nPart of a three CL change that moves vpd-log.conf out of chromeos-init and into\nvpd and simplifies vpd\u0027s use.\nVpd-log.conf will now run before boot-services so we dont need to dump the log\nin chromeos_startup\n\nBUG\u003dchromium:347789\nTEST\u003dbuild chromeos-init. vpd-log.conf is not part of chromeos-init\nTEST\u003dtrybot on amd64, daisy, x86, duck\nTEST\u003ddeploy to a chromebook. check that the script ran and wrote no errors to\n/var/log/messages\n\nCQ-DEPEND\u003dI3f853fc8b237644b21c87bff38417061fb8e4cc3\nCQ-DEPEND\u003dI9a004114fc6eefa260f4378a2ad45926de501c5e\n\nChange-Id: Idd14204194d12a83c3368f14b1beb44070210763\nReviewed-on: https://chromium-review.googlesource.com/188328\nReviewed-by: Jorge Lucangeli Obes \u003cjorgelo@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "3dc182e1ba83da9cd23dcc01cd0470ac9d0eff78", "tree": "734581448a550114e4a30ada3ef0ee47cfa961f7", "parents": [ "93e9c265556f087446d2373ff7592c0bc684d2a0" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Mon Mar 17 21:05:48 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sat Mar 22 06:23:52 2014" }, "message": "Remove trousers\u0027 init scripts\n\nPart of a three CLs change that moves trousers\u0027 init scripts from platform/init\nto platform/trousers.\n\nBUG\u003dchromium:351868\nTEST\u003dBuild chromeos-init. The scripts are no longer owned by chromeos-init.\n\nCQ-DEPEND\u003dIf83d13a55bc8695c9480d876dab2a03648ed29e0\nCQ-DEPEND\u003dI7c5c6b6c82ec0a8395a8ba2564b95f434116efab\n\nChange-Id: I72d477634d3349ea02f9360693e764604d76f47d\nReviewed-on: https://chromium-review.googlesource.com/190366\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "93e9c265556f087446d2373ff7592c0bc684d2a0", "tree": "b2039770c9bd883fa74f0634adece52d582e0e9d", "parents": [ "229b0273e0336dd3a7cd23474dc14befe9b930bc" ], "author": { "name": "Paul Stewart", "email": "pstew@chromium.org", "time": "Wed Mar 19 22:28:21 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Mar 21 23:58:28 2014" }, "message": "Make setup of regulatory domain more reliable\n\nInitially when regulatory_domain.conf was created, we worked\naround a startup issue by calling \"iw reg set\" twice. It\nturns out that this was a race condition between wireless\ndriver startup and setting of the regulatory domain. Add a\nretry loop to the regulatory setup script so that we wait\nfor a reasonable amount of time for the wireless LAN driver\nto initialize before setting the regulatory domain.\n\nBUG\u003dchromium:353773\nTEST\u003dOn a system where the wireless driver takes a while to load,\nbut for which a strict regdomain is configured, test the output of\nboth \"iw reg get\", and \"iw list\" to make sure that the appropriate\nchannels are disabled.\n\nChange-Id: I987d441c929a0f47366c410a9c2a449509f0dc59\nReviewed-on: https://chromium-review.googlesource.com/190761\nReviewed-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nTested-by: Paul Stewart \u003cpstew@chromium.org\u003e\nCommit-Queue: Paul Stewart \u003cpstew@chromium.org\u003e\n" }, { "commit": "229b0273e0336dd3a7cd23474dc14befe9b930bc", "tree": "2243fcad07674eba596c2dadbca8f4de242ba890", "parents": [ "19ab1f9bce8da2a782e852dc9b6c096f8b673ae3" ], "author": { "name": "Paul Stewart", "email": "pstew@chromium.org", "time": "Tue Mar 18 22:33:21 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Mar 21 23:58:25 2014" }, "message": "Set US as a strict regdomain\n\nGoing forward, it is impractical for many radio vendors to support\nchannel 12 and 13 to FCC regulations. As such, we should treat\nthe \"US\" regdomain as a strict regdomain so as to prohibit passive\nscanning on these channels.\n\nReferences:\nhttp://transition.fcc.gov/bureaus/oet/ea/presentations/files/oct13/70-Software-Configurations-and-DFS-issues-.pdf\nhttp://www.hctamerica.com/blog-radio_9.html\n\nBUG\u003dchromium:353773\nTEST\u003dBoot system with no default networks (so it doesn\u0027t associate\nat boot) with \"region\u003dus\" in the VPD and do \"iw reg get\". It should\nreport \"US\" as the regdomain.\n\nChange-Id: I5e82df6adad1f8334d649afb8b4da9298449e949\nReviewed-on: https://chromium-review.googlesource.com/190760\nReviewed-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nTested-by: Paul Stewart \u003cpstew@chromium.org\u003e\nCommit-Queue: Paul Stewart \u003cpstew@chromium.org\u003e\n" }, { "commit": "19ab1f9bce8da2a782e852dc9b6c096f8b673ae3", "tree": "1fed7b709acbef6ad64b4491b1f3ccfa7811c783", "parents": [ "de4f5a3fd4f85d78d6aba970f6d54f9fb8ccac40" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Wed Mar 19 00:26:29 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Mar 21 21:36:30 2014" }, "message": "Remove alsa-default.conf\n\nalsa-default.conf is no longer used.\n\nBUG\u003dchromium:353810\nTEST\u003dBuild chromeos-init. alsa-default.conf is no longer owned by chromeos-init.\n\nChange-Id: Ie5ec78777795b5198b8865195cb3cf5f533887fb\nReviewed-on: https://chromium-review.googlesource.com/190619\nReviewed-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "de4f5a3fd4f85d78d6aba970f6d54f9fb8ccac40", "tree": "b92e5a820ffa375839fe2d05232ed6ec21525cfd", "parents": [ "d5f54d625581591cd7c4d2e42c7577410aa7cec0" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Fri Mar 21 18:04:49 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Mar 21 21:35:53 2014" }, "message": "Remove unused getty wrapper\n\nembedded-init/agetty was used when we were experimenting with busybox and is not\nbeing installed anywhere now.\n\nBUG\u003dchromium:354670\nTEST\u003dtrybot on link, mario, daisy, duck\n\nChange-Id: I5f97727401f1d757ec425473aad8f06b23d371ca\nReviewed-on: https://chromium-review.googlesource.com/191101\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "d5f54d625581591cd7c4d2e42c7577410aa7cec0", "tree": "e970f322a7b57e3dee624af0d070bd3a9c9feb4f", "parents": [ "50f6c4f75992e2e9f6ec9799af42de3680c199f3" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue Mar 18 01:48:03 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Mar 21 21:35:13 2014" }, "message": "Remove issue from platform/init\n\nPart of a two CLs change that moves /etc/issue from chromeos-init to\nchromeos-base.\n\nBUG\u003dchromium:353608\nTEST\u003dBuild chromeos-init. /etc/issue is no longer owned by chromeos-init.\n\nCQ-DEPEND\u003dIbe6a2cc942912d4329ce663ae1eb45c4e2999472\n\nChange-Id: I35924e813a069cddbadc4da69939101f593b7dba\nReviewed-on: https://chromium-review.googlesource.com/190512\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "50f6c4f75992e2e9f6ec9799af42de3680c199f3", "tree": "2537d9ba400057b6ef2ba9aaa94738185ef1baea", "parents": [ "fa73336d4d784f7c85fa13e604a5a0b3ec4709f1" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Wed Mar 12 01:17:27 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Mar 18 20:35:00 2014" }, "message": "Remove avahi.conf from platform/init\n\nPart of a two CLs change that moves avahi.conf into its own ebuild package.\n\nBUG\u003dchromium:351388\nTEST\u003dBuild chromeos-init. avahi.conf is no longer owned by chromeos-init.\n\nCQ-DEPEND\u003dId9af41df2623590e5c7d4019b127a64075844dd6\n\nChange-Id: I97b23de92292513da6bf0cdaf74f70025b17ed98\nReviewed-on: https://chromium-review.googlesource.com/189647\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "fa73336d4d784f7c85fa13e604a5a0b3ec4709f1", "tree": "ed9f8c6613b3f2efabfae6094fa7c163e38ba1ff", "parents": [ "2b5128253e424a26b2e5b81d25ce85a5f2d2094e" ], "author": { "name": "Alexander Alekseev", "email": "alemate@chromium.org", "time": "Thu Mar 13 15:57:51 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Mar 18 14:48:40 2014" }, "message": "Fix Platform.DiskUsage.NumUserHomeDirectories UMA metrics.\n\nBUG\u003dchromium:352122\nTEST\u003dnone\nChange-Id: I9510ef03ee0b03d014592a8ac356e012e97beeac\nReviewed-on: https://chromium-review.googlesource.com/189830\nReviewed-by: Alexander Alekseev \u003calemate@chromium.org\u003e\nTested-by: Alexander Alekseev \u003calemate@chromium.org\u003e\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Alexander Alekseev \u003calemate@chromium.org\u003e\n" }, { "commit": "2b5128253e424a26b2e5b81d25ce85a5f2d2094e", "tree": "be4ff2b3b2d54d29de74009a0d3ec3b3cc792d0e", "parents": [ "04bb97f1a0d1a8750c66cfc38951fa537647ddc7" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue Mar 18 00:39:10 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Mar 18 09:41:57 2014" }, "message": "Remove install-completed.conf from platform/init\n\nPart of a three CLs change that moves install-completed.conf out of\nchromeos-init.\n\nBUG\u003dchromium:353400\nTEST\u003dBuild chromeos-init. install-completed.conf is no longer owned by\nchromeos-init.\n\nCQ-DEPEND\u003dIe874f191fc2ececd244469e4e6423a0d1c64df71\nCQ-DEPEND\u003dI0db3c3a932e654c95d77bbd1822b4fd011c0879f\n\nChange-Id: I5fd371c2bd9a20cd95a79b02525f88c179a1efd0\nReviewed-on: https://chromium-review.googlesource.com/190432\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "04bb97f1a0d1a8750c66cfc38951fa537647ddc7", "tree": "de3a6088eb492a49d58ccac7837935f1c41cc27e", "parents": [ "242ec6c704b497472b1ec5bcdc651d6bbe2d9aae" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Wed Feb 26 16:24:06 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Mar 18 00:02:47 2014" }, "message": "Remove clear-framebuffer and send-uptime-metrics\n\nPart of a three CLs commit that moves login_manager related init scripts from\nplatform/init to platform/login_manager\n\nBUG\u003dchromium:350600\nTEST\u003dbuild chromeos-init. clear-framebuffer.conf and send-uptime-metrics.conf\nare not owned by chromeos-init anymore.\n\nCQ-DEPEND\u003dI51f598cdbcbc997fe23ffb10279be366828f70bf\nCQ-DEPEND\u003dI4c80e0ed3a08a0bad2294c3262176a68ed9571c4\n\nChange-Id: Ifc98b2b7afc8cfa76cd6033ac2e543803c848654\nReviewed-on: https://chromium-review.googlesource.com/189511\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: Chris Masone \u003ccmasone@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "242ec6c704b497472b1ec5bcdc651d6bbe2d9aae", "tree": "1807229d6a83eefd2e8ed91d05ac40dd6c35266c", "parents": [ "4a75164f5187e4fec51364a83da69e0803b39397" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Wed Mar 05 22:35:35 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Mar 14 19:41:48 2014" }, "message": "Remove cryptohome specific init script from platform/init\n\nPart of a three CLs change that moves cryptohome\u0027s init script from\nplatform/init to platform/cryptohome.\n\nBUG\u003dchromium:349606\nTEST\u003dBuild chromeos-init. The four init scripts are no longer owned by\nchromeos-init.\n\nCQ-DEPEND\u003dI727f9e8b448f36ab9a892145e9183ad96f750d60\nCQ-DEPEND\u003dIfe62bf40604dbe8d1c64977e9b8fd5bbcf25478e\n\nChange-Id: I3fa27db26df90e2125cc098a90db27dd9c868321\nReviewed-on: https://chromium-review.googlesource.com/189722\nReviewed-by: Darren Krahn \u003cdkrahn@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "4a75164f5187e4fec51364a83da69e0803b39397", "tree": "4d5b8c09a8d58d1aecf1690614e3b9778e090ce3", "parents": [ "7716c35854d0623a88dbe40af7e15c163c6cdc20" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Wed Mar 12 22:17:58 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Mar 14 01:23:22 2014" }, "message": "Remove ureadahead.conf\n\nPart of a two CLs change that moves ureadahead\u0027s init script out of\nplatform/init.\n\nBUG\u003dchromium:351954\nTEST\u003dBuild chromeos-init. ureadahead is not longer owned by chromeo-init\n\nCQ-DEPEND\u003dIe6086d509a7f0691b7de87c2dde9cad948150cd0\n\nChange-Id: I54676bcb722104fa301823189b3ced29b63d257d\nReviewed-on: https://chromium-review.googlesource.com/189841\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "7716c35854d0623a88dbe40af7e15c163c6cdc20", "tree": "0e2e57afced7c241c1962eda2319f6278b9f801f", "parents": [ "032830e3af3c63232b1dff8b28df0fe434e0a5c4" ], "author": { "name": "mukesh agrawal", "email": "quiche@chromium.org", "time": "Fri Mar 07 22:32:10 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Mar 12 22:31:52 2014" }, "message": "init: remove ixchariot-endpoint\n\nWe\u0027re no longer using this software, so remove its upstart job.\n\nBUG\u003dchrome-os-partner:26616\nTEST\u003dnone\n\nChange-Id: Idb124f609eecd47d470e1d093a55b296d599506b\nReviewed-on: https://chromium-review.googlesource.com/189237\nTested-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nReviewed-by: Paul Stewart \u003cpstew@chromium.org\u003e\nCommit-Queue: mukesh agrawal \u003cquiche@chromium.org\u003e\n" }, { "commit": "032830e3af3c63232b1dff8b28df0fe434e0a5c4", "tree": "1986b0561ed424e8ee8c829784db8acfc23db6e0", "parents": [ "a945dfdbea0f78683cea6faaecd91976abd4ad45" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Sat Feb 22 01:23:39 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Mar 12 22:30:42 2014" }, "message": "Remove lightup and remove power_manager\u0027s init scripts\n\nPart of a three CLs change that moves power_manager\u0027s init scripts into\npower_manager.\nAs lightup_screen is no longer needed. We remove it it this commit too.\n\nBUG\u003dchromium:348214\nTEST\u003dbuild chromeos-init. powerd.conf and report-power-metrics are no longer\nowned by chromeos-init\n\nCQ-DEPEND\u003dI94ccaf741f770975bb890f9d23a020c8220f9b09\nCQ-DEPEND\u003dIcfdc9269084a9eb3dd431a0908a71149388cb07d\nCQ-DEPEND\u003dIb3cd2f548de5133a6145b0b8b02eb209d79d51c3\n\nChange-Id: I3539df39571de175df72e2f2e0f1ad9d42c0b9c5\nReviewed-on: https://chromium-review.googlesource.com/189053\nReviewed-by: Daniel Erat \u003cderat@chromium.org\u003e\nReviewed-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "a945dfdbea0f78683cea6faaecd91976abd4ad45", "tree": "6227568acf4655e845ca0a24ae1abf8931798aaf", "parents": [ "bec0d436bb3f51d47999264db9e8df0df7ac4625" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Mon Mar 10 16:56:32 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Mar 12 05:09:56 2014" }, "message": "Remove openssh-server\u0027s init script\n\nWe are moving openssh out of platform/init. openssh-server.conf now lives in\nopenssh-server-init\u0027s package.\n\nBUG\u003dchromium:350607\nTEST\u003dbuild chromeos-init and openssh-server-init. openssh-server.conf is still\ninstalled and owned by openssh-server-init.\n\nCQ-DEPEND\u003dIe8e7d30ef13d74ff35c52f81b9d7008e39c70764\n\nChange-Id: I8d279bfdec8cac026653e15eb38bec369447abbf\nReviewed-on: https://chromium-review.googlesource.com/189491\nReviewed-by: Simran Basi \u003csbasi@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "bec0d436bb3f51d47999264db9e8df0df7ac4625", "tree": "5410e0d4e0ff76c5b18e7fe533ee54011252e424", "parents": [ "f71e15c2b91fc40bb533e4b492cfc90a8b720e20" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Fri Feb 28 21:13:10 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sat Mar 08 03:51:56 2014" }, "message": "Remove laptop-mode init scripts\n\nPart of a two CLs change that moves laptop-mode\u0027s init scripts from\nchromeos-init to laptop-mode-tools.\n\nBUG\u003dchromium:348144\nTEST\u003dtrybot on amd64, x86, daisy, duck\nTEST\u003dbuild chromeos-init. laptop-mode-* scripts are no longer owned by\nchromeos-init.\n\nCQ-DEPEND\u003dI9e7ca01f4c909af1a0b37a578c8eee8be6e9e23e\n\nChange-Id: I0583b7bec8b93eb79f530fcc3739d11b72ee6368\nReviewed-on: https://chromium-review.googlesource.com/189068\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "f71e15c2b91fc40bb533e4b492cfc90a8b720e20", "tree": "763408ae283db88f65a097a8610a3f1e84582fd4", "parents": [ "b73e97e842f5ff70e0e6d53d6008e187fe24cdbb" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue Mar 04 00:36:16 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Mar 06 23:13:39 2014" }, "message": "Remove cromo.conf\n\nPart of a three CLs commit that moves cromo.conf from chromeos-init to cromo.\n\nBUG\u003dchromium:348835\nTEST\u003dbuild chromeos-init. cromo.conf is not installed by chromeos-init.\nCQ-DEPEND\u003dId68de5c365337097c90e50c9ae189ad0d4dbecb4\nCQ-DEPEND\u003dI3b30ccd198e4d189cc4e4d251b34e58cb584437a\n\nChange-Id: I59b37f46fa81dda8991b0aa74bf0dc83af062622\nReviewed-on: https://chromium-review.googlesource.com/188688\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "b73e97e842f5ff70e0e6d53d6008e187fe24cdbb", "tree": "62570eaa6ed05a7e88bd610da7233b387d06d74e", "parents": [ "6c18168e62c619bf3db697f9014809ad3afc7fbe" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Tue Mar 04 18:05:55 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Mar 06 04:11:13 2014" }, "message": "Remove update-engine\u0027s init script\n\nPart of a three CL commit that moves update-engine.conf from platform/init\nto platform/update_engine\n\nBUG\u003dchromium:348801\nTEST\u003dbuild chromeos-init. update-engine.conf is not owned by chromeos-init.\n\nCQ-DEPEND\u003dI54889e0b34c9adcf12ac7ba12c2409c49642827f\nCQ-DEPEND\u003dId23e80659dfde2d48b21417245fae1326ef4cdf7\n\nChange-Id: Idafd4fcd84ed4b785c11b96b879aa739cd9d2ade\nReviewed-on: https://chromium-review.googlesource.com/188772\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "6c18168e62c619bf3db697f9014809ad3afc7fbe", "tree": "79dd51e84f429eaba17c531123292f3dec6b1785", "parents": [ "75753961d55461e080178cb3d13f5bd067cf1c20" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Wed Feb 26 01:13:46 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Mar 04 21:36:02 2014" }, "message": "Break send-boot-metrics into simpler init scripts\n\nThis script does too many unrelated things.\nThis CL splits the scripts so that we can later move them into different\npackages.\n\nBUG\u003dchromium:346932\nTEST\u003dtrybot run on x86, amd64 and duck\nTEST\u003dcros deploy chromeos-init. check that the scripts are installed,\nrun and that no error appear on /var/log/messages\n\nChange-Id: Ia81feaa4d984480f7e6e73222489f995f6e22713\nReviewed-on: https://chromium-review.googlesource.com/188116\nReviewed-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "75753961d55461e080178cb3d13f5bd067cf1c20", "tree": "c8ef2a80e73dd624c43a0fa8ba2997297f1a0177", "parents": [ "b8f114ea666d9726ef671b4b1096d311056a4c50" ], "author": { "name": "Chris Sosa", "email": "sosa@chromium.org", "time": "Mon Mar 03 18:27:22 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Mon Mar 03 21:58:11 2014" }, "message": "Only clean CRX cache with stateful disk usage is gt 25%.\n\nBUG\u003dchromium:345335\nTEST\u003dRan script on device with lt 25 and gt 25 stateful disk usage.\n\nChange-Id: I1ac399f870a3dba6e206c2336c2e9b2eea20aacd\nReviewed-on: https://chromium-review.googlesource.com/188526\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nCommit-Queue: Chris Sosa \u003csosa@chromium.org\u003e\nTested-by: Chris Sosa \u003csosa@chromium.org\u003e\n" }, { "commit": "b8f114ea666d9726ef671b4b1096d311056a4c50", "tree": "bb0f89031b5a36fbc16ba0ecd11639ef7d5f248b", "parents": [ "06b53cb91d1034813bf2adf87d7d867ecbf5e245" ], "author": { "name": "mukesh agrawal", "email": "quiche@chromium.org", "time": "Sat Feb 22 01:34:27 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Feb 28 22:45:30 2014" }, "message": "rsyslog: keep tlsdated messages out of /var/log/messages\n\ntlsdate and tlsdated are chatty. While we previously filtered tlsdate\nmessages, to keep them out of /var/log/messages, we did not similarly\nfilter tlsdated messages. Fix this.\n\nBUG\u003dchromium:343333\nTEST\u003dmanual (see below)\n\nManual test\n-----------\ndut# logger -t tlsdated \"from tlsdated\"\ndut# logger -t tlsdate \"from tlsdate\"\ndut# grep -lr \u0027from tlsdate\u0027 /var/log\n -\u003e only matching file is /var/log/tlsdate.log\n\nChange-Id: Icbc45ba04a46f2976c3cf451a715832ff48364b7\nReviewed-on: https://chromium-review.googlesource.com/187486\nTested-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nReviewed-by: Will Drewry \u003cwad@chromium.org\u003e\nCommit-Queue: mukesh agrawal \u003cquiche@chromium.org\u003e\n" }, { "commit": "06b53cb91d1034813bf2adf87d7d867ecbf5e245", "tree": "c3e665d7d89da918d75d2fdc13c47ba2d59a02ac", "parents": [ "7a9d77575952826620075be2428591dad0269cbe" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Thu Feb 27 19:36:40 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Feb 28 19:12:00 2014" }, "message": "Remove wpa_supplicant.conf\n\nwpasupplicant.conf is now installed by wpa_supplicant\u0027s ebuild along\nwith the binaries\n\nBUG\u003dchromium:347702\nTEST\u003dwpasupplicant.conf is now installed by wpa_supplicant\nTEST\u003ddeploy on a Chromebook. Check that wpa_supplicant is launched\nand that no errors appear on /var/log/messages\nTEST\u003dtrybots on x86, amd64, daisy, duck\n\nCQ-DEPEND\u003dI4f1c6331dfe4cbb586a8253bd1c3fb77c37249ba\nCQ-DEPEND\u003dIe4be6851e59c49eb69887bdc22f5b8e81522135b\n\nChange-Id: Ib3566172426bb39193cafcaa52d5c0df037f80fc\nReviewed-on: https://chromium-review.googlesource.com/188255\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "7a9d77575952826620075be2428591dad0269cbe", "tree": "e1d21a552d9e5d7acc046be5cefec80e1d68bde4", "parents": [ "79cc8a01fa39f934e2353a15b82003151a919fdd" ], "author": { "name": "Chris Sosa", "email": "sosa@chromium.org", "time": "Thu Feb 20 21:54:15 2014" }, "committer": { "name": "Chris Sosa", "email": "sosa@chromium.org", "time": "Fri Feb 28 18:12:07 2014" }, "message": "Clean up the CRX cache if it still exists as part of cleanup-logs.\n\nchromeos-cleanup-logs is run once a day which is schedule by\ncron-life.conf. For the CRX cache, we\u0027ve decided to move cleanup from the\nimport to our scrubber to assist with some factory flow cases.\n\nBUG\u003dchromium:345335\nTEST\u003dRunning on device.\n\nChange-Id: I68c7b49bf61d93e8e3e8b2e4fe945fc2b77ab714\nReviewed-on: https://chromium-review.googlesource.com/187313\nTested-by: Chris Sosa \u003csosa@chromium.org\u003e\nReviewed-by: Don Garrett \u003cdgarrett@chromium.org\u003e\n" }, { "commit": "79cc8a01fa39f934e2353a15b82003151a919fdd", "tree": "195a96d431f0e8c5027977a2681989fb3056e0c1", "parents": [ "4ffec61dfff72c8b37852408990a649af79373a5" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Wed Feb 26 22:41:37 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Feb 27 05:38:16 2014" }, "message": "Remove tlsdated.conf from chromeos-init\n\nPart of a three CL commit to move tlsdates.conf from chromeos-init\nto net-misc/tlsdate.\n\nBUG\u003dchromium:347336\nTEST\u003dtrybot on x86, amd64 and duck\nTEST\u003dbuild an image without tlsdate. Check that tlsdated.conf is not installed\nTEST\u003ddeploy chromeos-init and tlsdate. Reboot. Check that tlsdate is running\nand there is not error in /var/log/messages\nCQ-DEPEND\u003dIb8029ab9642b9b852cbd3e34de5c89b649305309\nCQ-DEPEND\u003dI0578395a84d5e0a12fdc3dc272985bd28e466a14\n\nChange-Id: Ieaea926653b6baf7f35ce6777c200c8a3698c69a\nReviewed-on: https://chromium-review.googlesource.com/188114\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "4ffec61dfff72c8b37852408990a649af79373a5", "tree": "afe21e220911bc1b1521bd1b0547bd3418a8493a", "parents": [ "572cac4736767bd5897889ed27ea89b1015b2098" ], "author": { "name": "Luigi Semenzato", "email": "semenzato@chromium.org", "time": "Wed Feb 26 18:09:30 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Feb 27 00:50:05 2014" }, "message": "init: zram: compute zram size based on architecture\n\nThis sets the zram size to 150% of RAM for non-ARM\nand 100% os RAM for ARM. Previously it was set to\n150% of RAM unless overridden in a platform overlay.\nNow the override is ignored. (This doesn\u0027t change\nzram allocation for any existing platform.)\n\nBUG\u003dchrome-os-partner:24488\nTEST\u003dmanually on x86 and on pretend-ARM\nBRANCH\u003dnone\n\nChange-Id: I060d25ba4fb6237c8fc949839abc2833c0e053a2\nReviewed-on: https://chromium-review.googlesource.com/188044\nReviewed-by: Doug Anderson \u003cdianders@chromium.org\u003e\nTested-by: Doug Anderson \u003cdianders@chromium.org\u003e\nCommit-Queue: Doug Anderson \u003cdianders@chromium.org\u003e\n" }, { "commit": "572cac4736767bd5897889ed27ea89b1015b2098", "tree": "d07d7ebf22fb30a93fd3dfd9efd1ced27bd1f4f2", "parents": [ "40fd5ac5b25a368377f18957f907f5564c225d08" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Fri Feb 21 17:27:18 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Feb 27 00:49:45 2014" }, "message": "Moving metrics init scripts out of init\n\nRemoving metrics related scripts\n\nBUG\u003dchromium:346444\nTEST\u003dcbuildbot on x86-alex-paladin\nCQ-DEPEND\u003dCL:187470, CL:187456\n\nChange-Id: I657370ce9eabcb40e26de9973e96174fceb0f3c4\nReviewed-on: https://chromium-review.googlesource.com/187455\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "40fd5ac5b25a368377f18957f907f5564c225d08", "tree": "0b510c8b7ef67ede9e9411bce5dbe273399e0c30", "parents": [ "f0297d3c4fe19eaf2328a67711aa794105ddd412" ], "author": { "name": "Bertrand SIMONNET", "email": "bsimonnet@chromium.org", "time": "Fri Feb 21 21:18:51 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Feb 26 08:31:29 2014" }, "message": "Remove the init scripts for shill from platform/init\n\nThis change is part of a three CLs change that moves all\nshill specific init scripts from init to the shill package.\n\nBUG\u003dchromium:346443\nTEST\u003dtrybot on amd64-generic-paladin x86-alex-paladin daisy_spring-paladin\nCQ-DEPEND\u003dCL:187496, CL:187487\n\nChange-Id: I9a2efb5ba47cdc6314e5f2f89f9f9cae4b35a4e5\nReviewed-on: https://chromium-review.googlesource.com/187523\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: Paul Stewart \u003cpstew@chromium.org\u003e\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nTested-by: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\nCommit-Queue: Bertrand Simonnet \u003cbsimonnet@chromium.org\u003e\n" }, { "commit": "f0297d3c4fe19eaf2328a67711aa794105ddd412", "tree": "5857604b4b7bd540586c6c17005c586ed4e787ff", "parents": [ "d4ad120743fc81906d9da1321d00a9915f62e2b4" ], "author": { "name": "Darren Krahn", "email": "dkrahn@chromium.org", "time": "Wed Feb 19 03:21:40 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Feb 19 22:40:33 2014" }, "message": "Add a more detailed metric for the TPM dictionary attack counter.\n\nThis metric will track all values of the counter including the expected\nzero value.\n\nBUG\u003dchromium:341358\nTEST\u003dmanual\n\nChange-Id: If464415de5d3bd9d66a976ecce7bbecdef689534\nReviewed-on: https://chromium-review.googlesource.com/187036\nReviewed-by: Luigi Semenzato \u003csemenzato@chromium.org\u003e\nCommit-Queue: Darren Krahn \u003cdkrahn@chromium.org\u003e\nTested-by: Darren Krahn \u003cdkrahn@chromium.org\u003e\n" }, { "commit": "d4ad120743fc81906d9da1321d00a9915f62e2b4", "tree": "31aac4e85c2f566381490e2903e15ac8f0c918bc", "parents": [ "17b3a32bbfab60e7a999ba687d7c6eaa554e1fc8" ], "author": { "name": "Darren Krahn", "email": "dkrahn@chromium.org", "time": "Sat Feb 08 00:53:55 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Feb 12 00:40:53 2014" }, "message": "Added a check for non-zero dictionary attack counters.\n\nOn every boot we attempt to measure the TPM dictionary attack counter.\nWe send a metric and log if the counter was successfully measured and if\nit is non-zero.\n\nBUG\u003dchromium:341358\nTEST\u003dmanual\n\nChange-Id: I27bc21a9a581f9062e3b253b666da63ca7a7f948\nReviewed-on: https://chromium-review.googlesource.com/185494\nReviewed-by: Darren Krahn \u003cdkrahn@chromium.org\u003e\nTested-by: Darren Krahn \u003cdkrahn@chromium.org\u003e\nCommit-Queue: Darren Krahn \u003cdkrahn@chromium.org\u003e\n" }, { "commit": "17b3a32bbfab60e7a999ba687d7c6eaa554e1fc8", "tree": "2c3a4de551bd6e1c03847adb24ced29b6b98e44e", "parents": [ "3c70691f365b39c6ba4229adede50c118639e13f" ], "author": { "name": "Prathmesh Prabhu", "email": "pprabhu@chromium.org", "time": "Thu Jan 30 01:17:12 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Mon Feb 03 23:32:09 2014" }, "message": "[syslog] Direct logs with \u0027pseudomodem\u0027 process tag to net.log\n\npseudomodem is a modemmanager emulator used by tests. The logs should be handled\nin the same way as modemmanager logs.\n\nBUG\u003dchromium:328257\nTEST\u003dRun pseudomodem and check that logs appear in net.log\n\nChange-Id: I34702250be6f98f0d66a87d97ef0d632a10db5d3\nReviewed-on: https://chromium-review.googlesource.com/184720\nReviewed-by: Ben Chan \u003cbenchan@chromium.org\u003e\nCommit-Queue: Prathmesh Prabhu \u003cpprabhu@chromium.org\u003e\nTested-by: Prathmesh Prabhu \u003cpprabhu@chromium.org\u003e\n" }, { "commit": "3c70691f365b39c6ba4229adede50c118639e13f", "tree": "5bba1caa47104151518f043de3cabfa83cb63dd2", "parents": [ "d8a69ad9f441fd6e939b4a2fa2be33432c510c4d" ], "author": { "name": "Kees Cook", "email": "keescook@chromium.org", "time": "Fri Jan 24 20:48:18 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Jan 28 19:59:24 2014" }, "message": "chromeos_startup: do not follow mount symlinks\n\nWe must not follow symlinks when performing mounts in writable\ndirectories.\n\nBUG\u003dchromium:337667\nTEST\u003drambi build and boot, manual testing\n\nChange-Id: I518e92670fae3e6b4b05b4be477bec731b3b1bdb\nSigned-off-by: Kees Cook \u003ckeescook@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/183801\nReviewed-by: Jorge Lucangeli Obes \u003cjorgelo@chromium.org\u003e\nReviewed-by: Will Drewry \u003cwad@chromium.org\u003e\nCommit-Queue: Jorge Lucangeli Obes \u003cjorgelo@chromium.org\u003e\n" }, { "commit": "d8a69ad9f441fd6e939b4a2fa2be33432c510c4d", "tree": "0a6ebe0b91194626de47802a4adc6083b617fb6c", "parents": [ "3a432160f3de937777a1b1ab0f781d49a490094b" ], "author": { "name": "Don Garrett", "email": "dgarrett@google.com", "time": "Fri Jan 17 18:49:14 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Jan 23 16:17:39 2014" }, "message": "Fix directory for preserving pre-installed CRX files.\n\nBUG\u003dchrome-os-partner:25069\nTEST\u003dNone yet.\n\nChange-Id: I9c22d7d7f7dd401f9b793e6f3b8d4fdf5ba94ee1\nReviewed-on: https://chromium-review.googlesource.com/182939\nReviewed-by: Jon Salz \u003cjsalz@chromium.org\u003e\nTested-by: Don Garrett \u003cdgarrett@chromium.org\u003e\nCommit-Queue: Jon Salz \u003cjsalz@chromium.org\u003e\n" }, { "commit": "3a432160f3de937777a1b1ab0f781d49a490094b", "tree": "d3dc377b4a6c082ed9f4c751be0ad1304b1a492d", "parents": [ "c2c4f84e59a27a21a62e6262a47bb476847330ce" ], "author": { "name": "Simran Basi", "email": "sbasi@chromium.org", "time": "Mon Jan 13 23:57:36 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Jan 23 01:51:02 2014" }, "message": "chromeos-init: Remove firewall upstart jobs from platform/init\n\nPreviously we had only 1 set of firewall upstart jobs. This change\ndeletes them from platform/init and requires the chromeos-firewall-init\nebuild to install it from its files directory instead.\n\nAlso in order to remove a circular dependency on chromeos-init and\nchromeos-firewall-init we now have the jobs that depended on stopped\nip[6]tables.conf depend on started boot-services and expect the\nip[6]tables.conf to be tasks depending on starting shill.\n\nBUG\u003dchromium:327153\nTEST\u003dBuilt --board\u003dstumpy and --board\u003dstumpy_moblab and ensured\nthe correct upstart jobs were placed in /etc/init\n\nCQ-DEPEND\u003dI955a607f8e3960f126f67b54378215258f60f6d7\nCQ-DEPEND\u003dI433f7bad51148064761d4a813c71cd7c1364a2d6\n\nChange-Id: I6cc020a8c555099aa6697c2077aede3a8043d5e4\nReviewed-on: https://chromium-review.googlesource.com/181503\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Simran Basi \u003csbasi@chromium.org\u003e\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Simran Basi \u003csbasi@chromium.org\u003e\n" }, { "commit": "c2c4f84e59a27a21a62e6262a47bb476847330ce", "tree": "af79abed336732025be63e085964f761b2bcf4ec", "parents": [ "582fdbad14957e3fc0f09bec6b728628d3b3abf6" ], "author": { "name": "Alex Deymo", "email": "deymo@chromium.org", "time": "Tue Jan 21 22:56:57 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Jan 22 04:52:39 2014" }, "message": "Change factory-splash job to start on starting boot-services.\n\nWhen performing a powerwash on a device, the startup job launches the\nchromeos-boot-alert script which emits the boot-alert-request event.\nThis event is emitted in a blocking way, which will make the caller\n(startup) to wait until the boot-splash job is stopped.\n\nOn the other hand, CL:181323 included a new factory-splash job on\ntest images only, that depends on both boot-splash and startup\n\"stopping\" event. This means that this new job will block the\nemitted event until startup is stopped, creating a deadlock.\n\nThis patch makes the factory-splash.conf job to start on\nboot-services starting instead, which breaks the deadlock.\n\nBUG\u003dchromium:336500\nTEST\u003dplatform_Powerwash works on a test image and the factory splash\nscreen is shown when /usr/local/factory/enabled is present.\n\nChange-Id: Iafd1848bf78acb5fc770a3f1aca3cf7ce1c48154\nReviewed-on: https://chromium-review.googlesource.com/183363\nTested-by: Alex Deymo \u003cdeymo@chromium.org\u003e\nReviewed-by: Vic Yang \u003cvictoryang@chromium.org\u003e\nCommit-Queue: Alex Deymo \u003cdeymo@chromium.org\u003e\n" }, { "commit": "582fdbad14957e3fc0f09bec6b728628d3b3abf6", "tree": "ff3f08de2ac7e52c28556a4d7484b3fc861bcf43", "parents": [ "14dc7d9a860e7dffc18151434c0111482e109cfd" ], "author": { "name": "Paul Stewart", "email": "pstew@chromium.org", "time": "Thu Jan 16 22:21:07 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Jan 17 01:16:39 2014" }, "message": "Add device blacklist argument to shill startup\n\nAdd an upstart environment variable to the shill startup that\nspecifies what devices should be blacklisted.\n\nBUG\u003dchromium:327155\nTEST\u003d\"restart shill BLACKLISTED_DEVICES\u003dwlan0\" and ensure that\n\"--device-black-list\u003dwlan0\" appears on the shill command line.\n\nChange-Id: I97fd140587ae5c0a7e2e0b9ef9f321d2e862b9b3\nReviewed-on: https://chromium-review.googlesource.com/182856\nReviewed-by: Jay Kim \u003cyongjaek@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Paul Stewart \u003cpstew@chromium.org\u003e\nTested-by: Paul Stewart \u003cpstew@chromium.org\u003e\n" }, { "commit": "14dc7d9a860e7dffc18151434c0111482e109cfd", "tree": "13ecf11776475d4565a9207981b050ae540f8f4a", "parents": [ "a2dcd733c988d4abd547554efd068dde706019d2" ], "author": { "name": "Vic (Chun-Ju) Yang", "email": "victoryang@chromium.org", "time": "Thu Jan 02 06:35:24 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Jan 10 20:40:09 2014" }, "message": "Overlay factory test logo onto boot splash for factory testing\n\nWhen we are in factory test mode, overlay factory test logo after boot\nsplash is displayed. This makes it easier for user to know what image is\ncurrently in use.\n\nBUG\u003dchrome-os-partner:24798\nTEST\u003dIn factory test mode, check factory test logo is displayed. In\nnormal test image, check there is no factory test logo.\n\nChange-Id: Icf51431bf4cebe45b91330d02669ebc66e21b680\nSigned-off-by: Vic (Chun-Ju) Yang \u003cvictoryang@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/181323\n" }, { "commit": "a2dcd733c988d4abd547554efd068dde706019d2", "tree": "ac65e974697e6df98d8af46de18b1bd1d66e73d1", "parents": [ "569cb8aa77a32bec1b5ca28b6456c4935ec47231" ], "author": { "name": "Vic (Chun-Ju) Yang", "email": "victoryang@chromium.org", "time": "Mon Dec 30 06:42:43 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Jan 10 20:40:05 2014" }, "message": "Add inhibit jobs to test image\n\nWe used to modify upstart jobs when building factory test images.\nHowever, as we are merging factory test image and test image, we need to\ninhibit those upstart jobs dynamically. To do so, we are adding\ninhibit-* upstart jobs to stop specified upstart jobs when we are\nrunning factory tests.\n\nThe inhibited jobs can still be started manually by starting inhibit-*\njob with disable_inhibit\u003d1 first.\n\nBUG\u003dchrome-os-partner:24798\nTEST\u003dBoot factory test image and see upstart jobs inhibited.\n\nChange-Id: I3182bd8a5df736175a7c075cebe5401fc07823af\nSigned-off-by: Vic (Chun-Ju) Yang \u003cvictoryang@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/181218\n" }, { "commit": "569cb8aa77a32bec1b5ca28b6456c4935ec47231", "tree": "dd4e2f76c59c45d829d4de4dfb9611c4408ddfa6", "parents": [ "732d22bacb9f6aca57fea2af63714a86cbbd304c" ], "author": { "name": "Vic (Chun-Ju) Yang", "email": "victoryang@chromium.org", "time": "Mon Dec 30 06:38:55 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Jan 10 20:39:58 2014" }, "message": "Add factory related upstart config file to test image\n\nThese upstart jobs were installed by factorytest-init, which is going to\nbe deprecated. We are now installing factory related upstart jobs for\ntest image, but limiting them to start only when factory software\nexists.\n\nBUG\u003dchrome-os-partner:24798\nTEST\u003dBuild factory test image and check factory test starts correctly.\nCQ-DEPEND\u003dCL:181217 CL:181203 CL:182012\n\nChange-Id: Id5bec27dffa69750a97287c38017119e70025cce\nSigned-off-by: Vic (Chun-Ju) Yang \u003cvictoryang@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/181217\n" }, { "commit": "732d22bacb9f6aca57fea2af63714a86cbbd304c", "tree": "d36172a2507d0ea93d0214b4be177fed5406dacd", "parents": [ "48de3806e85a1a4c15dc4ffd0b58c540f9d91eee" ], "author": { "name": "Simran Basi", "email": "sbasi@chromium.org", "time": "Wed Jan 08 21:46:01 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Jan 10 20:39:48 2014" }, "message": "chromeos-init: Move openssh-server.conf\n\nThe dev-init folder previously only contained the upstart job required\nto start the openssh-server. However this job will be utilized by\ncertain base images, such as beaglebone and moblab. Thus specifying it\nas a dev-init only upstart job no longer applies.\n\nTherefore moved the openssh-server upstart job to a new folder to hold\nit.\n\nBUG\u003dchromium:327154\nTEST\u003dBuilt a stumpy_moblab base image and ensure I could ssh in, as well\nas a stumpy dev image and ensured I could still ssh in.\nCQ-DEPEND\u003dI112c88360c423e82ca43a9591d4806c21d137208\nCQ-DEPEND\u003dIdcac38da90ad0983804cd88740dab6cea69c0db8\nCQ-DEPEND\u003dI00eda2f1d043b52fff605aed036f30ef17a8cd6c\n\nChange-Id: Idaf7397b2a1387d71e8d12f94e2efae84d4b200e\nReviewed-on: https://chromium-review.googlesource.com/181974\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Simran Basi \u003csbasi@chromium.org\u003e\nTested-by: Aviv Keshet \u003cakeshet@google.com\u003e\nCommit-Queue: Simran Basi \u003csbasi@chromium.org\u003e\n" }, { "commit": "48de3806e85a1a4c15dc4ffd0b58c540f9d91eee", "tree": "c3f7e2aba805c5f191d907e2134948701fafceb8", "parents": [ "da3deee6cc7041d9dbe1de82c67896ad99de52b3" ], "author": { "name": "Vic (Chun-Ju) Yang", "email": "victoryang@chromium.org", "time": "Mon Dec 30 06:36:34 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Jan 09 05:26:37 2014" }, "message": "Remove use of /root/.factory_test\n\nWe are deprecating the tag file /root/.factory_test. Instead of checking\nfor this tag, let\u0027s check for the following two conditions to determine\nif we are running factory tests:\n - \u0027crossystem debug_build\u0027 is 1\n - /usr/local/factory exists\n\nBUG\u003dchrome-os-partner:24798\nTEST\u003dBuild a factory test image without .factory_test tag. Boot and\ncheck mount-encrypted is using factory mode.\nCQ-DEPEND\u003dCL:181430\n\nChange-Id: Ib2045cb03e3979f3d726b4ca051fd315a8039ab9\nSigned-off-by: Vic (Chun-Ju) Yang \u003cvictoryang@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/181216\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\n" }, { "commit": "da3deee6cc7041d9dbe1de82c67896ad99de52b3", "tree": "6ad0ba53652715c3f2a8a1341ce68ad577f6bb83", "parents": [ "dd1d08b73a038df1e6b7833bdf3f021a7212cca1" ], "author": { "name": "Scott James Remnant", "email": "keybuk@chromium.org", "time": "Mon Jan 06 19:09:40 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Jan 08 18:50:15 2014" }, "message": "dbus: Connect Upstart after starting\n\nUpstart has two communication channels, the private address you can use\nas root, and the public system bus connection where security is provided\nby the bus daemon.\n\nSince Upstart doesn\u0027t know which job starts the D-Bus Daemon, it needs\nto be sent a signal after starting to establish the connection to it.\n\nBUG\u003dNone\nTEST\u003ddbus-send --system --type\u003dmethod_call --print-reply --dest\u003dcom.ubuntu.Upstart /com/ubuntu/Upstart org.freedesktop.DBus.Properties.Get string:com.ubuntu.Upstart0_6 string:version\n\nChange-Id: I61e2d118ac5cf71fba9458253212b87535879842\nReviewed-on: https://chromium-review.googlesource.com/181508\nReviewed-by: Chris Masone \u003ccmasone@chromium.org\u003e\nReviewed-by: Kees Cook \u003ckeescook@chromium.org\u003e\nTested-by: Scott James Remnant \u003ckeybuk@chromium.org\u003e\nCommit-Queue: Chris Masone \u003ccmasone@chromium.org\u003e\n" }, { "commit": "dd1d08b73a038df1e6b7833bdf3f021a7212cca1", "tree": "5044bf4013c6a400d5b1bb300eb2425fc47b30da", "parents": [ "d90366ad246955e163ee8bb9c78faac740c4582b" ], "author": { "name": "Vic (Chun-Ju) Yang", "email": "victoryang@chromium.org", "time": "Mon Dec 30 06:34:07 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Jan 08 15:30:22 2014" }, "message": "Show boot splash for factory test\n\nWe are currently using a slightly different boot splash implemented in\nfactory repo. To make code simpler and also pave the way for merging\nfactory test image and test image, let\u0027s show the same boot splash for\nfactory test.\n\nBUG\u003dchrome-os-partner:24798\nTEST\u003dBoot factory test image and see splash screen\n\nChange-Id: I5d15a93418fb40af5c9ee7e335a1dd191b38f0b9\nSigned-off-by: Vic (Chun-Ju) Yang \u003cvictoryang@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/181215\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\n" }, { "commit": "d90366ad246955e163ee8bb9c78faac740c4582b", "tree": "895d22c40a108c007397164c20aea246fff8519f", "parents": [ "7486afbd82d6a7cd78bc4010114a0de182d2f623" ], "author": { "name": "Simran Basi", "email": "sbasi@chromium.org", "time": "Fri Jan 03 02:06:51 2014" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Jan 07 04:52:05 2014" }, "message": "Move startup_utils.sh\n\nMoved the two copies of startup_utils.sh to folders that better\nrepresent the differences: encrypted_stateful \u0026 unencrypted_stateful.\n\nBUG\u003dchromium:242840,chromium:327151\nTEST\u003dBuild image verified correct startup_utils.sh script was installed\non the image.\n\nCQ-DEPEND\u003dI0b260ec1a519ef437bf60ad57c22c8fa4c2296cd\n\nChange-Id: I34656d58f8fc79cc6e009b32607ce92556fddf07\nReviewed-on: https://chromium-review.googlesource.com/181403\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: Kees Cook \u003ckeescook@chromium.org\u003e\nReviewed-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nTested-by: Simran Basi \u003csbasi@chromium.org\u003e\nCommit-Queue: Simran Basi \u003csbasi@chromium.org\u003e\n" }, { "commit": "7486afbd82d6a7cd78bc4010114a0de182d2f623", "tree": "f97bd5aff3826cb053c73260014bbc5ac1e4f555", "parents": [ "f4ba00c9f164d75580bb7de29b11edec50fda44b" ], "author": { "name": "Charlie Mooney", "email": "charliemooney@chromium.org", "time": "Thu Dec 12 23:49:30 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Dec 13 20:19:00 2013" }, "message": "Remove input events from powerd init script\n\nIt used to be that powerd\u0027s init pre-start script would let powerd take\nownership of all the input device\u0027s wakeup sysfs entries. There is a\nlittle race condition in doing it like this, so udev rules have been set\nup to automatically chown the wakeup entries as the devices come up.\nThis CL depends on the CL\u0027s that set that up and just removes the old\nstyle of doing it from the pre-start script.\n\nBUG\u003dchrome-os-partner:24299\nTEST\u003dmanual testing on Lucas\nCQ-DEPEND\u003dIc6b2687a5bcd499e0baefc935117bb928aaaa1ac\n\nChange-Id: I7bb1a1336f2de7bc87b9f52ae4065ea96eabe933\nSigned-off-by: Charlie Mooney \u003ccharliemooney@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/179882\nReviewed-by: Daniel Erat \u003cderat@chromium.org\u003e\n" }, { "commit": "f4ba00c9f164d75580bb7de29b11edec50fda44b", "tree": "76eb3c97af7e6f95facb751e8f4dd110e66f328f", "parents": [ "76f30ddf24fd77e874c617ae4f2e59ff423ab5a5" ], "author": { "name": "Andrew Chew", "email": "achew@nvidia.com", "time": "Fri Dec 06 01:57:49 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Dec 06 19:50:49 2013" }, "message": "Add tegra_dc_ext to the early udev triggers list\n\nThis is needed for new recent builds of NVIDIA\u0027s L4T.\n\nWithout this change, the ui would die on startup, though the ui could start\nif one delayed the ui startup.\n\nBUG\u003dchrome-os-partner:24349\nTEST\u003dWas able to boot T124 norrin to UI.\n\nChange-Id: Ic3153c16bd57a5506074c279c01d979f3fd68125\nSigned-off-by: Andrew Chew \u003cachew@nvidia.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/179002\nReviewed-by: Niranjan Artal \u003cnartal@nvidia.com\u003e\nReviewed-by: Doug Anderson \u003cdianders@chromium.org\u003e\nCommit-Queue: Niranjan Artal \u003cnartal@nvidia.com\u003e\n" }, { "commit": "76f30ddf24fd77e874c617ae4f2e59ff423ab5a5", "tree": "ccd100ce3eab5ef1e211ca9e7771dfc6214cdb63", "parents": [ "8397b6e49a101a2f454a95c4fe16e90edf308503" ], "author": { "name": "J. Richard Barnette", "email": "jrbarnette@chromium.org", "time": "Wed Nov 27 18:28:25 2013" }, "committer": { "name": "Richard Barnette", "email": "jrbarnette@chromium.org", "time": "Wed Nov 27 20:38:19 2013" }, "message": "Preserve the .labmachine flag file after stateful update.\n\nThe .labmachine file is used to enable certain test lab-specfic\nbehaviors. Unfortunately, the file can\u0027t be created if the network\nfails to come up, and one of the .labmachine behaviors is meant to\nrepair a network that doesn\u0027t come up.\n\nThis change ensures that the file is preserved across stateful\nupdates that otherwise would clobber it.\n\nBUG\u003dchromium:320833\nTEST\u003dtouch the .labmachine file, stateful update w/ clobber, reboot\n\nChange-Id: Iaa064312814ff7456333f8292c4fed293d562365\nReviewed-on: https://chromium-review.googlesource.com/178204\nTested-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nReviewed-by: Simran Basi \u003csbasi@chromium.org\u003e\n" }, { "commit": "8397b6e49a101a2f454a95c4fe16e90edf308503", "tree": "95aa0cd5dc1589639f9d85182c6ac3c6aa11314b", "parents": [ "0e9f2f0799031e2a1969405729581362ccad75b4" ], "author": { "name": "Don Garrett", "email": "dgarrett@google.com", "time": "Thu Nov 14 00:10:27 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sun Nov 24 04:40:33 2013" }, "message": "Move archive shutdown timestamp AFTER log preservation.\n\nMy recent change to chromeos_shutdown archived off system logs AFTER the\ntimestamp for \"finished archiving\" timestamp is saved off. This throws off\nmetrics for system restarts in which system logs are preserved by the 10s of\nseconds it takes to copy them.\n\nContents of the preserve metrics dir after a clobber reboot.\n\nls -al /mnt/stateful_partition/unencrypted/preserve/log/metrics\n\ntotal 72\ndrwxr-xr-x 4 chronos chronos 4096 Nov 22 19:56 .\ndrwxrwxr-t 10 root syslog 4096 Nov 22 19:50 ..\n-rw------- 1 root root 8 Nov 22 19:13 Logging.AnyCrashesDaily\n-rw------- 1 root root 8 Nov 22 19:13 Logging.AnyCrashesWeekly\n-rw------- 1 root root 8 Nov 22 19:13 Logging.KernelCrashInterval\n-rw------- 1 root root 8 Nov 22 19:13 Logging.KernelCrashesDaily\n-rw------- 1 root root 8 Nov 22 19:13 Logging.KernelCrashesWeekly\n-rw------- 1 root root 8 Nov 22 19:13 Logging.UncleanShutdownsDaily\n-rw------- 1 root root 8 Nov 22 19:13 Logging.UncleanShutdownsWeekly\n-rw------- 1 root root 8 Nov 22 19:13 Logging.UserCrashInterval\n-rw------- 1 root root 8 Nov 22 19:13 Logging.UserCrashesDaily\n-rw------- 1 root root 8 Nov 22 19:13 Logging.UserCrashesWeekly\ndrwxr-xr-x 2 root root 4096 Nov 22 19:56 before_preserve.20131122195636\n-rw------- 1 root root 8 Nov 22 19:13 daily-usage\ndrwxr-xr-x 2 root root 4096 Nov 22 19:56 shutdown.20131122195636\n-rw-r--r-- 1 root root 24 Nov 22 19:49 shutdown_start\n-rw-r--r-- 1 root root 24 Nov 22 19:49 shutdown_stop\n-rw-rw-rw- 1 root root 3111 Nov 22 19:56 uma-events\n\nBUG\u003dchromium:318988\nTEST\u003dBuild/local push\n\nChange-Id: Idf7fff3d1734de03861541021025d3c04caa3e0b\nReviewed-on: https://chromium-review.googlesource.com/176726\nTested-by: Don Garrett \u003cdgarrett@chromium.org\u003e\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Don Garrett \u003cdgarrett@chromium.org\u003e\n" }, { "commit": "0e9f2f0799031e2a1969405729581362ccad75b4", "tree": "92b2d5a90e5dcc095c5b717283f2d1e1f6533835", "parents": [ "a6d30dbfe6d4e7173961fcc0f9abcf8701c89ce9" ], "author": { "name": "Luigi Semenzato", "email": "semenzato@chromium.org", "time": "Mon Jul 29 19:09:05 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Nov 20 20:40:06 2013" }, "message": "Send UMA stat for EC TPSRESET.\n\nSend it only once, and record the send by creating a file in /home/chronos.\n\nBRANCH\u003dspring\nBUG\u003dchrome-os-partner:21107\nTEST\u003don Spring, type \"pmu reset\" on the EC console,\nchech that the /home/chronos/.ec.tpsreset file is created and the UMA\nstat has been incremented.\n\nChange-Id: Ic58b7a8387170a4ba6e13dd369ef2cb2b9d7347a\nReviewed-on: https://chromium-review.googlesource.com/63613\nReviewed-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nCommit-Queue: Vincent Palatin \u003cvpalatin@chromium.org\u003e\n" }, { "commit": "a6d30dbfe6d4e7173961fcc0f9abcf8701c89ce9", "tree": "97e539a3ab56800c77e48f2dce46f527b8d2d2c1", "parents": [ "82d3d8de75c9b35ca78a54ca103c5f52c53aa849" ], "author": { "name": "Will Drewry", "email": "wad@chromium.org", "time": "Wed Nov 06 22:59:57 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Nov 08 05:58:52 2013" }, "message": "tlsdated.conf: make sure the permissions are updated\n\n/var/cache/tlsdated/timestamp was 0600 but now it should\nbe 0644. Newly created files are properly permissioned\nbut existing files are not changed and are unreadable by\ntlsdated during startup.\n\nThis change ensures the permissions are correct.\n\nTEST\u003d(in progress) emerge on to x86-alex, chmod 0600 /var/cache/tlsdated/timestamp, initctl restart tlsdated, ls -la /var/cache/tlsdated\nBUG\u003dchromium:315905\n\nChange-Id: Iba513635c7ba7dd23f2645e56852959ab27aeaf4\nReviewed-on: https://chromium-review.googlesource.com/175905\nReviewed-by: Kees Cook \u003ckeescook@chromium.org\u003e\nTested-by: Will Drewry \u003cwad@chromium.org\u003e\nCommit-Queue: Will Drewry \u003cwad@chromium.org\u003e\nReviewed-by: Will Drewry \u003cwad@chromium.org\u003e\n" }, { "commit": "82d3d8de75c9b35ca78a54ca103c5f52c53aa849", "tree": "c4d443120365db4bb01cc8c9def6f8ab8d7b70a2", "parents": [ "13e28a76032f7f3aa2969c4414acb26c7ec990da" ], "author": { "name": "Christopher Wiley", "email": "wiley@chromium.org", "time": "Fri Sep 27 18:45:53 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Nov 05 22:45:13 2013" }, "message": "Expect minijail to fork off wpa_supplicant\n\nThis fixes a bug where calling `restart wpasupplicant` appears to\nnot wait for wpa_supplicant to exit before attempting to start it up\nagain. This is a problem because wpa_supplicant owns a globally unique\nDBus name which it needs to release before restarting.\n\nThe underlying cause of this behavior is that upstart is waiting for\nminijail0 to exit since it is not expecting a fork. When upstart\nattempts to stop the wpasupplicant job, it will send a SIGTERM to the\nprocess group (including wpa_supplicant). Unfortunately, since upstart\nis watching for minijail0\u0027s SIGCHLD, it starts spawning new\nwpa_supplicant instances before wpa_supplicant exits.\n\nIn some cases, this can cause upstart to exhaust its pool of available\nrestarts for wpa_supplicant, since each attempt fails when trying to\nregister the DBus name.\n\nFix this behavior by:\n\n1) Expecting a fork.\n2) Adding a flag to minijail that causes minijail to surrender its init\n responsibilities for the child process.\n\nTEST\u003dCalled `restart wpasupplicant` before and after applying this patch\nwhile watching log files. Before this patch, occationally see\nwpa_supplicant attempting to start up before its predeccesor dies.\nAfter this patch, found that this was not the case.\nBUG\u003dchromium:298341\n\nCQ-DEPEND\u003dCL:175600\nChange-Id: I014f2dd4a86e6a959d76650e4eca15bab69b0c8b\nReviewed-on: https://chromium-review.googlesource.com/175592\nReviewed-by: Christopher Wiley \u003cwiley@chromium.org\u003e\nCommit-Queue: Christopher Wiley \u003cwiley@chromium.org\u003e\nTested-by: Christopher Wiley \u003cwiley@chromium.org\u003e\n" }, { "commit": "13e28a76032f7f3aa2969c4414acb26c7ec990da", "tree": "7b872b8f70781c2804d85845175620aeb01ab041", "parents": [ "0645872e8c52513b5c1be413c82bb391168ebfa4" ], "author": { "name": "J. Richard Barnette", "email": "jrbarnette@chromium.org", "time": "Fri Oct 25 01:02:23 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Nov 01 22:01:30 2013" }, "message": "Simplify the logic for determining stateful wipe.\n\nThe previous logic was contorted in various ways. This simplifies\nand consolidates the tests to eliminate redundancy and unnecessary\nrepetition.\n\nBUG\u003dNone\nTEST\u003dBoot, test power wash\n\nChange-Id: I48c924a0efe0433efe87ae31b492a9855740f741\nReviewed-on: https://chromium-review.googlesource.com/175156\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nTested-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Richard Barnette \u003cjrbarnette@chromium.org\u003e\n" }, { "commit": "0645872e8c52513b5c1be413c82bb391168ebfa4", "tree": "c1dc4625fc9695cdb417ba4efaaae58a546cf25c", "parents": [ "71e575c06497f0d00770878fe5495f1600af89a5" ], "author": { "name": "J. Richard Barnette", "email": "jrbarnette@chromium.org", "time": "Fri Oct 25 00:53:42 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Oct 31 21:56:51 2013" }, "message": "Test `crossystem \"debug_build?0\"` in place of /root/.dev_mode\n\n/root/.dev_mode is a legacy, and headed for obvlivion (Lord willin\u0027\nand the crick don\u0027t rise).\n\nBUG\u003dchromium:310681\nTEST\u003dBoot base and dev images\n\nChange-Id: Id38157c6d27a0fa13f2af697af4f7852172a3a2d\nReviewed-on: https://chromium-review.googlesource.com/175155\nReviewed-by: Will Drewry \u003cwad@chromium.org\u003e\nReviewed-by: Don Garrett \u003cdgarrett@chromium.org\u003e\nTested-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Richard Barnette \u003cjrbarnette@chromium.org\u003e\n" }, { "commit": "71e575c06497f0d00770878fe5495f1600af89a5", "tree": "ed7793341a94322a331a362ffc1e19b5547ff2e5", "parents": [ "0b0c0acd367da3422536f660b6929f835c912ed8" ], "author": { "name": "J. Richard Barnette", "email": "jrbarnette@chromium.org", "time": "Fri Oct 25 00:48:09 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Oct 31 21:56:47 2013" }, "message": "Move stateful update handling to follow stateful wipe.\n\nPreviously, a comment said that the code for handling a stateful\nupdate had to precede the stateful wipe. That comment is no longer\ncorrect. Moreover, if the code moves to follow the stateful wipe,\nit\u0027s more logical (why update when a wipe is pending?), and also it\nenables a number of code simplifications.\n\nThis change contains additional style cleanup, as well.\n\nBUG\u003dNone\nTEST\u003dBoot a system, run stateful update, run power wash\n\nChange-Id: I3fa3e71fdce6e8a89491307c2b6b7f61f2d72dd2\nReviewed-on: https://chromium-review.googlesource.com/175154\nTested-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nCommit-Queue: Richard Barnette \u003cjrbarnette@chromium.org\u003e\n" }, { "commit": "0b0c0acd367da3422536f660b6929f835c912ed8", "tree": "f29422229db9eddd1e3e572a98ae7e207da24244", "parents": [ "20ca429fd7da0f2b1869f78f202204b98ae0a3c8" ], "author": { "name": "Will Drewry", "email": "wad@chromium.org", "time": "Wed Sep 25 21:06:17 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Oct 30 23:10:43 2013" }, "message": "tlsdated: remove date proxy watcher hacks / use new tlsdated\n\nRun the new tlsdated with privilege dropping and in-process\nproxy resolution.\n\nTEST\u003dtest image for both lumpy and daisy, but not tested on x86-32 yet nor autotests\nBUG\u003dchromium:271644\n\nChange-Id: I3b135539441c15f815b787a2140298b6a9d7b5b3\nCQ-DEPEND\u003dCL:169131,CL:173120\nReviewed-on: https://chromium-review.googlesource.com/170650\nTested-by: Will Drewry \u003cwad@chromium.org\u003e\nReviewed-by: Kees Cook \u003ckeescook@chromium.org\u003e\nCommit-Queue: Will Drewry \u003cwad@chromium.org\u003e\nReviewed-by: Will Drewry \u003cwad@chromium.org\u003e\n" }, { "commit": "20ca429fd7da0f2b1869f78f202204b98ae0a3c8", "tree": "4fcd05880948307f0ac8a5a4a78139d1e9709ea0", "parents": [ "c6540733a82eced7db1b4959d8d054207d44f089" ], "author": { "name": "Paul Stewart", "email": "pstew@chromium.org", "time": "Mon Oct 28 14:46:39 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Mon Oct 28 19:09:53 2013" }, "message": "Add Argentina to the list of strict regulatory domains\n\nBUG\u003dchrome-os-partner:23550\nTEST\u003dBoot with \"region\"\u003d\"AR\" in VPD\n\nChange-Id: I641da1f75b21e47d1e283a87206484007799cbcf\nReviewed-on: https://chromium-review.googlesource.com/174880\nReviewed-by: Ajay Gummalla \u003cagummalla@chromium.org\u003e\nCommit-Queue: Paul Stewart \u003cpstew@chromium.org\u003e\nTested-by: Paul Stewart \u003cpstew@chromium.org\u003e\n" }, { "commit": "c6540733a82eced7db1b4959d8d054207d44f089", "tree": "71cfd764e3275fd1d5249e1a21112a68d7d0413f", "parents": [ "b46c747beddc274ff2db02802eb00d7012022713" ], "author": { "name": "Paul Stewart", "email": "pstew@chromium.org", "time": "Tue Oct 15 16:13:31 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Sat Oct 19 07:26:28 2013" }, "message": "Set regulatory domain\n\nFor systems intended for regulatory domains with stricter policies\nthan our world regulatory setting, we must manually set the kernel\nregulatory domain at boot. This new init script tests for any of\nthese domains set in the VPD database and forces the system regulatory\ndomain appropriately.\n\nBUG\u003dchrome-os-partner:20009\nTEST\u003dBoot on a system with:\n \"region\"\u003d\"id\"\nin /var/log/vpd_2.0.txt, disconnect from the network and do\n\"iw reg get\".\n\nChange-Id: I42db34a9192d85f166fea0de0d99bfb818472b31\nReviewed-on: https://chromium-review.googlesource.com/173082\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nReviewed-by: mukesh agrawal \u003cquiche@chromium.org\u003e\nTested-by: Paul Stewart \u003cpstew@chromium.org\u003e\nCommit-Queue: David James \u003cdavidjames@chromium.org\u003e\n" }, { "commit": "b46c747beddc274ff2db02802eb00d7012022713", "tree": "13d12460468b54a6695d0b86e5a8010ec2ff2cb3", "parents": [ "a61fd33bb895a5a751def50693a50c745eed9851" ], "author": { "name": "Don Garrett", "email": "dgarrett@google.com", "time": "Tue Sep 24 22:47:29 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Oct 17 01:45:54 2013" }, "message": "Preserve /mnt/stateful_partition/unencrypted/preserve/lab during lab reimage.\n\nWhen the lab reimages a machine before a test, we want a protected directory\nin which logs can be preserved.\n\ncp /var/log -\u003e /mnt/stateful_partition/unencrypted/preserve/lab on shutdown,\nand preserve it when clobbering stateful.\n\nBUG\u003dchromium:276766\nTEST\u003dManual testing.\n\nChange-Id: I9034260baeae47305a370f5db13222e191271290\nReviewed-on: https://chromium-review.googlesource.com/170518\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nTested-by: Don Garrett \u003cdgarrett@chromium.org\u003e\nCommit-Queue: Don Garrett \u003cdgarrett@chromium.org\u003e\n" }, { "commit": "a61fd33bb895a5a751def50693a50c745eed9851", "tree": "c73dd5879924b90000703feab18ca955e973f116", "parents": [ "913e2752f7d889f07dd46fc5e02290d5fadd1d6c" ], "author": { "name": "Don Garrett", "email": "dgarrett@google.com", "time": "Fri Oct 11 02:16:02 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Mon Oct 14 23:27:44 2013" }, "message": "Only rotate var_overlay and dev_image if we have replacements.\n\nThe directories /mnt/stateful_partition/var_overlay and\n/mnt/stateful_partition/dev_image are normally replaced on a stateful\nupdate. However, if there aren\u0027t new versions available, it will break\nthe lab.\n\nSo... only rotate them out for the new versions if there are new versions\npresent.\n\nBUG\u003dNone\nTEST\u003dNot much (yet)\n\nChange-Id: I3949b09b8e14dc2ca34425b8784caba03516fb5b\nReviewed-on: https://chromium-review.googlesource.com/172696\nTested-by: Don Garrett \u003cdgarrett@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nCommit-Queue: Don Garrett \u003cdgarrett@chromium.org\u003e\n" }, { "commit": "913e2752f7d889f07dd46fc5e02290d5fadd1d6c", "tree": "06b5e2b3dedd9361c804222409b791bc950d208a", "parents": [ "e509a085ceae2dc729f708cfb5b5a740b321f623" ], "author": { "name": "Alex Deymo", "email": "deymo@chromium.org", "time": "Fri Oct 04 18:29:25 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Oct 08 16:19:57 2013" }, "message": "avahi: Run avahi with \"expect daemon\".\n\nWhen avahi is run with --daemonize option it calls fork(2) twice\nto launch the \"avahi running\" process. This requires the upstart\nscript to include \"expect daemon\" option instead of \"expect fork\"\nwhich should be used for daemons that fork only once.\n\nAs a side note, the \"avahi running\" process will fork one more time\nto run a \"chroot helper\" process that is not tracked by upstart, but\nthat will be killed when SIGKILL is sent to the running process.\n\nBUG\u003dchromium:304237\nTEST\u003dRun \"start avahi; stop avahi\" and doesn\u0027t hang.\n\nChange-Id: Idbe0a5de5e63253dc26dd0f30f8477e05cff5d48\nReviewed-on: https://chromium-review.googlesource.com/171883\nTested-by: Alex Deymo \u003cdeymo@chromium.org\u003e\nReviewed-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nTested-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nReviewed-by: Scott James Remnant \u003ckeybuk@chromium.org\u003e\nCommit-Queue: Alex Deymo \u003cdeymo@chromium.org\u003e\n" }, { "commit": "e509a085ceae2dc729f708cfb5b5a740b321f623", "tree": "e02a664904b75c8fb89c792a2d94c7e510b157aa", "parents": [ "d247376dcf4510951800921569ad47ab48d758fb" ], "author": { "name": "Alex Deymo", "email": "deymo@chromium.org", "time": "Fri Oct 04 03:05:30 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Oct 08 16:19:54 2013" }, "message": "avahi: New env variable to pass a different config file.\n\nThis patch adds a new environment variable to the avahi init script\nallowing to use a different avahi-daemon.conf config file. This can\nbe used for testing to stop and restart avahi-daemon restricted to a\nsingle interface, using the \"allow-interfaces\" option in the config\nfile. This option can\u0027t be passed as a command line argument, so a\nnew config file needs to be created and passed to the init script.\n\nBUG\u003dchromium:271847\nTEST\u003dManual test, relaunch avahi listening only on wlan0 but not eth0.\n\nChange-Id: I8e663143972de4af2f32ce87a7d52cdf367985de\nReviewed-on: https://chromium-review.googlesource.com/171815\nReviewed-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nTested-by: Alex Deymo \u003cdeymo@chromium.org\u003e\nCommit-Queue: Alex Deymo \u003cdeymo@chromium.org\u003e\n" }, { "commit": "d247376dcf4510951800921569ad47ab48d758fb", "tree": "739e3c565da009848d3f460bb2869b09d52e83aa", "parents": [ "f9163aadc733b2de8750ea53c733fd20bf2c6c96" ], "author": { "name": "Dominik Behr", "email": "dbehr@chromium.org", "time": "Thu Oct 03 20:58:16 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Oct 04 21:41:14 2013" }, "message": "wait for tty1 and tty2 in udev-trigger-early\n\nX server needs tty1 (and tty2 when run on another VT)\nThis will be required when X server is started as user because\nudev will have to set tty1 and tty2 group permissions before\nX server starts.\n\nBUG\u003dchromium:182119\nTEST\u003dbuild and run Chrome OS\n\nChange-Id: I52880b96daba21fcb9aa2f35920716d7510a4179\nSigned-off-by: Dominik Behr \u003cdbehr@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/171760\nReviewed-by: Stéphane Marchesin \u003cmarcheu@chromium.org\u003e\n" }, { "commit": "f9163aadc733b2de8750ea53c733fd20bf2c6c96", "tree": "b71ed4efda8052acc223efe882cc279361db3fcf", "parents": [ "8d48f5b17a0eb7adcf5abd43d6e026a2ab9b7d32" ], "author": { "name": "Cheng-Yi Chiang", "email": "cychiang@chromium.org", "time": "Thu Mar 28 03:05:26 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Fri Oct 04 06:49:18 2013" }, "message": "Add comments for jobs modified in factory image\n\nAdd comments for jobs modified by chromeos-factoryinstall ebuild and\nfactorytest-init ebuild.\n\nBUG\u003dchrome-os-partner:18436\nTEST\u003dbuild factory image and check those conf files\nChange-Id: I0d27a449adb55cfa5cc002676091755e7c01e3e2\nReviewed-on: https://chromium-review.googlesource.com/46736\nReviewed-by: Daniel Erat \u003cderat@chromium.org\u003e\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Cheng-Yi Chiang \u003ccychiang@chromium.org\u003e\nTested-by: Cheng-Yi Chiang \u003ccychiang@chromium.org\u003e\n" }, { "commit": "8d48f5b17a0eb7adcf5abd43d6e026a2ab9b7d32", "tree": "2c8286332bbc09ea70120e4a2f9b13dd8e3b24ad", "parents": [ "d1c11f1614d6d234191b2fdeb2a7009536f1b170" ], "author": { "name": "Ben Chan", "email": "benchan@chromium.org", "time": "Wed Oct 02 22:36:01 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Thu Oct 03 22:58:56 2013" }, "message": "shill: increase kill timeout to 10s\n\nThis CL increases the kill timeout for the shill job to 10s and makes it\nstop on \u0027starting pre-shutdown\u0027 in order to ensure that shill has enough\ntime to complete its termination clearly. It also adds the bootstat\n\u0027shill-start\u0027 and \u0027shill-stop\u0027 for tracking the startup and shutdown\ntime of shill.\n\nBUG\u003dchromium:303395\nCQ-DEPEND\u003dCL:171657\nTEST\u003dTested the following:\n1. Connect to WiFi and cellular, and then run `stop shill` to terminate\n shill. Verify that shill terminates properly.\n2. Connect to WiFi and cellular, and then run `restart shill` to restart\n shill. Verify that shill terminates and restarts properly.\n3. Modify shill to artificially make it take more than 10s to terminate.\n - Run `stop shill` and verify that upstart kills shill after the 10s\n wait times out.\n - Run `init 6` and verify that chromeos_shutdown is not started\n before shill is terminated, i.e. bootstat_summary shows that\n \u0027shill-stop\u0027 happens before \u0027shutdown-start\u0027.\n\nChange-Id: I2f7dc742f99b7c818af5c26dccd8e9952be57a97\nReviewed-on: https://chromium-review.googlesource.com/171668\nReviewed-by: Richard Barnette \u003cjrbarnette@chromium.org\u003e\nCommit-Queue: Ben Chan \u003cbenchan@chromium.org\u003e\nTested-by: Ben Chan \u003cbenchan@chromium.org\u003e\n" }, { "commit": "d1c11f1614d6d234191b2fdeb2a7009536f1b170", "tree": "913d8b212f7ea79e8e80a7bfabbfa4d02dadaab8", "parents": [ "343abccd6f5be6343f990900c785c10ebedcb33f" ], "author": { "name": "Bernie Thompson", "email": "bhthompson@chromium.org", "time": "Tue Sep 10 23:26:58 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Mon Sep 23 19:28:30 2013" }, "message": "Remove activate_date code from chromeos_startup\n\nThis removes the activate_date calling functionality in\nchromeos_startup, migrating that functionality to a separate\nchromeos-activate-date.ebuild package.\n\nBUG\u003dchromium:289118\nTEST\u003dVerify activate date is still set with corresponding CLs.\nCQ-DEPEND\u003dCL:169650\n\nChange-Id: Id5ba38577767e186aaaff45a07619e6b7dd16e2a\nReviewed-on: https://chromium-review.googlesource.com/168848\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Bernie Thompson \u003cbhthompson@chromium.org\u003e\nCommit-Queue: Bernie Thompson \u003cbhthompson@chromium.org\u003e\n" }, { "commit": "343abccd6f5be6343f990900c785c10ebedcb33f", "tree": "ab2f63edc16cf18ff1b4b45802795716703e24a6", "parents": [ "8909a9a8fba55003c7a59a0d86cf402c8ad97c55" ], "author": { "name": "Liam McLoughlin", "email": "lmcloughlin@chromium.org", "time": "Wed Jul 31 19:59:23 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Wed Sep 11 01:49:57 2013" }, "message": "chromeos_startup: change stateful discovery to work for UBI partitions\n\nA reland of Liam\u0027s original patch https://gerrit.chromium.org/gerrit/63947\nwith a fix to correctly handle the rootdev type for emmc (e.g. /dev/mmcblk0p0).\n\nBUG\u003dchromium:267589\nTEST\u003dtested chromeos-install on daisy\n\nChange-Id: I026e2fed4096b520d54ba216283a35ebebb26bb5\nReviewed-on: https://chromium-review.googlesource.com/168374\nReviewed-by: Liam McLoughlin \u003clmcloughlin@chromium.org\u003e\nTested-by: Gaurav Shah \u003cgauravsh@chromium.org\u003e\nCommit-Queue: Gaurav Shah \u003cgauravsh@chromium.org\u003e\n" }, { "commit": "8909a9a8fba55003c7a59a0d86cf402c8ad97c55", "tree": "be7ca3fde88b0be4e44085d5260bbb2bfe1c09b7", "parents": [ "fa3a10b419efd956f5f0a9ed7eea67917021bbbd" ], "author": { "name": "David Zeuthen", "email": "zeuthen@chromium.org", "time": "Mon Sep 09 22:33:35 2013" }, "committer": { "name": "chrome-internal-fetch", "email": "chrome-internal-fetch@google.com", "time": "Tue Sep 10 22:46:38 2013" }, "message": "Move avahi.conf from test-init sub-directory\n\nNow that we\u0027re pulling in p2p by default, we need to move avahi.conf\nfrom test-init/ to where Upstart job definitions for the regular image\nlives. Without this, starting avahi on a non-test-image will fail.\n\nBUG\u003dchromium:288166\nTEST\u003dTested manually.\n\nChange-Id: Ic2ac7909171683431455aa7f4b6a5192839456b2\nReviewed-on: https://chromium-review.googlesource.com/168647\nReviewed-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nTested-by: David Zeuthen \u003czeuthen@chromium.org\u003e\nCommit-Queue: David Zeuthen \u003czeuthen@chromium.org\u003e\n" } ], "next": "fa3a10b419efd956f5f0a9ed7eea67917021bbbd" }