|
|
Created:
6 years, 10 months ago by Daniel Erat Modified:
6 years, 10 months ago CC:
chromium-reviews Base URL:
svn://svn.chromium.org/chrome/trunk/src Visibility:
Public. |
DescriptionEnable subpixel rendering in custom freetype2 library.
Set FT_CONFIG_OPTION_SUBPIXEL_RENDERING in the custom
freetype2 library built for content_shell so that local
Chrome builds will honor the developer's font settings.
BUG=342077
TBR=dpranke@chromium.org
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=253485
Patch Set 1 #Patch Set 2 : add exception for fast/text/chromium-linux-fontconfig-renderstyle.html #Patch Set 3 : merge #Patch Set 4 : merge again #
Messages
Total messages: 29 (0 generated)
I ran the linux_layout_rel on this just to see what would happen, and fast/text/chromium-linux-fontconfig-renderstyle.html will need to be rebaselined (again). See https://codereview.chromium.org/138123004 for the test expectations change I made when creating this file. Dirk should also be aware of this change.
On 2014/02/17 16:51:21, bungeman1 wrote: > I ran the linux_layout_rel on this just to see what would happen, and > fast/text/chromium-linux-fontconfig-renderstyle.html will need to be rebaselined > (again). See https://codereview.chromium.org/138123004 for the test expectations > change I made when creating this file. Dirk should also be aware of this change. Thanks for the pointer! I don't have any recent rebaselining experience. Is http://dev.chromium.org/developers/testing/webkit-layout-tests/testexpectatio... accurate? Is NeedsRebaseline the correct keyword to use here, rather than NeedsManualRebaseline?
On 2014/02/18 22:16:08, Daniel Erat wrote: > On 2014/02/17 16:51:21, bungeman1 wrote: > > I ran the linux_layout_rel on this just to see what would happen, and > > fast/text/chromium-linux-fontconfig-renderstyle.html will need to be > rebaselined > > (again). See https://codereview.chromium.org/138123004 for the test > expectations > > change I made when creating this file. Dirk should also be aware of this > change. > > Thanks for the pointer! I don't have any recent rebaselining experience. Is > http://dev.chromium.org/developers/testing/webkit-layout-tests/testexpectatio... > accurate? Is NeedsRebaseline the correct keyword to use here, rather than > NeedsManualRebaseline? I'm not sure, but I think NeedsRebaseline should only go into the Blink TestExpectations file. The issue here is Blink and Chromium being in separate repositories. I checked in with NeedsManualRebaseline to the Chromium test expectations, then checked in NeedsRebaseline to the Blink test expectations, waited for that to roll into Chromium, then removed the NeedsManualRebaseline from the Chromium test expectations. Then the bot eventually gets around to doing the rebaseline. Note that it's ojan@ who takes care of the bot, so if you have questions about that he'd be the one to ask.
On 2014/02/18 22:24:29, bungeman2 wrote: > On 2014/02/18 22:16:08, Daniel Erat wrote: > > On 2014/02/17 16:51:21, bungeman1 wrote: > > > I ran the linux_layout_rel on this just to see what would happen, and > > > fast/text/chromium-linux-fontconfig-renderstyle.html will need to be > > rebaselined > > > (again). See https://codereview.chromium.org/138123004 for the test > > expectations > > > change I made when creating this file. Dirk should also be aware of this > > change. > > > > Thanks for the pointer! I don't have any recent rebaselining experience. Is > > > http://dev.chromium.org/developers/testing/webkit-layout-tests/testexpectatio... > > accurate? Is NeedsRebaseline the correct keyword to use here, rather than > > NeedsManualRebaseline? > > I'm not sure, but I think NeedsRebaseline should only go into the Blink > TestExpectations file. That page should be correct. NeedsRebaseline is probably the right version to use; it's not that important if the downstream (pinned version) of the bots fails a test or two until the change can be rolled. If necessary you can mark it as expected to fail in the downstream expectations file. You definitely don't want to use both keywords, as that would just be confusing :). -- Dirk
lgtm
The CQ bit was checked by derat@chromium.org
The CQ bit was unchecked by derat@chromium.org
The CQ bit was checked by derat@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/derat@chromium.org/163433013/180001
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/derat@chromium.org/163433013/180001
The CQ bit was unchecked by commit-bot@chromium.org
Retried try job too often on chromium_presubmit for step(s) presubmit http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=chromium_p...
(Dirk, TBR-ing you for third_party/freetype2/OWNERS.)
The CQ bit was checked by derat@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/derat@chromium.org/163433013/180001
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/derat@chromium.org/163433013/180001
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/derat@chromium.org/163433013/180001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel
The CQ bit was checked by derat@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/derat@chromium.org/163433013/180001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel
The CQ bit was checked by derat@chromium.org
The CQ bit was unchecked by derat@chromium.org
The CQ bit was checked by derat@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/derat@chromium.org/163433013/180001
Message was sent while issue was closed.
Change committed as 253485 |