| commit | 6989c2052c47c23de4c0a879efdfa4f04e0acf23 | [log] [tgz] |
|---|---|---|
| author | Mohannad Farrag <aymanm@google.com> | Tue Mar 11 12:38:49 2025 +0000 |
| committer | Mohannad Farrag <aymanm@google.com> | Wed Mar 12 06:05:03 2025 -0700 |
| tree | 2b05f244f2666706cad29419a84a07ca82f93e95 | |
| parent | c68e25cb6f77afd2549613f441ab73761c84eaa4 [diff] |
Stop overriding flags in CTS tests Overriding flags seems to be explicitly disabled as per the [documentation](https://g3doc.corp.google.com/company/teams/android-core-experiments/trunk-stable/class-and-method-level-flag-override.md?cl=head). xTS tests are supposed to be flag-agnostic which was not the case and this has caused b/402303876 to occur, the alternative here is to use flag filtering. However, we think that the tests are no longer necessary at this point due to the fact that they run the default behavior which is what the current tests already do; We removed the tests. Tested: m cts && run cts -m CtsNetHttpTestCases -t android.net.http.cts.HttpEngineTest Bug: 402303876 Change-Id: I122dfe774f35dfa4d796b20f6c488bd102bddc8d
Cronet is Chrome's networking stack packaged into a client networking library for Android. It significantly improves performance thanks to highly optimized code and support of modern protocols like QUIC and HTTP/3.
Cronet is imported through copybara from Chromium. Please do not submit any changes to this repoistory or touch the Android.bp as they are auto-generated. Contact cronet-team@ for more information
See go/cronet-structure-in-aosp for more additional details
android/ only exists in AOSP and is not imported from Chromium. This contains tools and code that is usually developed in AOSP and is not related to Chromium (eg: HttpEngine API).
This include the top-level third_party/. It's important to note that there are some third-party code that lives under first-party code (eg: QUICHE which lives under net/third_party). Those should be moved to the top-level third_party directory at some point but we will only do so once chromium has done that.
We follow the same structure which Rust follows in AOSP where the crates live under third_party/rust/chromium_crates_io/vendor but the BUILD.gn which defines the build target lives under third_party/rust/{library_name} (eg: aho-corasick). For more information, see the README.md in Chromium for Rust crates.