Closed Bug 1594052 Opened 5 years ago Closed 4 years ago

Add Raptor tests to Geckoview Webrender

Categories

(Core :: Graphics: WebRender, enhancement, P3)

ARM64
Android
enhancement

Tracking

()

RESOLVED DUPLICATE of bug 1623421

People

(Reporter: ktaeleman, Assigned: ktaeleman)

References

(Blocks 1 open bug)

Details

(Whiteboard: wr-android)

Attachments

(1 obsolete file)

Currently talos tests are not being run on webrender.

See here:
https://searchfox.org/mozilla-central/source/taskcluster/ci/test/test-sets.yml

Priority: -- → P3
OS: Unspecified → Android
Hardware: Unspecified → ARM64
No longer blocks: wr-android-mvp
Blocks: wr-74-android
No longer blocks: wr-73-android
No longer blocks: wr-74-android

Changing this to Raptor tests as Talos tests are not run on android.

This will need to be setup so only changes to the gfx/ codepath result in running the testsuite.

Summary: Add Talos tests to Fenix Webrender → Add Raptor tests to Geckoview Webrender
  • Enabling Raptor tests on android arm7 platform with webrender
  • Adjusting schedule so we only run webrender hardware tasks when gfx/
    fileset changes.
Assignee: nobody → ktaeleman
Status: NEW → ASSIGNED

(In reply to Kris Taeleman (:ktaeleman) from comment #2)

  • Enabling Raptor tests on android arm7 platform with webrender

We recently moved most tests on android-hw P2's from the arm7 build to the aarch64 build, reasoning that 64-bit builds are much more likely on the P2; do the webrender tests need to run against arm7 builds?

Yes, I saw that I had a merge conflict, these can move to aarch64 as well, I will do that once we there is a plan to move forward with these tests on android-hw.

it is my understanding that webrender is not a big focus on Android until Fenix is successfully shipped, then focus will be back on webrender.

We do need to pick and choose what will be the right value.

In this patch, I see reference to reftest/crashtest, I think we can optimize those in bug 1621095.

I would prefer that we run webrender tests for unittests on android and not duplicated with non webrender. At least for hardware. When it comes to perf, keeping our runs to mozilla-central only would be ideal and on pixel2/aarch64 only (to reduce the duplication).

I am happy to think of other scenarios or shift things if my ideas are half baked.

Blocks: wr-android
Whiteboard: wr-android
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Attachment #9127681 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: