Run update check if channel is set to be the same #4521
Conversation
yuying-y
force-pushed
the
friction
branch
2 times, most recently
from
4cb2a4b to
755ea37
Compare
Yes, efforts were made to enable unit tests for the updater, but it was not complete because the team was pulled to other issues with higher priorities. Certain unit tests of the updater are enabled: https://source.corp.google.com/h/lbshell-internal/cobalt_src/+/COBALT:chrome/updater/BUILD.gn;l=108 Chrobalt is a a good chance to re-initiate this effort. I'll put it on the workstream doc as a P2. |
yuying-y
dismissed
yell0wd0g’s stale review
Replied as: Yes, efforts were made to enable unit tests for the updater, but it was not complete because the team was pulled to other issues with higher priorities. Certain unit tests of the updater are enabled: source.corp.google.com/h/lbshell-internal/cobalt_src/+/COBALT:chrome/updater/BUILD.gn;l=108 Chrobalt is a a good chance to re-initiate this effort. I'll put it on the workstream doc as a P2.
If SetUpdaterChannel is called with the same channel as the current channel, an update check is forced just like the channel has changed, as long as the channel is not "prod". b/381954273 Change-Id: I042ea07029c56b810f7b4e273fe621d1ab75a9e2
If SetUpdaterChannel is called with the same channel as the current channel, an update check is forced to check for available update on the channel.
b/381954273