Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(88)

Issue 1833863004: process_policy_test.cc: Fix mixed-sign comparison warning. (Closed)

Created:
4 years, 9 months ago by hans
Modified:
4 years, 9 months ago
Reviewers:
Will Harris
CC:
chromium-reviews, wfh+watch_chromium.org, rickyz+watch_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

process_policy_test.cc: Fix mixed-sign comparison warning. Clang builds were failing like this: In file included from ..\..\sandbox\win\src\process_policy_test.cc:19: ..\..\testing/gtest/include/gtest/gtest.h(1392,16): error: comparison of integers of different signs: 'const unsigned long' and 'const int' [-Werror,-Wsign-compare] if (expected == actual) { ~~~~~~~~ ^ ~~~~~~ ..\..\testing/gtest/include/gtest/gtest.h(1422,12): note: in instantiation of function template specialization 'testing::internal::CmpHelperEQ<unsigned long, int>' requested here return CmpHelperEQ(expected_expression, actual_expression, expected, ^ ..\..\sandbox\win\src\process_policy_test.cc(419,3): note: in instantiation of function template specialization 'testing::internal::EqHelper<false>::Compare<unsigned long, int>' requested here EXPECT_EQ(STATUS_BREAKPOINT, runner.RunTest(L"Process_Crash")); ^ ..\..\testing/gtest/include/gtest/gtest.h(1928,67): note: expanded from macro 'EXPECT_EQ' EqHelper<GTEST_IS_NULL_LITERAL_(expected)>::Compare, \ ^ BUG=82385 TBR=wfh Committed: https://chromium.googlesource.com/chromium/src/+/035459168ac247f089c25d5f5c3c1f36814bb1f5

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -1 line) Patch
M sandbox/win/src/process_policy_test.cc View 1 chunk +2 lines, -1 line 0 comments Download

Messages

Total messages: 10 (5 generated)
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1833863004/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1833863004/1
4 years, 9 months ago (2016-03-25 16:08:33 UTC) #4
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/035459168ac247f089c25d5f5c3c1f36814bb1f5 Cr-Commit-Position: refs/heads/master@{#383286}
4 years, 9 months ago (2016-03-25 16:30:48 UTC) #6
hans
Committed patchset #1 (id:1) manually as 035459168ac247f089c25d5f5c3c1f36814bb1f5 (presubmit successful).
4 years, 9 months ago (2016-03-25 16:31:55 UTC) #8
Will Harris
lgtm. when will clang compiler bots be coming to the CQ? :)
4 years, 9 months ago (2016-03-25 16:41:55 UTC) #9
hans
4 years, 9 months ago (2016-03-25 17:48:57 UTC) #10
Message was sent while issue was closed.
On 2016/03/25 16:41:55, Will Harris wrote:
> lgtm. when will clang compiler bots be coming to the CQ? :)

Should be Real Soon Now. Nico enabled it earlier this week, but had to disable
again due to capacity issues.

Powered by Google App Engine
This is Rietveld 408576698