|
|
Created:
3 years, 8 months ago by yhirano Modified:
3 years, 8 months ago CC:
chromium-reviews, tyoshino+watch_chromium.org, loading-reviews_chromium.org, gavinp+loader_chromium.org, blink-reviews, loading-reviews+fetch_chromium.org, kinuko+watch, Nate Chapin Target Ref:
refs/heads/master Project:
chromium Visibility:
Public. |
DescriptionMove |is_static_data| check down in DetermineRevalidationPolicy
This CL moves
if (is_static_data)
return kUse;
section down in DetermineRevalidationPolicy as a preparation to factor out some
|return kReload;| statements.
BUG=652228, 714574
R=hiroshige@chromium.org
Review-Url: https://codereview.chromium.org/2829043002
Cr-Commit-Position: refs/heads/master@{#466931}
Committed: https://chromium.googlesource.com/chromium/src/+/58197789bfafee408d8fc728c0ed2f1da81bbbed
Patch Set 1 #Patch Set 2 : fix #Patch Set 3 : fix #Patch Set 4 : rebase #Messages
Total messages: 35 (25 generated)
The CQ bit was checked by yhirano@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...
Could you explain the intention of this? Is there specific case where we want to return kReload for static data?
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_...)
The CQ bit was checked by yhirano@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 checked by yhirano@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 ========== Give is_static_data a lower priority in DetermineRevalidationPolicy BUG=652228 R=hiroshige@chromium.org, japhet@chromium.org ========== to ========== Move |is_static_data| check down in DetermineRevalidationPolicy This CL moves if (is_static_data) return kUse; section down in DetermineRevalidationPolicy as a preparation to factor out some |return kReload;| statements. BUG=652228 R=hiroshige@chromium.org, japhet@chromium.org ==========
yhirano@chromium.org changed reviewers: - japhet@chromium.org
Description was changed from ========== Move |is_static_data| check down in DetermineRevalidationPolicy This CL moves if (is_static_data) return kUse; section down in DetermineRevalidationPolicy as a preparation to factor out some |return kReload;| statements. BUG=652228 R=hiroshige@chromium.org, japhet@chromium.org ========== to ========== Move |is_static_data| check down in DetermineRevalidationPolicy This CL moves if (is_static_data) return kUse; section down in DetermineRevalidationPolicy as a preparation to factor out some |return kReload;| statements. BUG=652228 R=hiroshige@chromium.org ==========
On 2017/04/20 09:33:21, hiroshige wrote: > Could you explain the intention of this? > Is there specific case where we want to return kReload for static data? I didn't think you were awoke :) Done. Initially I thought I didn't need |!is_static_data &&|, but it was wrong according to a test failure. The motivation is that I will factor some kReload cases out in a subsequent CL and so I don't want to have a kUse statement in between.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
On 2017/04/20 11:19:09, yhirano wrote: > On 2017/04/20 09:33:21, hiroshige wrote: > > Could you explain the intention of this? > > Is there specific case where we want to return kReload for static data? > > I didn't think you were awoke :) > > Done. Initially I thought I didn't need |!is_static_data &&|, but it was wrong > according to a test failure. > > The motivation is that I will factor some kReload cases out in a subsequent CL > and so I don't want to have a kUse statement in between. lgtm. I also suspect additional |is_static_data| is not really needed (especially the one related to revalidation/304), but we can leave it for separate investigation because it isn't related to your context. Also, this looks consistent with Nate's plan to group the conditions of DetermineRevalidationPolicy(), e.g. high-priority kReloads, mid-priority kUse, low-priority kReloads, and then kRevalidate/kUse or something like. I think we should have a tracking bug for that and add it to BUG= line here. Nate, do you have an existing tracking bug for reordering/refactoring DetermineRevalidationPolicy(), or otherwise could you create a new one?\
hiroshige@chromium.org changed reviewers: + japhet@chromium.org
Oh, adding Nate.
The CQ bit was checked by yhirano@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_...)
No, I don't have an existing tracking bug for DetermineRevalidationPolicy cleanup. This LGTM.
Description was changed from ========== Move |is_static_data| check down in DetermineRevalidationPolicy This CL moves if (is_static_data) return kUse; section down in DetermineRevalidationPolicy as a preparation to factor out some |return kReload;| statements. BUG=652228 R=hiroshige@chromium.org ========== to ========== Move |is_static_data| check down in DetermineRevalidationPolicy This CL moves if (is_static_data) return kUse; section down in DetermineRevalidationPolicy as a preparation to factor out some |return kReload;| statements. BUG=652228, 714574 R=hiroshige@chromium.org ==========
Thank you. I filed https://crbug.com/714574.
The CQ bit was checked by yhirano@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from hiroshige@chromium.org Link to the patchset: https://codereview.chromium.org/2829043002/#ps60001 (title: "rebase")
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: 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 yhirano@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": 60001, "attempt_start_ts": 1493107423225460, "parent_rev": "0363d88c658806d011c31a4f48f25779e9bc5f22", "commit_rev": "58197789bfafee408d8fc728c0ed2f1da81bbbed"}
Message was sent while issue was closed.
Description was changed from ========== Move |is_static_data| check down in DetermineRevalidationPolicy This CL moves if (is_static_data) return kUse; section down in DetermineRevalidationPolicy as a preparation to factor out some |return kReload;| statements. BUG=652228, 714574 R=hiroshige@chromium.org ========== to ========== Move |is_static_data| check down in DetermineRevalidationPolicy This CL moves if (is_static_data) return kUse; section down in DetermineRevalidationPolicy as a preparation to factor out some |return kReload;| statements. BUG=652228, 714574 R=hiroshige@chromium.org Review-Url: https://codereview.chromium.org/2829043002 Cr-Commit-Position: refs/heads/master@{#466931} Committed: https://chromium.googlesource.com/chromium/src/+/58197789bfafee408d8fc728c0ed... ==========
Message was sent while issue was closed.
Committed patchset #4 (id:60001) as https://chromium.googlesource.com/chromium/src/+/58197789bfafee408d8fc728c0ed... |