Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geekbench-corporate 6.3.0 - waitForResultsv3onwards is broken #1271

Open
chrisswinchatt-arm opened this issue Oct 17, 2024 · 0 comments
Open
Labels

Comments

@chrisswinchatt-arm
Copy link

chrisswinchatt-arm commented Oct 17, 2024

In wa/workloads/geekbench/uiauto/app/src/main/java/com/arm/wa/uiauto/geekbench/UiAutomation.java method UiAutomation.waitForResultsv3onwards:

The method looks for the TextView containing the word Running which is on the test progress modal. Presumably in previous versions this simply said Running so the same TextView was present for the duration of the test, but in more recent versions the text is updated with the current test stage (e.g. Running file compression) and the "update" apparently happens by removing the previous TextView and creating a new one. This results in the UI automation detecting that the test has completed early (<1s on my Pixel 6).

A, possibly non-ideal, fix is to rewrite the function like this:

    public void waitForResultsv3onwards() throws Exception {
        UiSelector selector = new UiSelector();
        UiObject runningTextView;
        while (true) {
            runningTextView = mDevice.findObject(selector.textContains("Running")
                                                        .className("android.widget.TextView"));
            if (!runningTextView.waitForExists(WAIT_TIMEOUT_5SEC)) {
                break;
            }
        }
    }

This will wait for the final Running to be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant