/external/grpc-grpc/src/php/tests/qps/generated_code/Grpc/Testing/ |
D | Scenarios.php | 12 * A set of scenarios to be run with qps_json_driver 14 * Generated from protobuf message <code>grpc.testing.Scenarios</code> 16 class Scenarios extends \Google\Protobuf\Internal\Message class 19 * Generated from protobuf field <code>repeated .grpc.testing.Scenario scenarios = 1;</code> 21 private $scenarios; variable in Grpc\\Testing\\Scenarios 29 * Generated from protobuf field <code>repeated .grpc.testing.Scenario scenarios = 1;</code> 34 return $this->scenarios; 38 * Generated from protobuf field <code>repeated .grpc.testing.Scenario scenarios = 1;</code> 45 $this->scenarios = $arr;
|
/external/rust/crates/grpcio-sys/grpc/tools/run_tests/performance/ |
D | scenario_config_exporter.py | 28 """Returns list of scenarios that match given constraints.""" 30 scenarios = scenario_config.LANGUAGES[language_name].scenarios() 31 for scenario_json in scenarios: 47 """Dump a list of json scenarios to json files""" 52 # the dump file should have {"scenarios" : []} as the top level element 53 json.dump({'scenarios': [scenario]}, outfile, indent=2) 57 # example usage: extract C# scenarios and dump them as .json files 58 scenarios = get_json_scenarios('csharp', variable 61 dump_to_json_files(scenarios, 'scenario_dump_')
|
/external/grpc-grpc/test/cpp/qps/ |
D | json_run_localhost_scenarios.bzl | 1 """Scenarios run on localhost.""" 3 …scenarios\' : [{"name": "cpp_protobuf_async_unary_75Kqps_600channel_60Krpcs_300Breq_50Bresp", "war…
|
D | qps_json_driver_scenarios.bzl | 1 """Scenarios of qps driver.""" 3 …scenarios\' : [{"name": "cpp_protobuf_sync_streaming_qps_unconstrained_insecure", "warmup_seconds"…
|
D | qps_json_driver.cc | 204 // Parse into an array of scenarios in QpsDriver() 205 Scenarios scenarios; in QpsDriver() local 206 ParseJson(json.c_str(), "grpc.testing.Scenarios", &scenarios); in QpsDriver() 210 GPR_ASSERT(scenarios.scenarios_size() > 0); in QpsDriver() 212 for (int i = 0; i < scenarios.scenarios_size(); i++) { in QpsDriver() 214 const Scenario& scenario = scenarios.scenarios(i); in QpsDriver() 218 Scenario* scenario = scenarios.mutable_scenarios(i); in QpsDriver()
|
/external/mockftpserver/tags/2.0/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 31 FTP Scenarios Supported by FakeFtpServer 34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 83 scenarios not supported include: 105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/mockftpserver/tags/2.0.1/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 31 FTP Scenarios Supported by FakeFtpServer 34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 83 scenarios not supported include: 105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/mockftpserver/tags/2.0-rc1/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 31 FTP Scenarios Supported by FakeFtpServer 34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 83 scenarios not supported include: 105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/mockftpserver/tags/2.0.2/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 31 FTP Scenarios Supported by FakeFtpServer 34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 83 scenarios not supported include: 105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/mockftpserver/tags/2.0-rc1/MockFtpServer/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 31 FTP Scenarios Supported by FakeFtpServer 34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 83 scenarios not supported include: 105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/mockftpserver/tags/2.0-rc3/MockFtpServer/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 31 FTP Scenarios Supported by FakeFtpServer 34 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 58 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 82 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 83 scenarios not supported include: 105 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/grpc-grpc/tools/run_tests/ |
D | run_performance_tests.py | 122 'scenarios': [scenario_json] 347 """Create jobspecs for scenarios to run.""" 351 scenarios = [] 364 scenarios.append( 372 for scenario_json in language.scenarios(): 425 scenarios.append(scenario) 427 return scenarios 505 help='Just list scenarios to be run, but don\'t run them.') 511 help='Regex to select scenarios to run.') 527 help='Run netperf benchmark as one of the scenarios.') [all …]
|
/external/rust/crates/grpcio-sys/grpc/tools/run_tests/ |
D | run_performance_tests.py | 127 json.dumps({'scenarios': [scenario_json]})) 355 """Create jobspecs for scenarios to run.""" 359 scenarios = [] 372 scenarios.append( 380 for scenario_json in language.scenarios(): 433 scenarios.append(scenario) 435 return scenarios 515 help='Just list scenarios to be run, but don\'t run them.') 520 help='Regex to select scenarios to run.') 533 help='Run netperf benchmark as one of the scenarios.') [all …]
|
/external/mockftpserver/tags/2.1/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 33 FTP Scenarios Supported by FakeFtpServer 36 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 62 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 86 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 87 scenarios not supported include: 109 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
D | fakeftpserver-versus-stubftpserver.apt | 16 …and simulation scenarios. You define a filesystem (internal, in-memory) containing an arbitrary se… 30 which features and scenarios are supported. 38 …allowing simulation of a complete range of both success and failure scenarios. The <CommandHandler… 45 which features and scenarios are supported. 52 for more information on which features and scenarios are supported.
|
/external/mockftpserver/MockFtpServer/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 36 FTP Scenarios Supported by FakeFtpServer 39 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 65 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 89 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 90 scenarios not supported include: 112 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/mockftpserver/tags/2.2/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 33 FTP Scenarios Supported by FakeFtpServer 36 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 62 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 86 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 87 scenarios not supported include: 109 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/mockftpserver/tags/2.5/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 36 FTP Scenarios Supported by FakeFtpServer 39 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 65 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 89 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 90 scenarios not supported include: 112 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/mockftpserver/tags/2.3/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 36 FTP Scenarios Supported by FakeFtpServer 39 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 65 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 89 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 90 scenarios not supported include: 112 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
D | fakeftpserver-versus-stubftpserver.apt | 16 …and simulation scenarios. You define a filesystem (internal, in-memory) containing an arbitrary se… 30 which features and scenarios are supported. 38 …allowing simulation of a complete range of both success and failure scenarios. The <CommandHandler… 45 which features and scenarios are supported. 52 for more information on which features and scenarios are supported.
|
/external/mockftpserver/tags/2.4/src/site/apt/ |
D | fakeftpserver-features.apt | 12 … box with reasonable and expected behavior. Can simulate most mainline success and error scenarios. 36 FTP Scenarios Supported by FakeFtpServer 39 Some of the mainline success scenarios that you can simulate with <<FakeFtpServer>> include: 65 Some of the error scenarios that you can simulate with <<FakeFtpServer>> include: 89 …Not all FTP features, error scenarios and reply codes can be simulated using <<FakeFtpServer>>. Fe… 90 scenarios not supported include: 112 …For unsupported features, error scenarios and reply codes, consider using <<StubFtpServer>> instea…
|
/external/ltp/testcases/kernel/syscalls/ulimit/ |
D | ulimit01.c | 132 } Scenarios[] = { variable 159 TST_TOTAL = sizeof(Scenarios) / sizeof(struct limits_t); in main() 180 cmd = Scenarios[i].cmd; in main() 181 limit = Scenarios[i].newlimit; in main() 190 if (Scenarios[i].exp_fail) { in main() 200 if (Scenarios[i].exp_fail) { in main() 217 if (Scenarios[tmp].nlim_flag == in main() 219 Scenarios[tmp].newlimit in main() 222 if (Scenarios[tmp].nlim_flag == in main() 224 Scenarios[tmp].newlimit in main()
|
/external/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 45 Test Case Scenarios 47 Some potential test case scenarios are listed after each functional
|
/external/rust/crates/grpcio-sys/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:
|
/external/grpc-grpc/tools/profiling/qps/ |
D | qps_diff.py | 86 def run(name, scenarios, loops): argument 87 for sn in scenarios: 90 subprocess.check_call(_run_cmd(name, scenarios[sn], fname)) 115 def diff(scenarios, loops, old, new): argument 120 for sn in scenarios: 130 for sn in scenarios:
|