5112d75a46
Add TestEnvironment to tests
2020-07-30 23:43:02 -07:00
3e7d5976b5
Add TestEnvironment to tests
2020-07-30 11:06:52 -07:00
f2374fb591
Add TestEnvironment to tests
2020-07-29 19:29:55 -07:00
165ee5007a
Replaced grpc::string with std::string
2020-06-29 17:56:36 -07:00
2a3b1f0eb7
Revert log changes
2020-06-22 09:25:59 -07:00
b3469c723e
Pre-assigned the server port and added more logs
2020-06-19 13:49:16 -07:00
ed2037d343
Update by review
2020-06-12 16:32:02 -07:00
0eefd8b209
Finish client first completely for client-lead tests
2020-06-12 14:22:34 -07:00
d45f877dfb
Add more logs and asswert to qps_worker
2020-05-19 11:37:26 -07:00
c769951764
Remove deprecated variant of JoinHostPort().
2020-05-08 09:13:26 -07:00
fc6f26c89b
Remove grpc_core::StringView.
2020-04-27 07:46:13 -07:00
962a8f28f9
Add a flag to set a grpclb+pick_first service config in
...
CreateTestChannel; use CreateTestChannel in qps_json_driver
2020-04-03 12:28:55 -07:00
415d41f9e8
Rerun clang-formatter-7
2020-03-03 10:46:55 -08:00
41ac287f7b
generate build metadata from bazel BUILD
2020-02-26 19:56:49 -05:00
16ea383337
Update qps scenarios
2020-02-18 16:28:19 -08:00
6622c94c17
Shutdown server properly before CQs
2020-01-30 09:25:57 -08:00
e52081f903
More pythons to be formatted
2020-01-03 22:21:23 -08:00
e5634f318c
dont run qps_json_driver and json_run_localhost scenarios under bazel on mac
2019-11-27 17:16:28 +01:00
3240333334
Merge pull request #20597 from nanahpang/benchmark-correctness
...
Correct the benchmark calculation and add comments to clarify the meaning of each field in ScenarioResultSummary
2019-11-25 11:13:40 -08:00
be6979202b
Revamp server-side C++ callback API, message allocator, and mocking
2019-11-20 16:56:18 -08:00
e45b60d1fe
Fix unique_ptr<char> memory allocation mismatch
2019-11-07 17:53:59 -08:00
b2b7fc9af8
Replaced grpc_core::UniquePtr with std::unique_ptr
2019-11-07 13:05:39 -08:00
9918329bb5
Groundhog day
2019-11-06 14:54:31 -08:00
57e40c87e9
Buildifier again
2019-11-06 13:57:04 -08:00
959945705a
Merge branch 'master' of https://github.com/grpc/grpc into blaze_modifications
2019-11-06 11:00:47 -08:00
02f558e57a
Make the generated file buildifier format compatible
2019-11-05 14:03:53 -08:00
202a02341f
Regenerate qps scenarios
2019-11-05 14:03:52 -08:00
c34bef4ca4
Format all Bazel files with buildifier
2019-11-05 14:03:52 -08:00
5eea97b7d6
Merge remote-tracking branch 'upstream/master' into benchmark-correctness
2019-11-04 16:55:14 -08:00
444d5b7760
Revert "Reuse the definition already in the bazel/ directory"
...
Turns out that putting this in the main build definition starklark file
means that our users will also incur a dependency on the repo rule.
That's no bueno.
This reverts commit 78e443b4f6
2019-11-04 15:34:45 -08:00
78e443b4f6
Reuse the definition already in the bazel/ directory
2019-11-04 14:12:22 -08:00
4c8935761d
Add wrapper layer for Blaze
2019-11-04 14:02:30 -08:00
c97ce9057b
Simplify the platform and constraints settings for remote execution
...
* Remove the toolchains //third_party/toolchains:local and //third_party/toolchains:local_large.
* Remove the platforms :rbe_ubuntu1604, :rbe_ubuntu1604_large, :local and :local_large.
* No longer inherit from @rbe_default//config:platform but instead use it directly. It is now the only non-windows platform.
* When creating @rbe_default//config:platform directly with rbe_autoconfig, set dockerAddCapabilities and dockerPrivileged directly in the exec_properties field. No need to set dockerNetwork to "off" and dockerSiblingContainers to false since these are the defaults.
* Also set gceMachineType = "n1-highmem-2" on the default platform. This value can be overridden by specific targets that want to use LARGE_MACHINE.
* Use create_exec_properties_dict where appropriate.
* Use custom_exec_properties to define LARGE_MACHINE.
I wasn't able to test thoroughly that this PR does not break any existing targets. I was not able to run anything on windows/mac and I also don't have access to gRPC's RBE setup.
2019-10-29 15:40:28 -04:00
892d5d724e
Merge pull request #20732 from grpc/revert-20611-revert-20558-upgrade_bazel100
...
Revert "Revert "Upgrade to bazel 1.0.0""
2019-10-29 17:47:31 +01:00
e5e3f70a1a
Revert "Revert "Upgrade to bazel 1.0.0""
2019-10-29 06:31:38 -04:00
8983ad4aff
Revert "Measure benchmark results more accurately in qps_driver"
2019-10-28 19:37:48 -07:00
18580a9f4e
clang format
2019-10-28 10:44:42 -07:00
03ac8490ea
revert changes
2019-10-28 10:20:21 -07:00
1ead5c1905
remove the last invalid read, which cause hanging issue in driver
2019-10-28 10:00:25 -07:00
968f7130a7
Fix typo
2019-10-25 15:27:34 -07:00
b6fe2678bb
Clarify comments
2019-10-25 12:49:46 -07:00
8edf0dd0c8
clang format
2019-10-25 11:56:27 -07:00
3e90f3bea5
fix result inaccuracy in driver.cc
2019-10-25 11:32:08 -07:00
296f63b0bc
Explicitly spell out type to document RAII-ness
2019-10-23 14:07:30 -07:00
b8631a1301
Merge remote-tracking branch 'upstream/revert-20526-xds_policy_config_additions' into benchmark-correctness
2019-10-22 17:49:15 -07:00
1a374bc984
Add explanation to the comments
2019-10-21 18:21:08 -07:00
e35c869aaf
Remove unused-parameter warnings, round 2 (19 of 19)
2019-10-21 09:16:35 -07:00
c7f296908e
Merge pull request #20642 from vjpai/remove_warn_19
...
Remove unused parameter warnings (19 of 20)
2019-10-17 14:00:07 -07:00
ece1ed7906
clang-format
2019-10-17 09:08:38 -07:00
53e19e8de2
Remove unused parameter warning (20 of 20)
2019-10-17 08:52:15 -07:00
Esun Kim