Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 0a19601e authored by Ady Abraham's avatar Ady Abraham
Browse files

composer: 2.4: VTS using old value for parameter 

Fix a test that is using the incorrect parameter.

Bug: 161023185
Test: adb shell data/nativetest64/VtsHalGraphicsComposerV2_4TargetTest/VtsHalGraphicsComposerV2_4TargetTest
Change-Id: I8574abed50c23657f5d96e9d396709cb9b92e1fd
parent 88990e68

graphics/composer/2.4/vts/functional/VtsHalGraphicsComposerV2_4TargetTest.cpp

+6 −6
Original line number Diff line number Diff line
@@ -493,16 +493,16 @@ void GraphicsComposerHidlCommandTest::Test_setActiveConfigWithConstraints( 
            // At this point the refresh rate should have changed already, however in rare

            // cases the implementation might have missed the deadline. In this case a new

            // timeline should have been provided.

            auto newTimelime = mComposerCallback->takeLastVsyncPeriodChangeTimeline();

            auto newTimeline = mComposerCallback->takeLastVsyncPeriodChangeTimeline();

            if (timeline.refreshRequired && refreshMiss) {

                EXPECT_TRUE(newTimelime.has_value());

                EXPECT_TRUE(newTimeline.has_value());

            }



            if (newTimelime.has_value()) {

                if (timeline.refreshRequired) {

                    sendRefreshFrame(&newTimelime.value());

            if (newTimeline.has_value()) {

                if (newTimeline->refreshRequired) {

                    sendRefreshFrame(&newTimeline.value());

                }

                waitForVsyncPeriodChange(display, newTimelime.value(), constraints.desiredTimeNanos,

                waitForVsyncPeriodChange(display, newTimeline.value(), constraints.desiredTimeNanos,

                                         vsyncPeriod1, vsyncPeriod2);

            }