commit | 0ad9df7598c9f1bba4dc2b48c8b8c4105c9ca014 | [log] [tgz] |
---|---|---|
author | Alan Screen <awscreen@chromium.org> | Tue Sep 27 18:34:35 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 27 18:34:35 2022 |
tree | ce9fce9a9484b6ff2d1ac49ecb8d8fc7cc9cc0e4 | |
parent | ace02be7da26e455102dde0778deceb33de05a21 [diff] |
Add print test for error in middle of multipage job Add a test which will have a rendering failure on a page before the end of the job, where multiple pages have already been sent to the OOP PrintBackendService. This test needs to be disabled, as it shows there is incorrect print control flow in PrintBackendService for this scenario. This only affects Windows, which has a rendering call per page instead of just one rendering call for the whole document. Update the testing infrastructure to allow specifying that a rendering error can occur on a particular page number. Extend the class PrintBackendServiceTestImpl to hold onto pages without immediate rendering, to ensure consistent test behavior so there is no race condition between getting pages sent before the service can process them. LOW_COVERAGE_REASON=Files notified for are all browser tests support. Bug: 1326580 Change-Id: I6a0ee1211ea4b911802372d4db1e2274a718af67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3658629 Commit-Queue: Alan Screen <awscreen@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1051920}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.