3 years, 5 months ago
(2017-06-30 15:36:07 UTC)
#2
As per email discussion. PTAL.
Pierre-Antoine
bcwhite
https://codereview.chromium.org/2966563004/diff/1/components/browser_watcher/stability_report.proto File components/browser_watcher/stability_report.proto (right): https://codereview.chromium.org/2966563004/diff/1/components/browser_watcher/stability_report.proto#newcode191 components/browser_watcher/stability_report.proto:191: map<string, TypedValue> data = 5; Can the name be ...
3 years, 5 months ago
(2017-06-30 16:40:55 UTC)
#3
3 years, 5 months ago
(2017-06-30 20:50:51 UTC)
#6
lgtm
manzagop (departed)
Thanks for the review! I'll wait a bit before submitting this, and possibly bundle more ...
3 years, 5 months ago
(2017-06-30 20:56:47 UTC)
#7
Thanks for the review!
I'll wait a bit before submitting this, and possibly bundle more changes with
it. I wanted to give an early concrete look into what the changes would look
like int terms of the proto.
manzagop (departed)
The CQ bit was checked by manzagop@chromium.org to run a CQ dry run
3 years, 4 months ago
(2017-07-28 19:18:32 UTC)
#8
Description was changed from ========== StabilityReport proto changes for multi-process support The first in a ...
3 years, 4 months ago
(2017-07-28 19:25:50 UTC)
#10
Description was changed from
==========
StabilityReport proto changes for multi-process support
The first in a series of changes to enable multi process support for
collection. Support for recording was introduced in
https://codereview.chromium.org/2680123003
BUG=691595
==========
to
==========
StabilityReport multi-process collection support
Introduces multi-process collection support. Note that multi-processing
recording was introduced in https://codereview.chromium.org/2680123003.
Details:
- processes now have a process type and key-value data.
- modules are now attributed to a process
- now collecting all processes, not just the first
- some key-value data (version information, timestamp) remains at report scope,
to simplify report parsing
BUG=691595
==========
commit-bot: I haz the power
The CQ bit was unchecked by commit-bot@chromium.org
3 years, 4 months ago
(2017-07-28 19:27:38 UTC)
#11
Dry run: Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/512415) win_clang on ...
3 years, 4 months ago
(2017-07-28 19:27:39 UTC)
#12
Dry run: Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/512438)
3 years, 4 months ago
(2017-07-28 20:24:05 UTC)
#17
LGTM (my phone with Authenticator died while away and my rescue codes are locked away ...
3 years, 4 months ago
(2017-07-31 13:55:45 UTC)
#18
LGTM
(my phone with Authenticator died while away and my rescue codes are locked
away in Montreal)
On Fri, Jul 28, 2017 at 3:50 PM, <manzagop@chromium.org> wrote:
> Hi Brian,
> I added the changes to fill the proto. Another look?
> Thanks!
> Pierre
>
> https://codereview.chromium.org/2966563004/
>
--
Brian
bcwhite@google.com
-----------------------------------------------------------------------------------------
*Treat someone as they are and they will remain that way.Treat someone as
they can be and they will become that way.*
--
You received this message because you are subscribed to the Google Groups
"Chromium-reviews" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.
manzagop (departed)
The CQ bit was checked by manzagop@chromium.org to run a CQ dry run
3 years, 4 months ago
(2017-08-04 19:37:53 UTC)
#19
Dry run: Try jobs failed on following builders: cast_shell_linux on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linux/builds/423633)
3 years, 4 months ago
(2017-08-04 20:12:49 UTC)
#22
Dry run: Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presubmit/builds/509480)
3 years, 4 months ago
(2017-08-05 15:19:49 UTC)
#26
Dry run: Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presubmit/builds/509486)
3 years, 4 months ago
(2017-08-05 15:53:39 UTC)
#30
Dry run: Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presubmit/builds/509487)
3 years, 4 months ago
(2017-08-05 16:12:28 UTC)
#34
3 years, 4 months ago
(2017-08-05 16:40:45 UTC)
#37
Patchset #7 (id:120001) has been deleted
manzagop (departed)
Patchset #7 (id:140001) has been deleted
3 years, 4 months ago
(2017-08-05 16:40:56 UTC)
#38
Patchset #7 (id:140001) has been deleted
manzagop (departed)
Patchset #7 (id:160001) has been deleted
3 years, 4 months ago
(2017-08-05 16:41:04 UTC)
#39
Patchset #7 (id:160001) has been deleted
manzagop (departed)
The tests were failing because modules are filtered based on analysis_stamp_ which is set via ...
3 years, 4 months ago
(2017-08-05 16:43:30 UTC)
#40
The tests were failing because modules are filtered based on analysis_stamp_
which is set via GetFirstProcess. I revised the contract to state the
expectation that GetFirstProcess must be called. Another look?
CQ is committing da patch. Bot data: {"patchset_id": 200001, "attempt_start_ts": 1503001576725110, "parent_rev": "25f8e45097c78da4357826bf2b4d3b9f281eef25", "commit_rev": "27f4805ad79030129eaa9f2e5fa5cf1f8b77393f"}
3 years, 4 months ago
(2017-08-17 20:32:15 UTC)
#55
CQ is committing da patch.
Bot data: {"patchset_id": 200001, "attempt_start_ts": 1503001576725110,
"parent_rev": "25f8e45097c78da4357826bf2b4d3b9f281eef25", "commit_rev":
"27f4805ad79030129eaa9f2e5fa5cf1f8b77393f"}
commit-bot: I haz the power
Description was changed from ========== StabilityReport multi-process collection support Introduces multi-process collection support. Note that ...
3 years, 4 months ago
(2017-08-17 20:32:41 UTC)
#56
Message was sent while issue was closed.
Description was changed from
==========
StabilityReport multi-process collection support
Introduces multi-process collection support. Note that multi-processing
recording was introduced in https://codereview.chromium.org/2680123003.
Details:
- processes now have a process type and key-value data.
- modules are now attributed to a process
- now collecting all processes, not just the first
- some key-value data (version information, timestamp) remains at report scope,
to simplify report parsing
BUG=691595
==========
to
==========
StabilityReport multi-process collection support
Introduces multi-process collection support. Note that multi-processing
recording was introduced in https://codereview.chromium.org/2680123003.
Details:
- processes now have a process type and key-value data.
- modules are now attributed to a process
- now collecting all processes, not just the first
- some key-value data (version information, timestamp) remains at report scope,
to simplify report parsing
BUG=691595
Review-Url: https://codereview.chromium.org/2966563004
Cr-Commit-Position: refs/heads/master@{#495306}
Committed:
https://chromium.googlesource.com/chromium/src/+/27f4805ad79030129eaa9f2e5fa5...
==========
commit-bot: I haz the power
Committed patchset #8 (id:200001) as https://chromium.googlesource.com/chromium/src/+/27f4805ad79030129eaa9f2e5fa5cf1f8b77393f
3 years, 4 months ago
(2017-08-17 20:32:43 UTC)
#57
Issue 2966563004: StabilityReport proto changes for multi-process support
(Closed)
Created 3 years, 5 months ago by manzagop (departed)
Modified 3 years, 4 months ago
Reviewers: bcwhite, mmandlis, ivanpe, jwd
Base URL:
Comments: 2