30ef1bf331d251fce77e0a7a9a5c3ea9c638d32f |
|
25-Apr-2018 |
Lloyd Pique <lpique@google.com> |
Allow the window to be recreated in the middle of a test On ARC++ devices, some of the dEQP CTS tests were occasionally failing on devices running in tablet mode, due to the timing of a WM relayout that happens shortly after the orientation change is realized. We traced it back to the dEQP test harness always expecting to see a call from the system to onNativeWindowResized() after a call to oNNativeWindowCreated(). It happened that the relayout on ARC++ devices was not causing a size change, so this message was never received. The result was that the test paused itself, and never completed. The watchdog thread that the test harness creates ended up killing and failing the test. This patch adjusts the logic so that the activity only waits to process the window creation for the very first call to onNativeWindowResized(), as when the activity is first created that call is indeed made (but note not really guaranteed). A subsequent call to onNativeWindowCreated() will unpause the test (setting the READY state), as well as finish processing the window creation. Bug: 74371892 Test: dEQP-GLES3.functional.prerequisite#clear_color Change-Id: I3c429aea272cbfee3f150a32c12233c9f38a7936
/external/deqp/framework/platform/android/tcuAndroidRenderActivity.cpp
|
fd1df7eaea78d2c9c6bdb3da51d5f1255c479694 |
|
23-Oct-2014 |
Pyry Haulos <phaulos@google.com> |
Remove invalid assert from RenderActivity::setThread() It is valid to call setThread() with null thread as part of activity teardown, so the assert was invalid. Change-Id: I0b3a89db1f5aff04c97def32b1881e0d66e5d250
/external/deqp/framework/platform/android/tcuAndroidRenderActivity.cpp
|
217426c2d19d5247e094e363615d7a0b84daf3a7 |
|
02-Oct-2014 |
Pyry Haulos <phaulos@google.com> |
Make Android integration more robust for API >= 11 Recent targetSdkLevel bump exposed robustness issues in the Android port which were hidden by pre-honeycomb workarounds in android.app.ActivityThread. For honeycomb and up when launching activity with lockscreen on or screen off the system for some reason first starts the activity once, puts it back to stopped state and then resumes again. Original Android port assumed that stop event signaled that the test execution should always stop and process should kill itself. This might have been necessary workaround on some older Android versions where onDestroy was never called even if app called finish(). This commit improves Android integration in multiple ways: * Android port can continue test execution even across stop-start boundary in the Activity life-cycle. * eglu::GLRenderContext can recover from window loss by recreating the window if NativeWindow::postIterate() throws WindowDestroyedError. * eglu::GLRenderContext refreshes window surface size in postIterate() call. Note that most test cases might not like if surface is resized during execution though. * Temporary window loss (recreation) no longer leads to test run abort, but rather Android NativeWindow correctly signals that event allowing eglu::GLRenderContext to recover. Change-Id: Iaa240f16a2ae6cea7fb894c5772d1e7959a1cfac
/external/deqp/framework/platform/android/tcuAndroidRenderActivity.cpp
|
67e56c9a76571b87c58a174bdad44fa1425d40fe |
|
30-Sep-2014 |
Pyry Haulos <phaulos@google.com> |
Clean up msg queue implementation in RenderActivity tcu::Android::Message type (which RenderActivity uses to communicate with the render thread) didn't validate payload type against the message type. This change fixes that. Change-Id: I2f120783e4f1bb5b7d0122bb8849c429577c267c
/external/deqp/framework/platform/android/tcuAndroidRenderActivity.cpp
|
3c827367444ee418f129b2c238299f49d3264554 |
|
02-Sep-2014 |
Jarkko Poyry <jpoyry@google.com> |
Import dEQP. Import drawElements Quality Program from an internal repository. Bug: 17388917 Change-Id: Ic109fe4a57e31b2a816113d90fbdf51a43e7abeb
/external/deqp/framework/platform/android/tcuAndroidRenderActivity.cpp
|