|
|
Created:
3 years, 10 months ago by manzagop (departed) Modified:
3 years, 10 months ago Reviewers:
ivanpe, Sigurður Ásgeirsson, gab, scottmg, Mark Mentovai, sdefresne, Robert Sesek, ananta CC:
chromium-reviews, kalyank, sadrul Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionDouble variations crash key size
This is done by introducing a new crash key size (kHugeSize), which requires raising kLargestValueAllowed.
BUG=689045
Review-Url: https://codereview.chromium.org/2671383002
Cr-Commit-Position: refs/heads/master@{#449064}
Committed: https://chromium.googlesource.com/chromium/src/+/3d62ffd98b8739d42ac7cd34cd4e04be35929f62
Patch Set 1 #
Total comments: 2
Patch Set 2 : 2 more instances of the crash key #Patch Set 3 : Increase kLargestValueAllowed and add a test #Patch Set 4 : Format specifier issue #Patch Set 5 : More signed/unsigned mismatches #Patch Set 6 : Remove an expectation based on chunk size #
Messages
Total messages: 59 (39 generated)
manzagop@chromium.org changed reviewers: + ivanpe@chromium.org, mark@chromium.org, scottmg@chromium.org
Hi, Does this make sense for a short term fix? Thanks, Pierre
The CQ bit was checked by manzagop@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...
scottmg@chromium.org changed reviewers: + ananta@chromium.org
I don't know, but lgtm to try. There's still multiple copies of the keys though. You should change this one too: https://cs.chromium.org/chromium/src/chrome/app/chrome_crash_reporter_client_... (I sort of thought there was 3 copies, but maybe there's only 2 now. Ananta do you know of another copy?)
On 2017/02/06 15:41:23, scottmg wrote: > I don't know, but lgtm to try. There's still multiple copies of the keys though. > You should change this one too: > > https://cs.chromium.org/chromium/src/chrome/app/chrome_crash_reporter_client_... > > (I sort of thought there was 3 copies, but maybe there's only 2 now. Ananta do > you know of another copy?) Ah looks like there's at least also another in src/ios/chrome/browser/crash_report/crash_keys.cc
siggi@chromium.org changed reviewers: + siggi@chromium.org
https://codereview.chromium.org/2671383002/diff/1/components/crash/core/commo... File components/crash/core/common/crash_keys.cc (right): https://codereview.chromium.org/2671383002/diff/1/components/crash/core/commo... components/crash/core/common/crash_keys.cc:96: variations_string.reserve(kHugeSize); is it possible to test that this actually works? There's an associated unittest I haven't looked at...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by manzagop@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: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
I'll write a test. Looks like I'll also need to raise kLargestValueAllowed. https://codereview.chromium.org/2671383002/diff/1/components/crash/core/commo... File components/crash/core/common/crash_keys.cc (right): https://codereview.chromium.org/2671383002/diff/1/components/crash/core/commo... components/crash/core/common/crash_keys.cc:96: variations_string.reserve(kHugeSize); On 2017/02/06 15:44:56, Sigurður Ásgeirsson wrote: > is it possible to test that this actually works? There's an associated unittest > I haven't looked at... Ack.
The CQ bit was checked by manzagop@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...
I added some kind of test. Tell me what you think. Should we add a function like GetCrashKeysForCommandLineSwitches for variations?
The CQ bit was unchecked by commit-bot@chromium.org
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_...)
The CQ bit was checked by manzagop@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: Try jobs failed on following builders: linux_chromium_tsan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...) ios-device-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device-xcode-...) ios-simulator-xcode-clang on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-simulator-xco...) mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by manzagop@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: 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_...)
The CQ bit was checked by manzagop@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...
Description was changed from ========== Double variations crash key size BUG=689045 ========== to ========== Double variations crash key size This is done by introducing a new crash key size (kHugeSize), which requires raising kLargestValueAllowed. BUG=689045 ==========
manzagop@chromium.org changed reviewers: + rsesek@chromium.org
Hi rsesek@, sdefresne@, Could you have an OWNERS' look? rsesek@: chrome\common\crash_keys.cc sdefresne@: ios\chrome\browser\crash_report\crash_keys.cc Thanks! Pierre
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
manzagop@chromium.org changed reviewers: + sdefresne@chromium.org
+sdefresne@ for realz
ios/ lgtm
LGTM
Thanks for the reviews!
The CQ bit was checked by manzagop@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from scottmg@chromium.org Link to the patchset: https://codereview.chromium.org/2671383002/#ps100001 (title: "Remove an expectation based on chunk size")
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
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_presub...)
manzagop@chromium.org changed reviewers: + gab@chromium.org
Hi Gab! Could you have an OWNERS's look at: base/debug/crash_logging.cc Thanks! Pierre-Antoine
On 2017/02/08 00:02:41, manzagop wrote: > Hi Gab! > > Could you have an OWNERS's look at: > base/debug/crash_logging.cc base/ r-s lgtm given scottmg's > > Thanks! > > Pierre-Antoine
On 2017/02/08 16:05:17, gab wrote: > On 2017/02/08 00:02:41, manzagop wrote: > > Hi Gab! > > > > Could you have an OWNERS's look at: > > base/debug/crash_logging.cc > > base/ r-s lgtm given scottmg's > > > > > Thanks! > > > > Pierre-Antoine Thanks!
The CQ bit was checked by manzagop@chromium.org
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
Try jobs failed on following builders: linux_android_rel_ng on master.tryserver.chromium.android (JOB_FAILED, https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)
The CQ bit was checked by manzagop@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch. Bot data: {"patchset_id": 100001, "attempt_start_ts": 1486579258291470, "parent_rev": "07f10c1ad12b4ccb681a27131a353c074431997d", "commit_rev": "3d62ffd98b8739d42ac7cd34cd4e04be35929f62"}
Message was sent while issue was closed.
Description was changed from ========== Double variations crash key size This is done by introducing a new crash key size (kHugeSize), which requires raising kLargestValueAllowed. BUG=689045 ========== to ========== Double variations crash key size This is done by introducing a new crash key size (kHugeSize), which requires raising kLargestValueAllowed. BUG=689045 Review-Url: https://codereview.chromium.org/2671383002 Cr-Commit-Position: refs/heads/master@{#449064} Committed: https://chromium.googlesource.com/chromium/src/+/3d62ffd98b8739d42ac7cd34cd4e... ==========
Message was sent while issue was closed.
Committed patchset #6 (id:100001) as https://chromium.googlesource.com/chromium/src/+/3d62ffd98b8739d42ac7cd34cd4e... |