Add debugging information to raw_secure_server_socket_test.

Add debugging information to raw_secure_server_socket_test.

R=fschneider@google.com, kustermann@google.com

Committed: https://github.com/dart-lang/sdk/commit/f1ae158a2a49feae70749f8cee44fa3a6255a3cd

[floitsch, 2016-12-13 14:04:02]

floitsch@google.com changed reviewers:
+ fschneider@google.com, kustermann@google.com

[Florian Schneider, 2016-12-13 18:27:20]

https://codereview.chromium.org/2571603004/diff/1/tests/standalone/io/raw_sec...
File tests/standalone/io/raw_secure_server_socket_test.dart (right):

https://codereview.chromium.org/2571603004/diff/1/tests/standalone/io/raw_sec...
tests/standalone/io/raw_secure_server_socket_test.dart:599: runTests() {
Would it make sense to split this up as a multi-test? This way we would also see
which part timed out without having to add printing.

[floitsch, 2016-12-13 19:21:48]

https://codereview.chromium.org/2571603004/diff/1/tests/standalone/io/raw_sec...
File tests/standalone/io/raw_secure_server_socket_test.dart (right):

https://codereview.chromium.org/2571603004/diff/1/tests/standalone/io/raw_sec...
tests/standalone/io/raw_secure_server_socket_test.dart:599: runTests() {
On 2016/12/13 18:27:20, Florian Schneider wrote:
> Would it make sense to split this up as a multi-test? This way we would also
see
> which part timed out without having to add printing.

Unfortunately no: the test uses VMOptions which is not supported with
multitests.

[Florian Schneider, 2016-12-13 19:26:19]

I see. I didn't know that limitation of multi-tests.

Lgtm.

[kustermann, 2016-12-13 19:39:38]

lgtm

[floitsch, 2016-12-13 20:29:28]

Description was changed from

==========
Add debugging information to raw_secure_server_socket_test.
==========

to

==========
Add debugging information to raw_secure_server_socket_test.

R=fschneider@google.com, kustermann@google.com

Committed:
https://github.com/dart-lang/sdk/commit/f1ae158a2a49feae70749f8cee44fa3a6255a3cd
==========

[floitsch, 2016-12-13 20:29:30]

Committed patchset #1 (id:1) manually as
f1ae158a2a49feae70749f8cee44fa3a6255a3cd (presubmit successful).