Roll src/third_party/pdfium/ 9ec0bca73..b7c41498a (2 commits)

https://pdfium.googlesource.com/pdfium.git/+log/9ec0bca735b5..b7c41498ac1f

$ git log 9ec0bca73..b7c41498a --date=short --no-merges --format='%ad %ae %s'
2018-05-08 thestig Add some basic tests for FPDF_VIEWERREF_GetPrintPageRange().
2018-05-08 thestig Split CCodec_FlateScanlineDecoder in two.

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: Ibf11fa15f242c5a2608c9487a6cf81c6deb8c62d
Reviewed-on: https://chromium-review.googlesource.com/1050574
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@{#556970}
parent 7f2289bb
...@@ -120,7 +120,7 @@ vars = { ...@@ -120,7 +120,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': '9ec0bca735b5039293f4d2a7552dc491b345f0ab', 'pdfium_revision': 'b7c41498ac1f09debe0b12efe1312a22246a18b0',
# 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