|
|
DescriptionFix PrintPreviewDestinationSearchTest.Select
This reverts commit d2672f44f61002cfff2d7fd5a4bc70d54d903304.
Uninitialized booleans are causing the test to crash when used to build
a JSON string on the ASAN bot. Problem surfaced after clang was uprevved.
BUG=702640
Review-Url: https://codereview.chromium.org/2788283002
Cr-Commit-Position: refs/heads/master@{#462312}
Committed: https://chromium.googlesource.com/chromium/src/+/67d0cd0e97bb647deaf65a7adb3dfc76ff71dacc
Patch Set 1 #
Total comments: 4
Patch Set 2 : move init into constructor #Patch Set 3 : update test #Patch Set 4 : run the print preview test for CrOS only #Patch Set 5 : test all platforms #
Total comments: 7
Patch Set 6 : comments addressed #
Messages
Total messages: 49 (28 generated)
The CQ bit was checked by skau@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: This issue passed the CQ dry run.
skau@chromium.org changed reviewers: + thakis@chromium.org
Please review. It looks like uninitialized booleans are now causing failures in the ASAN bot.
Description was changed from ========== Fix PrintPreviewDestinationSearchTest.Select This reverts commit d2672f44f61002cfff2d7fd5a4bc70d54d903304. Uninitialized booleans are causing the test to crash when used to build a JSON string. I suspect a compiler bug. BUG=702640 ========== to ========== Fix PrintPreviewDestinationSearchTest.Select This reverts commit d2672f44f61002cfff2d7fd5a4bc70d54d903304. Uninitialized booleans are causing the test to crash when used to build a JSON string on the ASAN bot. Problem surfaced after clang was uprevved. BUG=702640 ==========
skau@chromium.org changed reviewers: + thestig@chromium.org - thakis@chromium.org
thestig: Can you take a look? thakis should probably review, but he's out today.
https://codereview.chromium.org/2788283002/diff/1/chrome/browser/ui/webui/pri... File chrome/browser/ui/webui/print_preview/print_preview_ui.h (right): https://codereview.chromium.org/2788283002/diff/1/chrome/browser/ui/webui/pri... chrome/browser/ui/webui/print_preview/print_preview_ui.h:178: bool source_is_modifiable_ = false; This is also being set in the constructor... to true. Can we leave this alone? It's clearly not the cause of the uninit error. https://codereview.chromium.org/2788283002/diff/1/chrome/browser/ui/webui/pri... chrome/browser/ui/webui/print_preview/print_preview_ui.h:184: bool print_selection_only_ = false; This is the missing initialization. Let's move it to the ctor for consistency with the rest.
The CQ bit was checked by skau@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...
Thanks for the review. I forgot to look at the ctor before making the change. https://codereview.chromium.org/2788283002/diff/1/chrome/browser/ui/webui/pri... File chrome/browser/ui/webui/print_preview/print_preview_ui.h (right): https://codereview.chromium.org/2788283002/diff/1/chrome/browser/ui/webui/pri... chrome/browser/ui/webui/print_preview/print_preview_ui.h:178: bool source_is_modifiable_ = false; On 2017/04/03 20:32:42, Lei Zhang wrote: > This is also being set in the constructor... to true. Can we leave this alone? > It's clearly not the cause of the uninit error. Done. https://codereview.chromium.org/2788283002/diff/1/chrome/browser/ui/webui/pri... chrome/browser/ui/webui/print_preview/print_preview_ui.h:184: bool print_selection_only_ = false; On 2017/04/03 20:32:42, Lei Zhang wrote: > This is the missing initialization. Let's move it to the ctor for consistency > with the rest. Done.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: 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_...)
Initializing |print_selection_only_| lgtm, but the test is still failing on trybots. :[
The CQ bit was checked by skau@chromium.org to run a CQ dry run
The recent change to the UI invalidated the test. I've fixed it now. I'll wait until tomorrow to submit if you want to take another look.
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
++lgtm
The CQ bit was checked by skau@chromium.org
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: win_chromium_x64_rel_ng on master.tryserver.chromium.win (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)
The CQ bit was checked by skau@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...
Looks like the codepath for the non-CrOS platforms are no longer compatible. I'll need to tweak the test to ignore some of the platform specific behavior.
Does it make sense to have a non-ChromeOS version of PrintPreviewDestinationSearchTest.Select as well?
There's some similarity between the ChromeOS and non-ChromeOS flow so I'm trying to see if there's a sensible way to test all platforms with the same code.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by skau@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...
PTAL. I've update the test to verify behavior on all the platforms. The codepaths have some differences so the tests have some conditional logic in them. Let me know if you think I should separate it into two files.
PTAL. I've update the test to verify behavior on all the platforms. The codepaths have some differences so the tests have some conditional logic in them. Let me know if you think I should separate it into two files.
PTAL. I've update the test to verify behavior on all the platforms. The codepaths have some differences so the tests have some conditional logic in them. Let me know if you think I should separate it into two files.
https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... File chrome/test/data/webui/print_preview_destination_search_test.js (right): https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... chrome/test/data/webui/print_preview_destination_search_test.js:104: if (!cr.isChromeOS) { If it's all the same, put the isChromeOS case inside the if block, as it is shorter. https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... chrome/test/data/webui/print_preview_destination_search_test.js:151: if (!cr.isChromeOS) { Why omit the success key/value for non-ChromeOS now? https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... chrome/test/data/webui/print_preview_destination_search_test.js:236: if (cr.isChromeOS) { How about the non-ChromeOS case?
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by skau@chromium.org to run a CQ dry run
Comments addressed. PTAL. https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... File chrome/test/data/webui/print_preview_destination_search_test.js (right): https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... chrome/test/data/webui/print_preview_destination_search_test.js:104: if (!cr.isChromeOS) { On 2017/04/05 21:54:31, Lei Zhang wrote: > If it's all the same, put the isChromeOS case inside the if block, as it is > shorter. Done. https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... chrome/test/data/webui/print_preview_destination_search_test.js:151: if (!cr.isChromeOS) { On 2017/04/05 21:54:31, Lei Zhang wrote: > Why omit the success key/value for non-ChromeOS now? non-ChromeOS doesn't read the success value. But it doesn't matter if it's included. https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... chrome/test/data/webui/print_preview_destination_search_test.js:236: if (cr.isChromeOS) { On 2017/04/05 21:54:32, Lei Zhang wrote: > How about the non-ChromeOS case? I've added the non-CrOS case. It's a bit weird as selection still occurs. I'll look into adding an appropriate check in a later CL.
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
lgtm += 2? https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... File chrome/test/data/webui/print_preview_destination_search_test.js (right): https://codereview.chromium.org/2788283002/diff/80001/chrome/test/data/webui/... chrome/test/data/webui/print_preview_destination_search_test.js:236: if (cr.isChromeOS) { On 2017/04/05 23:41:09, skau wrote: > On 2017/04/05 21:54:32, Lei Zhang wrote: > > How about the non-ChromeOS case? > > I've added the non-CrOS case. It's a bit weird as selection still occurs. I'll > look into adding an appropriate check in a later CL. Thanks.
The CQ bit was checked by skau@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Logged crbug.com/708834 to address the behavior in print preview.
CQ is committing da patch. Bot data: {"patchset_id": 100001, "attempt_start_ts": 1491436807426710, "parent_rev": "e792e0e91d5b20121b9eb634b43af7eeb04b612f", "commit_rev": "67d0cd0e97bb647deaf65a7adb3dfc76ff71dacc"}
Message was sent while issue was closed.
Description was changed from ========== Fix PrintPreviewDestinationSearchTest.Select This reverts commit d2672f44f61002cfff2d7fd5a4bc70d54d903304. Uninitialized booleans are causing the test to crash when used to build a JSON string on the ASAN bot. Problem surfaced after clang was uprevved. BUG=702640 ========== to ========== Fix PrintPreviewDestinationSearchTest.Select This reverts commit d2672f44f61002cfff2d7fd5a4bc70d54d903304. Uninitialized booleans are causing the test to crash when used to build a JSON string on the ASAN bot. Problem surfaced after clang was uprevved. BUG=702640 Review-Url: https://codereview.chromium.org/2788283002 Cr-Commit-Position: refs/heads/master@{#462312} Committed: https://chromium.googlesource.com/chromium/src/+/67d0cd0e97bb647deaf65a7adb3d... ==========
Message was sent while issue was closed.
Committed patchset #6 (id:100001) as https://chromium.googlesource.com/chromium/src/+/67d0cd0e97bb647deaf65a7adb3d... |