)]}' { "commit": "5bc8f9c7f9ddda443d5d7214034192c5d9091887", "tree": "80b09c37c107fe6a2a891b9ed002df92ca918e5e", "parents": [ "cc77bb21ebf1e131a6a8333e89709a1b8f195817" ], "author": { "name": "Hung-Te Lin", "email": "hungte@chromium.org", "time": "Fri Sep 21 17:39:46 2018 +0800" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 21 10:11:34 2018 -0700" }, "message": "futility: update: Skip TPM check if tpm_fwver is not valid.\n\nIdeally we should fail if `tpm_fwver` can\u0027t be retrieved, but if an user can\nrun the updater then his system is already up so it\u0027s more likely to be a\nvboot library issue (especially in early proto devices) that the crossystem\nvalues were not reported correctly.\n\nAs a result, it seems more reasonable to skip checking TPM anti-rollback if\n`tpm_fwver` can\u0027t be retrieved.\n\nBRANCH\u003dNone\nBUG\u003db:115764295\nTEST\u003dmake futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility\n\nChange-Id: I7b6bf72531edb334a465c730fe8b3fbafa469b3a\nSigned-off-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/1238099\nReviewed-by: Joel Kitching \u003ckitching@chromium.org\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "81fd8f41d2ad26d249bf8848ce00b30ef2ecd559", "old_mode": 33188, "old_path": "futility/cmd_update.c", "new_id": "c48979181c84944b7cb2bcc473c514b57d9232b0", "new_mode": 33188, "new_path": "futility/cmd_update.c" }, { "type": "modify", "old_id": "b74c7ea9df89c9ec42d9a087fa30020a491ed986", "old_mode": 33261, "old_path": "tests/futility/test_update.sh", "new_id": "8c5e0d569bb26bcdd5ad2172637a9585d1a9bdcf", "new_mode": 33261, "new_path": "tests/futility/test_update.sh" } ] }