Now gtest-parallel is the same as in the github repo.
A wrapper script was created to handle the environment variables.
TBR=pbos@webrtc.org
BUG=chromium:497757
NOTRY=True
Review-Url: https://codereview.webrtc.org/2513073002
Cr-Commit-Position: refs/heads/master@{#15170}
This is because:
1) The environment variables were still around when the test was executed.
2) gtest-parallel executes only one test at a time.
So when the test was invoked from a shard different than the 0th one, for example as:
./something_unittests --gtest_filter=Test.Name
It read the environment variables, and the environment variables together with the gtest_filter flag, told it that there were several shards, but only one test to be run, so if it wasn't the 0th shard, it wouldn't run the test at all.
This is fixed by erasing the environment variables once read.
Also change swarming-related flag names to fit the rest of the flags and validate their values.
NOTRY=True
BUG=chromium:497757, chromium:664425
TBR=pbos@webrtc.org, kjellander@webrtc.org
Review-Url: https://codereview.webrtc.org/2505093003
Cr-Commit-Position: refs/heads/master@{#15110}
22c71034 Add flag for running only failed and new tests
2f5c75fd Fix support for TYPED_TEST_CASEs.
Review-Url: https://codereview.webrtc.org/2025293002
Cr-Commit-Position: refs/heads/master@{#12994}
Brings in fixes that save log output to disk instead of piping them
through Python. Should fix problem where output from tests stall for
more than 10 seconds.
Also enabling JsepPeerConnectionP2PTestClient on all platforms again.
BUG=webrtc:5231
R=kjellander@webrtc.org
Review URL: https://codereview.webrtc.org/1509463002 .
Cr-Commit-Position: refs/heads/master@{#10917}
