Code Coverage tools bundle is getting incorrectly unpacked |
||
Issue descriptionJust noticed the the bots are failing to produce new reports because llvm-cov and llvm-profdata files are in /chromium/src/third_party/llvm-build/Release+Asserts/bin/bin/ directory instead of /chromium/src/third_party/llvm-build/Release+Asserts/bin/ <--- single "bin" at the end. I suspect this was introduced in this CL: https://chromium-review.googlesource.com/c/chromium/src/+/1274127/9/tools/code_coverage/update_clang_coverage_tools.py#52
,
Oct 18
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d26f5c50005671c4200120c7d9ca347259c0279d commit d26f5c50005671c4200120c7d9ca347259c0279d Author: Max Moroz <mmoroz@chromium.org> Date: Thu Oct 18 13:49:00 2018 Code Coverage: use correct path to llvm binaries in update_clang_coverage_tools.py. TBR=liaoyuke@chromium.org,robertocn@chromium.org Change-Id: I783b07eacca213f2815f6c0f66bfb77c55b9435f Bug: 896556 Reviewed-on: https://chromium-review.googlesource.com/c/1288689 Reviewed-by: Max Moroz <mmoroz@chromium.org> Commit-Queue: Max Moroz <mmoroz@chromium.org> Cr-Commit-Position: refs/heads/master@{#600748} [modify] https://crrev.com/d26f5c50005671c4200120c7d9ca347259c0279d/tools/code_coverage/update_clang_coverage_tools.py
,
Oct 18
,
Oct 18
Restarted bot -0001 and scheduled restarts for the others with 2 hours interval. |
||
►
Sign in to add a comment |
||
Comment 1 by mmoroz@chromium.org
, Oct 18Status: Started (was: Assigned)