- Jul 08, 2016
-
-
murgatroid99 authored
-
- Jul 07, 2016
-
-
Craig Tiller authored
Fix TSAN failure in tcp_server (shown via qps_openloop_test)
-
kpayson64 authored
Ruby garbage collection fixes
-
- Jul 06, 2016
-
-
Nicolas Noble authored
removed unused version of status_code_enum.h
-
Nicolas Noble authored
Initialize variables in surface/call.c
-
kpayson64 authored
Make running individual Python tests less painful
-
Nicolas Noble authored
Change port_server.py to use port 32766
-
- Jul 02, 2016
-
-
Nicolas Noble authored
Expunge all references to zookeeper
-
Nicolas Noble authored
Add http2 status code in error_message if it's not 200
-
Nicolas Noble authored
Contributed cmake project files.
-
Nicolas "Pixel" Noble authored
-
Nicolas "Pixel" Noble authored
-
David G. Quintas authored
Removed invalid sentence from interop flag description
-
- Jul 01, 2016
-
-
Craig Tiller authored
-
Craig Tiller authored
-
Masood Malekghassemi authored
-
Masood Malekghassemi authored
-
Masood Malekghassemi authored
We'll need to fix coverage testing in the future anyway (see #6894).
-
Masood Malekghassemi authored
-
Masood Malekghassemi authored
-
Masood Malekghassemi authored
-
Masood Malekghassemi authored
Before this change, running Python tests individually required building a tox environment via the run_tests script and then specifying long environment variables to filter out just the test we wanted to run (and then we wouldn't be able to get the output on interrupt, nor would we have an easy way of determining the PID of the process for debugger attachment). Now invoking the build_python.sh script creates a workable python virtual environment that includes all necessary libraries and tests (s.t. running a single test is now possible by just knowing the module name). This does not change existing supported means of running tests (e.g. through run_tests.py). An additional way of running individual tests has been introduced. Following invocation of `./tools/run_tests/build_python.sh` (or run_tests.py), one may invoke ./$VENV/bin/python -m $TEST_MODULE_NAME and acquire a single running process that *is* the test process (rather than a parent of the process). $VENV is the virtual environment name specified to `build_python.sh` (defaults to `py27`) and $TEST_MODULE_NAME is what it says on the tin.
-
Masood Malekghassemi authored
Moves all tests into a separate package. This does not change existing supported means of running tests (e.g. through run_tests.py).
-
Masood Malekghassemi authored
-
Masood Malekghassemi authored
-
Masood Malekghassemi authored
-
Ken Payson authored
32767 is used by filenet-powsrm
-
Craig Tiller authored
Fix memory leak, fix error.c refcount reporting
-
Yuchen Zeng authored
-
makdharma authored
Build objective-c examples as part of automatic tests
-
- Jun 30, 2016
-
-
murgatroid99 authored
-
murgatroid99 authored
-
Jan Tattermusch authored
Add a maybe-temporary way for apps to clear the channel cache
-
Jan Tattermusch authored
fix for working with compressed data. Fixes #6746.
-
Jan Tattermusch authored
Use open-source defaults to propagate Python plugin configuration
-
Jan Tattermusch authored
Fix bug with override_server flag in run_interop_tests.py
-
Jan Tattermusch authored
Dont create errors redundently in chttp2_transport.c
-
Jan Tattermusch authored
implemented eventfd_check_availability
-
Jan Tattermusch authored
Fix Python server interop spec noncompliance
-
Jan Tattermusch authored
PHP: fix shutdown hang issue
-