Consolidate flat and compressed data format into one and use protobuf |
|
Issue description1. Currently, for the sake of debugging and prototyping, two formats (flat and compressed) exist simultaneously in the code base, eventually, the flat one should be removed in favor of compressed one, and a debugging page should be developed in the service so that the compressed format can be properly decompressed and presented on a UI when something goes wrong and needs debugging. 2. Protobuf should instead be used to replace the json, because it's more tractable and format can be documented in the .proto file, which will make it easier to maintain and develop new features in the future.
,
Nov 30
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/4b60d640bb3ca2f70f47fec9d2e8605683014692 commit 4b60d640bb3ca2f70f47fec9d2e8605683014692 Author: Yuke Liao <liaoyuke@chromium.org> Date: Fri Nov 30 05:52:34 2018 [code coverage] Serve per-cl coverage data using the compressed format In https://chromium-review.googlesource.com/c/chromium/tools/build/+/1351694, the flat format is deleted in favor of the compressed format, and this CL makes necessary change at the service side accordingly. Bug: 904469 Change-Id: Ie0bf9969f951c5475c6b8ca188b9e0279071d973 Reviewed-on: https://chromium-review.googlesource.com/c/1355699 Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Reviewed-by: Roberto Carrillo <robertocn@chromium.org> Reviewed-by: Shuotao Gao <stgao@chromium.org> Cr-Commit-Position: refs/heads/master@{#19273} [modify] https://crrev.com/4b60d640bb3ca2f70f47fec9d2e8605683014692/appengine/findit/handlers/code_coverage.py |
|
►
Sign in to add a comment |
|
Comment 1 by bugdroid1@chromium.org
, Nov 30