Conflicts:
	tools/run_tests/run_tests.py

Helgrind support for run_tests.py

  -) Adding a new command line flag to be able to see which tests are passing.
  -) Adding more status when the tool is idle in forever mode.
  -) Adding a last status when the tool is finished so to avoid leaving the console in a weird state.
  -) Adding a status message in the forever mode if the previous run failed.
  -) Swapped the message and its explanation, so you don't have to scroll up to see which test failed.
  -) Fixed a race condition in the watch_dir.py code if a file is deleted during the loop.

Grpc Tools: update JDK; fix the interop server transport flag

Also allow maxjobs to be tweaked based upon which configs are being run,
to prevent memory starvation.

Muting an extremely chatty log line.

- necessary to allow seamless interop testing, as discussed earlier this week.

Send a scheme of http or https as appropriate, rather than grpc.

1. scheme_from_args should return const char*
2. Rename grpc.scheme arg to grpc.http2_scheme, and define a macro for
it.

Remove unused private field

Remove go codegen from this repository

Build all targets for a config at once

Fix return behavior of run_tools.py

Make the C++ API use C API calls to fiddle with status

This prevents mismatches from breaking tests.

So that later cancellations do not clobber status.

If not running in forever mode, and a test fails, fail run_tests.py
also.

If running in forever mode and make fails, wait for the next run.

Make cpp codegen consistent with protoc in template format.

Properly mask signals in unit tests

Compile fix for mac

Node client constructor

Various win32 fixes.

Removing a few more traces of libevent.

Now all the gpr tests build and run under win32.