|
|
Created:
4 years, 4 months ago by norvez Modified:
4 years, 4 months ago CC:
chromium-reviews, dzhioev+watch_chromium.org, achuith+watch_chromium.org, oshima+watch_chromium.org, davemoore+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionNo "Factory error" splashscreen on ChromeOS VMs
If the HWID is invalid (for instance, "unknown") and the firmware ID is non-Chrome ("nonchrome") then assume that we're running in a VM and do not report a factory
error. A warning message is added to the log.
BUG=b:30155895
Committed: https://crrev.com/7077c9c09ee068bfeb7623c8ac58e7a21b7143c8
Cr-Commit-Position: refs/heads/master@{#408870}
Patch Set 1 #Patch Set 2 : No "Factory error" splashscreen on ChromeOS VMs #
Messages
Total messages: 27 (12 generated)
Description was changed from ========== No "Factory error" splashscreen on ChromeOS VMs If the HWID is invalid and the firmware ID is non-Chrome ("unknown") then assume that we're running in a VM and do not report a factory error. A warning message is sent to the log. BUG=b:30155895 ========== to ========== No "Factory error" splashscreen on ChromeOS VMs If the HWID is invalid and the firmware ID is non-Chrome ("unknown") then assume that we're running in a VM and do not report a factory error. A warning message is sent to the log. BUG=b:30155895 ==========
norvez@chromium.org changed reviewers: + hungte@chromium.org, rspangler@chromium.org, vpalatin@chromium.org
Hi, Proposed CL for b/30155895 to avoid HWID check failures in VMs. This is done at the Chrome level rather than crossystem after review at https://chromium-review.googlesource.com/#/c/363330/ PTAL :)
Only few comments to the commit message: > If the HWID is invalid and the firmware ID is non-Chrome ("unknown") If the HWID is empty and the firmware type is non-Chrome ("nonchrome") P.S: I think on VM the HWID is always empty. Do you want to assume it's VM whenever HWID is invalid, or just the case of empty?
On 2016/07/27 15:01:32, Hung-Te wrote: > Only few comments to the commit message: > > > If the HWID is invalid and the firmware ID is non-Chrome ("unknown") > > If the HWID is empty and the firmware type is non-Chrome ("nonchrome") Woops, good catch, thanks! Will fix... > > P.S: I think on VM the HWID is always empty. Do you want to assume it's VM > whenever HWID is invalid, or just the case of empty? I think statistics_provider sets it to "unknown" in that case: https://cs.chromium.org/chromium/src/chromeos/system/statistics_provider.cc?r... I could check for "unknown" but I think there's a bit more work to do at the same time to fully support VMs, see crbug.com/585514 and crbug.com/585515 for example. There's also a bit of cleanup to do to in statistics_provider, we should handle ARM systems that don't have "/sys/class/dmi/id/sys_vendor" and a few other things. All in all I think that should be in a separate CL, and we could add some tests for statistics_provider at the same time. WDYT?
Hmmm. In that case I'd agree to move on with your current version. Meanwhile I'd like to revise my previous feedback to If the HWID is invalid (for instance, "unknown") and the firmware type is non-Chrome
Description was changed from ========== No "Factory error" splashscreen on ChromeOS VMs If the HWID is invalid and the firmware ID is non-Chrome ("unknown") then assume that we're running in a VM and do not report a factory error. A warning message is sent to the log. BUG=b:30155895 ========== to ========== No "Factory error" splashscreen on ChromeOS VMs If the HWID is invalid (for instance, "unknown") and the firmware ID is non-Chrome ("nonchrome") then assume that we're running in a VM and do not report a factory error. A warning message is added to the log. BUG=b:30155895 ==========
On 2016/07/27 15:31:55, Hung-Te wrote: > Hmmm. In that case I'd agree to move on with your current version. > > Meanwhile I'd like to revise my previous feedback to > > If the HWID is invalid (for instance, "unknown") and the firmware type is > non-Chrome Thanks, I've modified the commit message. I'll try to come up with another CL to do the more invasive changes to that would help VM support.
norvez@chromium.org changed reviewers: + dzhioev@chromium.org
Forgot to add an owner to reviewers!
vpalatin@google.com changed reviewers: + vpalatin@google.com
lgtm
lgtm
lgtm
The CQ bit was checked by norvez@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
LGTM
The CQ bit was checked by norvez@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== No "Factory error" splashscreen on ChromeOS VMs If the HWID is invalid (for instance, "unknown") and the firmware ID is non-Chrome ("nonchrome") then assume that we're running in a VM and do not report a factory error. A warning message is added to the log. BUG=b:30155895 ========== to ========== No "Factory error" splashscreen on ChromeOS VMs If the HWID is invalid (for instance, "unknown") and the firmware ID is non-Chrome ("nonchrome") then assume that we're running in a VM and do not report a factory error. A warning message is added to the log. BUG=b:30155895 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== No "Factory error" splashscreen on ChromeOS VMs If the HWID is invalid (for instance, "unknown") and the firmware ID is non-Chrome ("nonchrome") then assume that we're running in a VM and do not report a factory error. A warning message is added to the log. BUG=b:30155895 ========== to ========== No "Factory error" splashscreen on ChromeOS VMs If the HWID is invalid (for instance, "unknown") and the firmware ID is non-Chrome ("nonchrome") then assume that we're running in a VM and do not report a factory error. A warning message is added to the log. BUG=b:30155895 Committed: https://crrev.com/7077c9c09ee068bfeb7623c8ac58e7a21b7143c8 Cr-Commit-Position: refs/heads/master@{#408870} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/7077c9c09ee068bfeb7623c8ac58e7a21b7143c8 Cr-Commit-Position: refs/heads/master@{#408870} |