New issue
Advanced search Search tips

Issue 913585 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocking:
issue 872407



Sign in to add a comment

Remove references to LASTCHANGE_STRING in chrome_cleaner_unittests

Project Member Reported by joenotcharles@google.com, Dec 10

Issue description

Pointed out by Nico at https://crrev.com/c/1160776/6/chrome/chrome_cleaner/logging/interface_log_service.cc#124, InterfaceLogService hardcodes LASTCHANGE_STRING in the log. LASTCHANGE_STRING is updated on every build, so every time this is built into a unit test, the test binary is different. That means test results can't be cached.

We should pass inject a fixed version in tests, and only use LASTCHANGE_STRING in the final executables.
 
Blocking: 872407
Note that I'm asking to do this not just in the tests, but in the prod code too, for the same reasons. I'm hoping to completely get rid of lastchange.py. LASTCHANGE_STRING is already referenced in only 2 places, both of them in chrome_cleaner.

Hopefully the debug log exchange with your partner is done at some point, or regular prod chrome versions become good enough; at that point presumably we can get rid of the other use too.
Status: Started (was: Assigned)
There are still some other uses of it in the internal repo that hasn't been upstreamed to chrome/chrome_cleaner yet. But I don't think our use of it is important enough to keep the entire mechanism around, so I'll clean those up as I upstream them.
Status: Fixed (was: Started)

Sign in to add a comment