|
|
Created:
4 years, 4 months ago by scottmg Modified:
4 years, 4 months ago Reviewers:
Sigurður Ásgeirsson, chrisha, robertshield, manzagop (departed), ananta, grt (UTC plus 2) CC:
chromium-reviews Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionFix SyzyASAN build
Removes Kasko for hang watcher from chrome.exe build.
Fixes after changes in https://codereview.chromium.org/2250263002.
BUG=638370, 604923
Committed: https://crrev.com/4879c957ec62ddaa58340afbfdbfa9a4f72c4516
Cr-Commit-Position: refs/heads/master@{#412883}
Patch Set 1 #Patch Set 2 : . #
Total comments: 3
Patch Set 3 : . #
Messages
Total messages: 41 (19 generated)
The CQ bit was checked by scottmg@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 ========== Fix Kasko SyzyASAN build After https://codereview.chromium.org/2250263002. BUG=638370, 604923 ========== to ========== Fix Kasko SyzyASAN build After https://codereview.chromium.org/2250263002. BUG=638370, 604923 ==========
scottmg@chromium.org changed reviewers: + chrisha@chromium.org, siggi@chromium.org
First to stamp wins! I haven't finished a full build (official!) but ninja -C out\Release obj/chrome/chrome_initial/kasko_client.obj builds again now in is_syzyasan=true && is_official_build=true.
lgtm - thanks!
The CQ bit was unchecked by scottmg@chromium.org
The CQ bit was checked by scottmg@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Local build just finished and looks liek this doesn't link still, looking...
The CQ bit was unchecked by scottmg@chromium.org
scottmg@chromium.org changed reviewers: + ananta@chromium.org
scottmg@chromium.org changed reviewers: + manzagop@chromium.org
On 2016/08/17 17:36:12, scottmg wrote: > Local build just finished and looks liek this doesn't link still, looking... Link failure is because of the ChromeWatcherClient code here https://cs.chromium.org/chromium/src/chrome/app/main_dll_loader_win.cc?rcl=0&... (So, nothing to do with SyzyASAN, just to do with having is_syzyasan=true turn on Kasko.) Are we still using that code path? It's been always-off since Jul 19th, when the Crashpad database and client moved to chrome_elf (the database wasn't initialized in chrome.exe, so GetUploadsEnabled() was always false until https://codereview.chromium.org/2250263002 yesterday. It's non-trivial to resurrect it because ChromeCrashReporterClient isn't in chrome.exe any more.
On 2016/08/17 17:53:14, scottmg wrote: > On 2016/08/17 17:36:12, scottmg wrote: > > Local build just finished and looks liek this doesn't link still, looking... > > Link failure is because of the ChromeWatcherClient code here > https://cs.chromium.org/chromium/src/chrome/app/main_dll_loader_win.cc?rcl=0&... > > (So, nothing to do with SyzyASAN, just to do with having is_syzyasan=true turn > on Kasko.) > > Are we still using that code path? It's been always-off since Jul 19th, when the > Crashpad database and client moved to chrome_elf (the database wasn't > initialized in chrome.exe, so GetUploadsEnabled() was always false until > https://codereview.chromium.org/2250263002 yesterday. > > It's non-trivial to resurrect it because ChromeCrashReporterClient isn't in > chrome.exe any more. The browser watcher was using that kasko to send the browser hang reports. BUT, that was removed in https://codereview.chromium.org/2086403002/diff/60001/chrome/chrome_watcher/c... So I don't see this being used.
On 2016/08/17 17:53:14, scottmg wrote: > On 2016/08/17 17:36:12, scottmg wrote: > > Local build just finished and looks liek this doesn't link still, looking... > > Link failure is because of the ChromeWatcherClient code here > https://cs.chromium.org/chromium/src/chrome/app/main_dll_loader_win.cc?rcl=0&... > > (So, nothing to do with SyzyASAN, just to do with having is_syzyasan=true turn > on Kasko.) > > Are we still using that code path? It's been always-off since Jul 19th, when the > Crashpad database and client moved to chrome_elf (the database wasn't > initialized in chrome.exe, so GetUploadsEnabled() was always false until > https://codereview.chromium.org/2250263002 yesterday. > > It's non-trivial to resurrect it because ChromeCrashReporterClient isn't in > chrome.exe any more. The hang watcher is gonsky for now, it's fine to scuttle this - care to do the honors?
On 2016/08/17 20:52:31, Sigurður Ásgeirsson wrote: > On 2016/08/17 17:53:14, scottmg wrote: > > On 2016/08/17 17:36:12, scottmg wrote: > > > Local build just finished and looks liek this doesn't link still, looking... > > > > Link failure is because of the ChromeWatcherClient code here > > > https://cs.chromium.org/chromium/src/chrome/app/main_dll_loader_win.cc?rcl=0&... > > > > (So, nothing to do with SyzyASAN, just to do with having is_syzyasan=true turn > > on Kasko.) > > > > Are we still using that code path? It's been always-off since Jul 19th, when > the > > Crashpad database and client moved to chrome_elf (the database wasn't > > initialized in chrome.exe, so GetUploadsEnabled() was always false until > > https://codereview.chromium.org/2250263002 yesterday. > > > > It's non-trivial to resurrect it because ChromeCrashReporterClient isn't in > > chrome.exe any more. > > The hang watcher is gonsky for now, it's fine to scuttle this - care to do the > honors? Aha, OK, thanks. Updated this CL to remove the watcher code which incidentally will fix the SyzyASAN build too since that's the bit of code that was breaking it.
Description was changed from ========== Fix Kasko SyzyASAN build After https://codereview.chromium.org/2250263002. BUG=638370, 604923 ========== to ========== Fix SyzyASAN build Removes Kasko for hang watcher from chrome.exe build. Fixes after changes in https://codereview.chromium.org/2250263002. BUG=638370, 604923 ==========
scottmg@chromium.org changed reviewers: + robertshield@chromium.org
+robertshield for re-removing the bit in chrome_elf that got added yesterday.
On 2016/08/17 21:00:05, scottmg wrote: > +robertshield for re-removing the bit in chrome_elf that got added yesterday. Removing chrome_elf bit lgtm
The CQ bit was checked by scottmg@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from siggi@chromium.org Link to the patchset: https://codereview.chromium.org/2256723002/#ps20001 (title: ".")
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...)
scottmg@chromium.org changed reviewers: + grt@chromium.org
oops, +grt for chrome/app.
lgtm w/ gypi fix https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn File chrome/BUILD.gn (left): https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn#oldcode144 chrome/BUILD.gn:144: "app/kasko_client.cc", please remove these same two lines from chrome/chrome_exe.gypi
lgtm w/ gypi fix
https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn File chrome/BUILD.gn (left): https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn#oldcode144 chrome/BUILD.gn:144: "app/kasko_client.cc", On 2016/08/18 08:12:43, grt (UTC plus 2) wrote: > please remove these same two lines from chrome/chrome_exe.gypi I was under the impression that we weren't supposed to maintain the gyp build any more. But since this is trivial, I will here.
The CQ bit was checked by scottmg@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from siggi@chromium.org, robertshield@chromium.org, grt@chromium.org Link to the patchset: https://codereview.chromium.org/2256723002/#ps40001 (title: ".")
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 ========== Fix SyzyASAN build Removes Kasko for hang watcher from chrome.exe build. Fixes after changes in https://codereview.chromium.org/2250263002. BUG=638370, 604923 ========== to ========== Fix SyzyASAN build Removes Kasko for hang watcher from chrome.exe build. Fixes after changes in https://codereview.chromium.org/2250263002. BUG=638370, 604923 ==========
Message was sent while issue was closed.
Committed patchset #3 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== Fix SyzyASAN build Removes Kasko for hang watcher from chrome.exe build. Fixes after changes in https://codereview.chromium.org/2250263002. BUG=638370, 604923 ========== to ========== Fix SyzyASAN build Removes Kasko for hang watcher from chrome.exe build. Fixes after changes in https://codereview.chromium.org/2250263002. BUG=638370, 604923 Committed: https://crrev.com/4879c957ec62ddaa58340afbfdbfa9a4f72c4516 Cr-Commit-Position: refs/heads/master@{#412883} ==========
Message was sent while issue was closed.
Patchset 3 (id:??) landed as https://crrev.com/4879c957ec62ddaa58340afbfdbfa9a4f72c4516 Cr-Commit-Position: refs/heads/master@{#412883}
Message was sent while issue was closed.
https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn File chrome/BUILD.gn (left): https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn#oldcode144 chrome/BUILD.gn:144: "app/kasko_client.cc", On 2016/08/18 16:26:58, scottmg wrote: > On 2016/08/18 08:12:43, grt (UTC plus 2) wrote: > > please remove these same two lines from chrome/chrome_exe.gypi > > I was under the impression that we weren't supposed to maintain the gyp build > any more. But since this is trivial, I will here. Thanks. My understanding was that GYP was no longer run by default, but that it was still supported in some sense (see "PSA: GYP is no longer run by default in gclient runhooks" on chromium-dev). I don't expect it to really work, but I find it confusing to have ghosts present in .gyp* files.
Message was sent while issue was closed.
On 2016/08/18 20:38:51, grt (UTC plus 2) wrote: > https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn > File chrome/BUILD.gn (left): > > https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn#oldcode144 > chrome/BUILD.gn:144: "app/kasko_client.cc", > On 2016/08/18 16:26:58, scottmg wrote: > > On 2016/08/18 08:12:43, grt (UTC plus 2) wrote: > > > please remove these same two lines from chrome/chrome_exe.gypi > > > > I was under the impression that we weren't supposed to maintain the gyp build > > any more. But since this is trivial, I will here. > > Thanks. My understanding was that GYP was no longer run by default, but that it > was still supported in some sense (see "PSA: GYP is no longer run by default in > gclient runhooks" on chromium-dev). I don't expect it to really work, but I find > it confusing to have ghosts present in .gyp* files. Yup, it's confusing to have grep show things up, especially since GN still pulls file lists from gypi files in many cases. I was going based on https://groups.google.com/a/chromium.org/d/msg/chromium-dev/NZkPr-CXvQ0/dn1rb... from a couple weeks after "PSA: GYP is no longer run by default in gclient runhooks". So I think we're off now officially the gyp hook. I inquired as to when we might be able to do the great purge, but for some not-too-clear reason, we're keeping the gyp files until M54. Not long though...
Message was sent while issue was closed.
On 2016/08/18 20:44:55, scottmg wrote: > On 2016/08/18 20:38:51, grt (UTC plus 2) wrote: > > https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn > > File chrome/BUILD.gn (left): > > > > > https://codereview.chromium.org/2256723002/diff/20001/chrome/BUILD.gn#oldcode144 > > chrome/BUILD.gn:144: "app/kasko_client.cc", > > On 2016/08/18 16:26:58, scottmg wrote: > > > On 2016/08/18 08:12:43, grt (UTC plus 2) wrote: > > > > please remove these same two lines from chrome/chrome_exe.gypi > > > > > > I was under the impression that we weren't supposed to maintain the gyp > build > > > any more. But since this is trivial, I will here. > > > > Thanks. My understanding was that GYP was no longer run by default, but that > it > > was still supported in some sense (see "PSA: GYP is no longer run by default > in > > gclient runhooks" on chromium-dev). I don't expect it to really work, but I > find > > it confusing to have ghosts present in .gyp* files. > > Yup, it's confusing to have grep show things up, especially since GN still pulls > file lists from gypi files in many cases. > > I was going based on > https://groups.google.com/a/chromium.org/d/msg/chromium-dev/NZkPr-CXvQ0/dn1rb... > from a couple weeks after "PSA: GYP is no longer run by default in > gclient runhooks". So I think we're off now officially the gyp hook. Awesome. Thanks for the link. |