kc3-lang/angle/infra

Diff

  • Show log

    Commit

  • Hash : b778f1ce
    Author : Yuly Novikov
    Date : 2025-08-07T15:31:01 

    Balance test shards to 10 minutes

Shards increased due to googletest roll:
angle_end2end_tests on Win ASAN: 10 -> 14
angle_deqp_gles3_tests on Linux ASAN and TSAN: 8 -> 11

Drive-by shards increase for slowness which was not investigated:
angle_end2end_tests:
  on Linux Intel and Windows and Linux NVIDIA: 2 -> 3
  on Win Intel experiment (UHD 770, 2 processes): 3 -> 5
  on Win Intel (UHD 630, 1 process): 4 -> 10
angle_restricted_trace_gold_tests
  on Linux Intel and Windows and Linux NVIDIA: 1 -> 3
  on Win Intel UHD 770: 1 -> 4
  on Win Intel UHD 630: 1 -> 5
angle_trace_perf_vulkan_tests
  on Win Intel UHD 770: 2 -> 4
  on Win Intel UHD 630: 2 -> 3

Skip EGLDisplayTest.ContextLeakAfterTerminate on Linux Intel,
which started failing with the new sharding.

Bug: angleproject:428697844, angleproject:437259106
Change-Id: I3ba458aa7b68bddf9786bb9fcbc2a3ed7479556c
Reviewed-on: https://chromium-review.googlesource.com/c/angle/angle/+/6827389
Auto-Submit: Yuly Novikov <ynovikov@chromium.org>
Reviewed-by: Cody Northrop <cnorthrop@google.com>
Commit-Queue: Cody Northrop <cnorthrop@google.com>

  • Properties

  • Git HTTP https://git.kmx.io/kc3-lang/angle.git
    Git SSH git@git.kmx.io:kc3-lang/angle.git
    Public access ? public
    Description

    A conformant OpenGL ES implementation for Windows, Mac, Linux, iOS and Android.

    Homepage

    Github
    Users
    		 thodg_m kc3_lang_org thodg_w www_kmx_io thodg thodg_l
    Tags

  • README.md

  • ANGLE Testing Infrastructure

    ANGLE runs hundreds of thousands of tests on every change before it lands in the tree. We scale our pre-commit and post-commit testing to many machines using Chromium Swarming. Our testing setup heavily leverages existing work in Chromium. We also run standalone testing that does not depend on a Chromium checkout.

    Pre-Commit Testing

    We have pre-commit testing on Chromium and ANGLE try waterfalls.

    We currently run pre-commit tests on:

    • Windows 64-bit Intel and NVIDIA GPUs and SwiftShader on VMs
    • Windows 32-bit on SwiftShader on VMs
    • Linux 64-bit Intel and NVIDIA GPUs and SwiftShader on VMs
    • Mac NVIDIA, Intel and AMD GPUs
    • Pixel 2, Pixel 4 and Pixel 6
    • Fuchsia compile-only
    • iOS simulator on demand

    Looking at an example build shows how tests are split up between machines. See for example:

    https://ci.chromium.org/ui/p/angle/builders/ci/mac-test/8117/overview

    This build ran 67 test steps across 3 GPU families. In some cases (e.g. angle_deqp_gles3_metal_tests) the test is split up between multiple machines to run faster (in this case 2 different machines at once). This build took 10 minutes to complete 50 minutes of real automated testing.

    For more details on running and working with our test sets see the docs in Contributing Code.

    Post-Commit Testing

    Similarly to pre-commit testing, there are also Chromium and ANGLE CI (Continuous Integration) waterfalls. These run on the same configurations as pre-commit, plus additional configurations for which we only have limited HW, e.g. Samsung S22 phones. They are useful for detecting flaky failures and for regression blamelists in case some failure does manage to slip through pre-commit testing.

    Auto-Rollers

    Some ANGLE dependencies are rolled in via automatically created CLs by these auto-rollers:

    Similarly, Chromium’s copy of ANGLE is updated by the ANGLE into Chromium auto-roller. And there also exists a SwiftShader into Chromium auto-roller.

kmx.io     mail     discord kmxgit v0.4.0