Chiebot-Mirror/grpc - grpc - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Craig Tiller	621aa4e5ce	[call-v3] Yodel - a call testing framework (#36635 ) Introduce "Yodel" - a framework for testing things vaguely related to calls. This is breaking up some work I did for transport test suites - we've got a nice way of spawning test-only promises and tracking them visually, and support for setting up an environment that can run as a test or a fuzzer. I'm making that piece a little more reusable, and then rebasing the transport test suite atop that infrastructure. Closes #36635 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/36635 from ctiller:transport-refs-6 `843a9f4b7e` PiperOrigin-RevId: 637022756	7 months ago
Mark D. Roth	0944410d6c	[reorg] move test/core/util -> test/core/test_util (#36446 ) Closes #36446 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/36446 from markdroth:reorg_test `5dcc85e006` PiperOrigin-RevId: 629229220	8 months ago
Craig Tiller	1751f1043e	[transport] Add a transport test suite for promise based transports (#35476 ) Implemented for inproc & chaotic-good Closes #35476 COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/35476 from ctiller:v3-svall `5358538d54` PiperOrigin-RevId: 599701775	11 months ago
Craig Tiller	7a3e2e45da	[fuzzer] Change core_end2end_test_fuzzer test selection scheme (#33197 ) Use an index instead of a string to select tests (and use that index module total test count to ensure whatever the fuzzer selects we always run a test). This will make the fuzzer corpus unstable when the test count changes, which I think is fine - it'll regenerate. <!-- If you know who should review your pull request, please assign it to that person, otherwise the pull request would get assigned randomly. If your pull request is for a specific language, please add the appropriate lang label. -->	2 years ago
Craig Tiller	4674f2ccf7	[fuzz] Turn core end2end tests into fuzzers (#33013 ) Add a new binary that runs all core end2end tests in fuzzing mode. In this mode FuzzingEventEngine is substituted for the default event engine. This means that time is simulated, as is IO. The FEE gets control of callback delays also. In our tests the `Step()` function becomes, instead of a single call to `completion_queue_next`, a series of calls to that function and `FuzzingEventEngine::Tick`, driving forward the event loop until progress can be made. PR guide: --- New binaries `core_end2end_test_fuzzer` - the new fuzzer itself `seed_end2end_corpus` - a tool that produces an interesting seed corpus Config changes for safe fuzzing The implementation tries to use the config fuzzing work we've previously deployed in api_fuzzer to fuzz across experiments. Since some experiments are far too experimental to be safe in such fuzzing (and this will always be the case): - a new flag is added to experiments to opt-out of this fuzzing - a new hook is added to the config system to allow variables to re-write their inputs before setting them during the fuzz Event manager/IO changes Changes are made to the event engine shims so that tcp_server_posix can run with a non-FD carrying EventEngine. These are in my mind a bit clunky, but they work and they're in code that we expect to delete in the medium term, so I think overall the approach is good. Changes to time A small tweak is made to fix a bug initializing time for fuzzers in time.cc - we were previously failing to initialize `g_process_epoch_cycles` Changes to `Crash` A version that prints to stdio is added so that we can reliably print a crash from the fuzzer. Changes to CqVerifier Hooks are added to allow the top level loop to hook the verification functions with a function that steps time between CQ polls. Changes to end2end fixtures State machinery moves from the fixture to the test infra, to keep the customizations for fuzzing or not in one place. This means that fixtures are now just client/server factories, which is overall nice. It did necessitate moving some bespoke machinery into h2_ssl_cert_test.cc - this file is beginning to be problematic in borrowing parts but not all of the e2e test machinery. Some future PR needs to solve this. A cq arg is added to the Make functions since the cq is now owned by the test and not the fixture. Changes to test registration `TEST_P` is replaced by `CORE_END2END_TEST` and our own test registry is used as a first depot for test information. The gtest version of these tests: queries that registry to manually register tests with gtest. This ultimately changes the name of our tests again (I think for the last time) - the new names are shorter and more readable, so I don't count this as a regression. The fuzzer version of these tests: constructs a database of fuzzable tests that it can consult to look up a particular suite/test/config combination specified by the fuzzer to fuzz against. This gives us a single fuzzer that can test all 3k-ish fuzzing ready tests and cross polinate configuration between them. Changes to test config The zero size registry stuff was causing some problems with the event engine feature macros, so instead I've removed those and used GTEST_SKIP in the problematic tests. I think that's the approach we move towards in the future. Which tests are included Configs that are compatible - those that do not do fd manipulation directly (these are incompatible with FuzzingEventEngine), and those that do not join threads on their shutdown path (as these are incompatible with our cq wait methodology). Each we can talk about in the future - fd manipulation would be a significant expansion of FuzzingEventEngine, and is probably not worth it, however many uses of background threads now should probably evolve to be EventEngine::Run calls in the future, and then would be trivially enabled in the fuzzers. Some tests currently fail in the fuzzing environment, a `SKIP_IF_FUZZING` macro is used for these few to disable them if in the fuzzing environment. We'll burn these down in the future. Changes to fuzzing_event_engine Changes are made to time: an exponential sweep forward is used now - this catches small time precision things early, but makes decade long timers (we have them) able to be used right now. In the future we'll just skip time forward to the next scheduled timer, but that approach doesn't yet work due to legacy timer system interactions. Changes to port assignment: we ensure that ports are legal numbers before assigning them via `grpc_pick_port_or_die`. A race condition between time checking and io is fixed. --------- Co-authored-by: ctiller <ctiller@users.noreply.github.com>	2 years ago
Yijie Ma	1d10ca77ce	[Fuzzing] Migrate client and server_fuzzer to structured fuzzing (#32878 ) - Added `fuzzer_input.proto` and `NetworkInput` proto message - Migrated client_fuzzer and server_fuzzer to proto fuzzer - Migrated the existing corpus and verified that the code coverage (e.g. chttp2) stays the same Probably need to cherrypick due to amount of files changed. <!-- If you know who should review your pull request, please assign it to that person, otherwise the pull request would get assigned randomly. If your pull request is for a specific language, please add the appropriate lang label. -->	2 years ago
Craig Tiller	33aaa55032	Filter fuzzer (#29177 ) * begin * tests * fix * http * Filter fuzzer * progress * basics * progress * Automated change: Fix sanity tests * Automated change: Fix sanity tests * Revert "Revert "HTTP Client Filter --> promises (#29031)" (#29181)" This reverts commit `6ee276f672`. * stuff * debug * minimal reproduction * progress * progress * create call * progress * recv trailing metadata * wakeups * corpus * Automated change: Fix sanity tests * Automated change: Fix sanity tests * debug * fix state machine for c# * Revert "minimal reproduction" This reverts commit `4d02d2e730`. * Revert "debug" This reverts commit `7960842f48`. * Revert "debug" This reverts commit `a6f224e4a1`. * no-logging * initial-metadata * Revert "Revert "debug"" This reverts commit `951844e857`. * Better int conversion * debug * Fix for Cronet * Revert "debug" This reverts commit `4d641c4281`. * Revert "Better int conversion" This reverts commit `4001b957cb`. * Revert "Revert "Revert "debug""" This reverts commit `d135c61043`. * progress * progress * Automated change: Fix sanity tests * fix, c++ize * handle transport, use objects * enable more stuffs * remove placeholder * contexts * fix * fix * Automated change: Fix sanity tests * Automated change: Fix sanity tests * x * exceptional toast * include idle filters, time * fix * namespace * fixes * final info * progress * Automated change: Fix sanity tests * fix * fix * combine cases Co-authored-by: ctiller <ctiller@users.noreply.github.com> Co-authored-by: Jan Tattermusch <jtattermusch@google.com>	3 years ago
AJ Heller	5ef1585070	A more granular EventEngine conformance test suite (#28889 ) This allows implementers to select which subset of the conformance test suite they wish to exercise with their implementation. This was a request from the fuchsia team, and may be useful for partial implementations that are composed into a complete EventEngine solution.	3 years ago
Jan Tattermusch	57139d1eef	fix C# codegen for empty service	7 years ago
Daniel Neighman	8b7007ad7b	Updates the ruby generator RubyAsType to correctly account for underscores in packages Prior to this change, when the ruby generator tried to reference an entity that was not part of the same package (or a direct parent package) and the package contains underscores, the result would simply uppercase the first character. It should however uppercase each letter that proceeds an underscore and remove underscores. i.e. ``` package my_package.service; import "my_package/data.proto"; service MyService { rpc Test (data.Request) returns data.Response {} } ``` Was ```ruby # ... rpc :Test, My_package::Data::REquest, My_package::Data::Response # ... ``` Should be: ```ruby # ... rpc :Test, MyPackage::Data::REquest, My_package::Data::Response # ... ```	7 years ago
Nathaniel Manista	719ade3cdc	Overhaul protoc_plugins._split_definitions_test We were mistaken before when we were testing _pb2.py files being generated in one directory and _pb2_grpc.py files being generated in another directory. Sure, that was a thing our code generator could do, but because of the way paths and packages work in Python it wasn't a realistic use case for actual users. This test now tests _pb2.py files and _pb2_grpc.py files being generated either together or independently of one another, and if independently, in either order. Looking forward to an eventual py_grpc_library Bazel rule, that's what actually matters.	7 years ago
Jan Tattermusch	7897ae9308	auto-fix most of licenses	8 years ago
Masood Malekghassemi	53360f2d1c	Backport Python features to 1.0.x Backports per-object grpc_init/deinit and separated-file grpc protoc codegen (#7538, #8246, #8920).	8 years ago
Craig Tiller	6169d5f7b0	Update copyrights	9 years ago
David Garcia Quintas	3c1720c984	Updated copyrights...	9 years ago
David Garcia Quintas	45484b31bb	Added sanity check for trailing newlines	9 years ago
murgatroid99	5828fb960d	Added failing test that echos the request message	10 years ago
Jan Tattermusch	503bbac217	added C# interop server	10 years ago
Craig Tiller	ce5021b0b9	Add missing new-lines at end of file	10 years ago
Craig Tiller	ad1fd3a49e	Add proto copyrights	10 years ago
yangg	1456d15221	Add a test to export two TestService on the same server, only with different package names. Make sure they work as intended. This is based on [] Change on 2015/01/08 by yangg <yangg@google.com> ------------- Created by MOE: http://code.google.com/p/moe-java MOE_MIGRATED_REVID=83558743	10 years ago

1 Commits (f9fdab56571feee205c591ffd4da62f3238f4e52)