binderRpcWireProtocolTest: remove experimental
We are no longer testing that when the wire protocol version
is not experimental, that the experimental wire protocol
version has no changes.
Due to TARGET_RELEASE, we will never mark the 'current' or
'default' version of the wire protocol to be the experimental
version. Instead, the experimental version would stage various
changes to the wire protocol, and we'd update the default
once we want to stabilize that.
Bug: 305786304
Test: binderRpcWireProtocolTest on -next
Change-Id: Ie4db164bc00ff5980c2c10f0697a05557c752a3a
diff --git a/libs/binder/tests/binderRpcWireProtocolTest.cpp b/libs/binder/tests/binderRpcWireProtocolTest.cpp
index 642cea4..2718af6 100644
--- a/libs/binder/tests/binderRpcWireProtocolTest.cpp
+++ b/libs/binder/tests/binderRpcWireProtocolTest.cpp
@@ -263,16 +263,4 @@
}
}
-TEST(RpcWire, IfNotExperimentalCodeHasNoExperimentalFeatures) {
- if (RPC_WIRE_PROTOCOL_VERSION == RPC_WIRE_PROTOCOL_VERSION_EXPERIMENTAL) {
- GTEST_SKIP() << "Version is experimental, so experimental features are okay.";
- }
-
- // if we set the wire protocol version to experimental, none of the code
- // should introduce a difference (if this fails, it means we have features
- // which are enabled under experimental mode, but we aren't actually using
- // or testing them!)
- checkRepr(kCurrentRepr, RPC_WIRE_PROTOCOL_VERSION_EXPERIMENTAL);
-}
-
} // namespace android