| Commit-Queue | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
packet->set_os_name(base::SysInfo::OperatingSystemName());Should we use `components::metrics::GetOperatingSystemName` now?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
+chromium-metrics-reviews@ for components/metrics/
packet->set_os_name(base::SysInfo::OperatingSystemName());Should we use `components::metrics::GetOperatingSystemName` now?
No because we can't access components/metrics from here (hence the injection though TracingDelegate)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Reviewer source(s):
rka...@chromium.org is from context(analysis/uma/chrome-metrics.gwsq)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
packet->set_os_name(base::SysInfo::OperatingSystemName());Etienne Pierre-DorayShould we use `components::metrics::GetOperatingSystemName` now?
No because we can't access components/metrics from here (hence the injection though TracingDelegate)
Then we should retain the `#if BUILDFLAG(IS_CHROMEOS)`? IIUC, `base::SysInfo::OperatingSystemName()` returns 'Linux' on Chrome OS, hence the need for a special case.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
packet->set_os_name(base::SysInfo::OperatingSystemName());Etienne Pierre-DorayShould we use `components::metrics::GetOperatingSystemName` now?
Mikhail KhokhlovNo because we can't access components/metrics from here (hence the injection though TracingDelegate)
Then we should retain the `#if BUILDFLAG(IS_CHROMEOS)`? IIUC, `base::SysInfo::OperatingSystemName()` returns 'Linux' on Chrome OS, hence the need for a special case.
This is only for content (e.g. when tracing unittests), while a chrome trace will get its values in components/tracing/common/system_profile_metadata_recorder.cc.
For simplicity I figured it doesn't really matter here (and we could also remove this entirely really).
There is a unittest in content that checks this, but it still relies on ChromeEventBundle, because the os-name from ChromeMetadataPacket doesn't get translated in json.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
packet->set_os_name(base::SysInfo::OperatingSystemName());Etienne Pierre-DorayShould we use `components::metrics::GetOperatingSystemName` now?
Mikhail KhokhlovNo because we can't access components/metrics from here (hence the injection though TracingDelegate)
Etienne Pierre-DorayThen we should retain the `#if BUILDFLAG(IS_CHROMEOS)`? IIUC, `base::SysInfo::OperatingSystemName()` returns 'Linux' on Chrome OS, hence the need for a special case.
This is only for content (e.g. when tracing unittests), while a chrome trace will get its values in components/tracing/common/system_profile_metadata_recorder.cc.
For simplicity I figured it doesn't really matter here (and we could also remove this entirely really).There is a unittest in content that checks this, but it still relies on ChromeEventBundle, because the os-name from ChromeMetadataPacket doesn't get translated in json.
Ah I see. Then I'd vote for removing this, to reduce potential confusion when reading code.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
metrics changes lg
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
+dtapuska@ for content/public
+ntfschr@ for a_w/browser
packet->set_os_name(base::SysInfo::OperatingSystemName());Etienne Pierre-DorayShould we use `components::metrics::GetOperatingSystemName` now?
Mikhail KhokhlovNo because we can't access components/metrics from here (hence the injection though TracingDelegate)
Etienne Pierre-DorayThen we should retain the `#if BUILDFLAG(IS_CHROMEOS)`? IIUC, `base::SysInfo::OperatingSystemName()` returns 'Linux' on Chrome OS, hence the need for a special case.
Mikhail KhokhlovThis is only for content (e.g. when tracing unittests), while a chrome trace will get its values in components/tracing/common/system_profile_metadata_recorder.cc.
For simplicity I figured it doesn't really matter here (and we could also remove this entirely really).There is a unittest in content that checks this, but it still relies on ChromeEventBundle, because the os-name from ChromeMetadataPacket doesn't get translated in json.
Ah I see. Then I'd vote for removing this, to reduce potential confusion when reading code.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[tracing] Fill typed fields in chrome metadata
This CL fills a few typed fields in ChromeMetadataPack that we added in
https://github.com/google/perfetto/commit/fe9b2f932a1cf9d104e6b49ee3acbf173997062c
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |