WindowManager: Remove untenable tests.
SurfaceFlinger will throw an error if the WM tries to create
too large of a Surface, but there is no way to predict what this value is.
Practically it should be at least 4096x4096 but there is no guarantee.
It's not enough to query GL_MAX_TEXTURE_SIZE as we don't know what configuration
SurfaceFlinger is using. The CDD has no notes on maximum texture size.
Bug: 62685202
Bug: 63136620
Test: There are fewer now.
Change-Id: I3fd5fe417011a76078f3bc1a6c22ee076d24ea9d
(cherry picked from commit e4f7be1c29e49515ed49886ca95b573b0b643ec6)
diff --git a/hostsidetests/services/activityandwindowmanager/windowmanager/src/android/server/cts/DialogFrameTests.java b/hostsidetests/services/activityandwindowmanager/windowmanager/src/android/server/cts/DialogFrameTests.java
index 6fb5fbd..c99f001 100644
--- a/hostsidetests/services/activityandwindowmanager/windowmanager/src/android/server/cts/DialogFrameTests.java
+++ b/hostsidetests/services/activityandwindowmanager/windowmanager/src/android/server/cts/DialogFrameTests.java
@@ -131,20 +131,21 @@
// });
// }
- static final int oversizedDimension = 5000;
+ // TODO(b/63993863) : Disabled pending public API to fetch maximum surface size.
+ // static final int oversizedDimension = 5000;
// With FLAG_LAYOUT_NO_LIMITS we should get the size we request, even if its much
// larger than the screen.
- public void testOversizedDimensionsNoLimits() throws Exception {
- // TODO(b/36890978): We only run this in fullscreen because of the
- // unclear status of NO_LIMITS for non-child surfaces in MW modes
- doFullscreenTest("OversizedDimensionsNoLimits",
- (WindowState parent, WindowState dialog) -> {
- Rectangle contentFrame = parent.getContentFrame();
- Rectangle expectedFrame = new Rectangle(contentFrame.x, contentFrame.y,
- oversizedDimension, oversizedDimension);
- assertEquals(expectedFrame, dialog.getFrame());
- });
- }
+ // public void testOversizedDimensionsNoLimits() throws Exception {
+ // TODO(b/36890978): We only run this in fullscreen because of the
+ // unclear status of NO_LIMITS for non-child surfaces in MW modes
+ // doFullscreenTest("OversizedDimensionsNoLimits",
+ // (WindowState parent, WindowState dialog) -> {
+ // Rectangle contentFrame = parent.getContentFrame();
+ // Rectangle expectedFrame = new Rectangle(contentFrame.x, contentFrame.y,
+ // oversizedDimension, oversizedDimension);
+ // assertEquals(expectedFrame, dialog.getFrame());
+ // });
+ // }
// If we request the MATCH_PARENT and a non-zero position, we wouldn't be
// able to fit all of our content, so we should be adjusted to just fit the
