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
1 file changed
tree: 2b05f244f2666706cad29419a84a07ca82f93e95
  1. android/
  2. base/
  3. build/
  4. buildtools/
  5. chrome/
  6. components/
  7. crypto/
  8. ipc/
  9. net/
  10. test_runner/
  11. testing/
  12. third_party/
  13. url/
  14. Android.bp
  15. Android.extras.bp
  16. chromium.bara.consistency
  17. exclude_coverage.list
  18. LICENSE
  19. METADATA
  20. MODULE_LICENSE_BSD
  21. OWNERS
  22. PREUPLOAD.cfg
  23. README.md
  24. TEST_MAPPING
README.md

Cronet (HttpEngine)

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

Repository Layout

See go/cronet-structure-in-aosp for more additional details

AOSP-only

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).

Third-party code

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.

Rust Third-party code

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.