| /third_party/grpc/test/cpp/qps/ |
| D | json_run_localhost_scenarios.bzl | 3 …scenarios\' : [{"name": "cpp_protobuf_async_unary_75Kqps_600channel_60Krpcs_300Breq_50Bresp", "war…
|
| D | qps_json_driver_scenarios.bzl | 3 …scenarios\' : [{"name": "cpp_protobuf_sync_streaming_qps_unconstrained_insecure", "warmup_seconds"…
|
| D | qps_json_driver.cc | 261 Scenarios scenarios; in QpsDriver() local
262 ParseJson(json.c_str(), "grpc.testing.Scenarios", &scenarios); in QpsDriver()
266 GPR_ASSERT(scenarios.scenarios_size() > 0); in QpsDriver()
268 for (int i = 0; i < scenarios.scenarios_size(); i++) { in QpsDriver()
270 const Scenario& scenario = scenarios.scenarios(i); in QpsDriver()
274 Scenario* scenario = scenarios.mutable_scenarios(i); in QpsDriver()
|
| D | gen_build_yaml.py | 131 for scenario_json in scenario_config.CXXLanguage().scenarios()
160 for scenario_json in scenario_config.CXXLanguage().scenarios()
195 for scenario_json in scenario_config.CXXLanguage().scenarios()
|
| /third_party/grpc/tools/profiling/qps/ |
| D | qps_diff.py | 84 def run(name, scenarios, loops): argument
85 for sn in scenarios:
88 subprocess.check_call(_run_cmd(name, scenarios[sn], fname))
113 def diff(scenarios, loops, old, new): argument
118 for sn in scenarios:
128 for sn in scenarios:
|
| /third_party/grpc/src/php/tests/qps/generated_code/Grpc/Testing/ |
| D | Scenarios.php | 21 private $scenarios; variable in Grpc\\Testing\\Scenarios
43 return $this->scenarios;
54 $this->scenarios = $arr;
|
| /third_party/grpc/test/core/fling/ |
| D | client.cc | 139 static const scenario scenarios[] = { variable
181 for (i = 0; i < GPR_ARRAY_SIZE(scenarios); i++) { in main()
182 if (0 == strcmp(scenarios[i].name, scenario_name)) { in main()
183 sc = scenarios[i]; in main()
189 for (i = 0; i < GPR_ARRAY_SIZE(scenarios); i++) { in main()
190 fprintf(stderr, " %s", scenarios[i].name); in main()
|
| /third_party/node/test/parallel/ |
| D | test-timers-nested.js | 13 const scenarios = [0, 100]; variable
15 scenarios.forEach(function(delay) {
|
| /third_party/grpc/tools/run_tests/ |
| D | run_performance_tests.py | 359 scenarios = []
372 scenarios.append(
380 for scenario_json in language.scenarios():
433 scenarios.append(scenario)
435 return scenarios
638 scenarios = create_scenarios(languages,
648 if not scenarios:
656 for scenario in scenarios:
|
| D | README.md | 37 Runs predefined benchmark scenarios for given languages. Besides the simple configuration of runnin…
45 - `--regex` use regex to select particular scenarios to run.
|
| /third_party/boost/libs/endian/doc/endian/ |
| D | mini_review_topics.adoc | 17 Common use case scenarios should be developed.::
20 <<choosing_use_cases,Use cases>> for use case scenarios.
22 Example programs should be developed for the common use case scenarios.::
26 …eger/float type and endian conversion approaches to the common use case scenarios, and provide gui…
42 …endian integer approaches against endian conversion approaches for the common use case scenarios.::
|
| D | history.adoc | 21 Common use case scenarios should be developed.::
24 <<choosing_use_cases,Use cases>> for use case scenarios.
26 Example programs should be developed for the common use case scenarios.::
30 …eger/float type and endian conversion approaches to the common use case scenarios, and provide gui…
46 …endian integer approaches against endian conversion approaches for the common use case scenarios.::
|
| /third_party/typescript/src/testRunner/unittests/tsserver/ |
| D | projectReferenceCompileOnSave.ts | 161 scenarios: readonly ScenarioDetails[]; property
169 function verifyScenario({ openFiles, scenarios }: VerifyScenario) {
174 } of scenarios) {
398 scenarios: scenarioDetailsOfUsage()
405 scenarios: [
|
| /third_party/grpc/tools/run_tests/performance/ |
| D | scenario_config.py | 243 def scenarios(self): member in CXXLanguage
629 def scenarios(self): member in CSharpLanguage
757 def scenarios(self): member in PythonLanguage
834 def scenarios(self): member in PythonAsyncIOLanguage
983 def scenarios(self): member in RubyLanguage
1056 def scenarios(self): member in Php7Language
1119 def scenarios(self): member in JavaLanguage
1223 def scenarios(self): member in GoLanguage
1315 def scenarios(self): member in NodeLanguage
|
| /third_party/ltp/testcases/open_posix_testsuite/functional/timers/ |
| D | plan.txt | 7 scenarios. Not all of these may be implemented. The assertions.xml file
13 clocks - Testing that clocks can accurately keep time in certain scenarios.
37 correct behavior of the features listed above and generated test scenarios
40 generated test scenarios setting clocks or timers to these critical
47 Some potential test case scenarios are listed after each functional
|
| /third_party/musl/libc-test/src/functional/ |
| D | pthread_cancel-points.c | 103 } scenarios[] = { variable
112 }, *cur_sc = scenarios;
|
| /third_party/grpc/test/cpp/thread_manager/ |
| D | thread_manager_test.cc | 150 TestThreadManagerSettings scenarios[] = { variable
159 ::testing::ValuesIn(scenarios));
|
| /third_party/grpc/src/python/grpcio_tests/tests_aio/unit/ |
| D | _metadata_test.py | 123 scenarios = (
130 for source, expected in scenarios:
|
| /third_party/grpc/test/cpp/end2end/ |
| D | port_sharing_end2end_test.cc | 312 std::vector<TestScenario> scenarios; in CreateTestScenarios() local
332 scenarios.emplace_back(server_has_port, queue_pending_data, cred); in CreateTestScenarios()
336 return scenarios; in CreateTestScenarios()
|
| D | message_allocator_end2end_test.cc | 366 std::vector<TestScenario> scenarios; in CreateTestScenarios() local
388 scenarios.emplace_back(p, cred); in CreateTestScenarios()
391 return scenarios; in CreateTestScenarios()
|
| /third_party/protobuf/java/compatibility_tests/ |
| D | README.md | 26 more_protos depending on protos. This way we can test scenarios where only part
31 We use a shell script to drive the test of different scenarios so the test
|
| /third_party/ltp/testcases/kernel/controllers/memctl/ |
| D | README | 28 Most of the error scenarios have been taken care of for a sane cleanup of the
36 This script creates different scenarios for memory controller testing and
|
| /third_party/ltp/testcases/open_posix_testsuite/stress/timers/ |
| D | plan.txt | 7 scenarios. Not all of these may be implemented. The assertions.xml file
28 Some potential test case scenarios are listed after each functional
|
| /third_party/flutter/engine/flutter/testing/scenario_app/android/app/src/androidTest/java/dev/flutter/scenarios/ |
| D | ExampleInstrumentedTest.java | 1 package dev.flutter.scenarios;
|
| /third_party/boost/libs/convert/ |
| D | README.md | 3 * to be useful and applicable in a wider range of deployment scenarios,
|