Roll src/third_party/pdfium/ f24afac5e..54e6da1ee (2 commits)

https://pdfium.googlesource.com/pdfium.git/+log/f24afac5e17e..54e6da1ee793

$ git log f24afac5e..54e6da1ee --date=short --no-merges --format='%ad %ae %s'
2018-04-19 thestig Do validation earlier in CPDF_SampledFunc::v_Init().
2018-04-19 thestig Validate the Range key in Functions.

Created with:
  roll-dep src/third_party/pdfium


The AutoRoll server is located here: https://pdfium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=dsinclair@chromium.org

Change-Id: I4be0a495123c63ad2aa5d32b8621bad925fe1f41
Reviewed-on: https://chromium-review.googlesource.com/1019729
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: default avatarpdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#552139}
parent a4b24be5
...@@ -113,7 +113,7 @@ vars = { ...@@ -113,7 +113,7 @@ vars = {
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling PDFium # the commit queue can handle CLs rolling PDFium
# and whatever else without interference from each other. # and whatever else without interference from each other.
'pdfium_revision': 'f24afac5e17e10f70336912ff85d8cb9c783f8a8', 'pdfium_revision': '54e6da1ee793f436341dfcdc4e0c26b0658d1928',
# Three lines of non-changing comments so that # Three lines of non-changing comments so that
# the commit queue can handle CLs rolling openmax_dl # the commit queue can handle CLs rolling openmax_dl
# and whatever else without interference from each other. # and whatever else without interference from each other.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment