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

Issue 4524003: net: add Snap Start tests (Closed)

Created:
10 years, 1 month ago by agl
Modified:
9 years, 7 months ago
CC:
chromium-reviews, cbentzel+watch_chromium.org, darin-cc_chromium.org
Visibility:
Public.

Description

net: add Snap Start tests These tests are Linux only for now. Adding Mac support should be pretty easy. However, Windows will be tough to do without making the tests flakey. Given the huge amounts of pain caused by testserver.py and ephemeral ports I'd rather get the tests working well on a couple of platforms (since the Snap Start code is all platform-generic anyway), then add more flakiness. BUG=none TEST=snap_start_unittests

Patch Set 1 #

Patch Set 2 : ... #

Total comments: 7
Unified diffs Side-by-side diffs Delta from patch set Stats (+601 lines, -0 lines) Patch
M DEPS View 1 chunk +3 lines, -0 lines 0 comments Download
M net/net.gyp View 1 chunk +30 lines, -0 lines 0 comments Download
A net/socket/ssl_client_socket_snapstart_unittest.cc View 1 1 chunk +327 lines, -0 lines 5 comments Download
A net/test/openssl_helper.cc View 1 chunk +241 lines, -0 lines 2 comments Download

Messages

Total messages: 3 (0 generated)
agl
10 years, 1 month ago (2010-11-05 18:14:22 UTC) #1
Mike Belshe
lgtm http://codereview.chromium.org/4524003/diff/3001/4003 File net/socket/ssl_client_socket_snapstart_unittest.cc (right): http://codereview.chromium.org/4524003/diff/3001/4003#newcode5 net/socket/ssl_client_socket_snapstart_unittest.cc:5: #include "build/build_config.h" q: is this intentional? http://codereview.chromium.org/4524003/diff/3001/4003#newcode257 net/socket/ssl_client_socket_snapstart_unittest.cc:257: ...
10 years, 1 month ago (2010-11-08 16:41:10 UTC) #2
Paweł Hajdan Jr.
10 years, 1 month ago (2010-11-08 16:55:32 UTC) #3
Drive-by with test comments. Please fix them before committing.

http://codereview.chromium.org/4524003/diff/3001/4003
File net/socket/ssl_client_socket_snapstart_unittest.cc (right):

http://codereview.chromium.org/4524003/diff/3001/4003#newcode55
net/socket/ssl_client_socket_snapstart_unittest.cc:55: NOTREACHED();
Please read
http://www.chromium.org/developers/coding-style#TOC-CHECK-vs-DCHECK-and-NOTRE...

We avoid crashing the entire test binary. Moreover, this "assertion" will only
fire in debug mode.

http://codereview.chromium.org/4524003/diff/3001/4003#newcode99
net/socket/ssl_client_socket_snapstart_unittest.cc:99: LOG(FATAL) << "Failed to
get DIR_EXE";
Same here, and all other similar places.

http://codereview.chromium.org/4524003/diff/3001/4003#newcode144
net/socket/ssl_client_socket_snapstart_unittest.cc:144: CHECK(r) << "failed to
read " << path.value();
CHECK is bad too.

http://codereview.chromium.org/4524003/diff/3001/4004
File net/test/openssl_helper.cc (right):

http://codereview.chromium.org/4524003/diff/3001/4004#newcode190
net/test/openssl_helper.cc:190: if (ret != 1) {
nit: Simpler:

if (ret == 1)
  break;
...

Powered by Google App Engine
This is Rietveld 408576698