New issue
Advanced search Search tips

Issue 642178 link

Starred by 1 user
Status: Assigned
Owner:
cmt...@chromium.org
Cc:
llozano@chromium.org
cmt...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

object bisector misses some files in the cache

Project Member Reported by laszio@chromium.org, Aug 29 2016 
While the build command line relies on the default output and doesn't specify -o, object bisector misses the output. There are some other cases missed as well, such as the outputs not ending with ".o".

Comment 1 by llozano@chromium.org, Aug 30 2016 

can you give some examples of this? 
I know that object files may not end up in .o but I have not seen this in practice. Are you seeing this in practice?

Comment 2 by llozano@chromium.org, Sep 25 2017

Owner: cmt...@chromium.org
Status: assigned (was: Untriaged)

Comment 3 by zalcorn@chromium.org, Dec 26 2017

Components: Infra

Comment 4 by mmoss@chromium.org, Jan 2 2018

Components: -Infra Infra>Client>ChromeOS
[It appears that a bunch of old cros issues bulk-added the "Infra" component recently, but they should probably be "Infra>Client>ChromeOS".]

Comment 5 by cmt...@chromium.org, Jan 4 2018

Components: -Infra>Client>ChromeOS

Comment 6 by cmt...@chromium.org, Feb 5 2018

Components: Tools>ChromeOS-Toolchain
►

Sign in to add a comment