{"push_id":742297631,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"b10e562b4cb5ffd6f02ab891d40644b581ad5d47","before":"dcf890914c7571d3068046b9df1f672e9f45b4d2","commits":[{"sha":"f93db4b827818806ca4cee80e6ec954d7aa40632","author":{"email":"9ec2621bb952ab212238ced42dcfb982244bde16@google.com","name":"Yasuhiro Matsuda"},"message":"Introduce a mechanism to trace boot sequence.\n\nThis CL adds a trigger and a service so that Systrace can be used\nfor tracing events during boot.\npersist.debug.atrace.boottrace property is used for switching on\nand off tracing during boot. /data/misc/boottrace/categories\nfile is used for specifying the categories to be traced.\nThese property and file are rewritten by Systrace when the newly\nadded option --boot is specified.\n\nHere is an example of tracing events of am and wm catetories\nduring boot.\n\n$ external/chromium-trace/systrace am wm --boot\n\nThis command will cause the device to reboot. Once the device has\nbooted up, the trace report is created by hitting Ctrl+C.\n\nAs written in readme.txt, this mechanism relies on persistent\nproperty, so tracing events that are emitted before that are not\nrecorded. This is enough for tracing events after zygote is\nlaunched though.\nThis only works on userdebug or eng build for security reason.\n\nBUG: 21739901\nChange-Id: I03f2963d77a678f47eab5e3e29fc7e91bc9ca3a4","distinct":true,"url":"https://api.github.com/repos/android/platform_system_core/commits/f93db4b827818806ca4cee80e6ec954d7aa40632"},{"sha":"b10e562b4cb5ffd6f02ab891d40644b581ad5d47","author":{"email":"9ec2621bb952ab212238ced42dcfb982244bde16@google.com","name":"Yasuhiro Matsuda"},"message":"Merge \"Introduce a mechanism to trace boot sequence.\"","distinct":true,"url":"https://api.github.com/repos/android/platform_system_core/commits/b10e562b4cb5ffd6f02ab891d40644b581ad5d47"}]}