commit | ee0b826893eb9451ad4b0ebbbba93039297831c0 | [log] [tgz] |
---|---|---|
author | Fei Shao <fshao@chromium.org> | Mon May 09 05:18:17 2022 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 11 09:14:15 2022 |
tree | ca64dce21ca9ab0520a8ae185d89290d75fc1e23 | |
parent | 67bc8aae5c1f893a07cb6564f84a74f15cc17c2b [diff] |
Update reference images for fill_tex_trilinear_linear tests Update the reference images generated by Mali Valhall r32p0 on MT8192 and MT8195 boards. BUG=b:231906100 TEST=tast run $DUT-TOMATO graphics.GLBench TEST=update_glbench_image_filelists.sh Change-Id: I3e385f68585effbaca99ad3c0e4fb755cd155991 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/glbench/+/3631107 Reviewed-by: Ilja Friedel <ihf@chromium.org> Auto-Submit: Fei Shao <fshao@chromium.org> Commit-Queue: Fei Shao <fshao@chromium.org> Tested-by: Fei Shao <fshao@chromium.org> Reviewed-by: Po-Hsien Wang <pwang@chromium.org>
GLBench runs OpenGL or OpenGL ES microbenchmarks and writes performance numbers to stdout and resulting images to a directory for verification.
For the test to pass the performance numbers have to be better than a predefined threshold, while the resulting images have to be found in a repository of reference images. As the image name encodes the raw pixel MD5 this can be done as a simple file existence check. If we ever get too much pixel variation using a tool like perceptualdiff to waive small differences should be acceptable.
It might be easier to develop new tests under Linux:
sudo apt-get install libgflags-dev sudo apt-get install libwaffle-dev sudo apt-get install waffle-utils (optional) make
./glbench -notemp [-save [-outdir=<directory>]]
./glbench -save -outdir=img # board_id: NVIDIA Corporation - Quadro FX 380/PCI/SSE2 swap_swap = 214.77 us [swap_swap.pixmd5-20dbc406b95e214a799a6a7f9c700d2f.png] clear_color = 4448.28 mpixels_sec [clear_color.pixmd5-e3609de1022a164fe240a562c69367de.png] clear_depth = 10199.76 mpixels_sec [clear_depth.pixmd5-e3609de1022a164fe240a562c69367de.png] clear_colordepth = 3250.57 mpixels_sec [clear_colordepth.pixmd5-e3609de1022a164fe240a562c69367de.png] clear_depthstencil = 26447.22 mpixels_sec [clear_depthstencil.pixmd5-e3609de1022a164fe240a562c69367de.png] [...] ls img clear_color.pixmd5-e3609de122a164fe240a562c69367de.png clear_colordepth.pixmd5-e3609de122a164fe240a562c69367de.png clear_colordepthstencil.pixmd5-e3609de122a164fe240a562c69367de.png compositing.pixmd5-7d02a16a7ac15cd6cbbc5c786f1.png [...]
Running the autotest test_that $DUT graphics_GLBench will \
Good reference images themselves are located at ./ref_images/glbench_reference_images/
Images that have outstanding defects and an open bug filed are at ./ref_images/glbench_knownbad_images/chromium-bug-NNNNN/
When that bug is closed the directory should be moved to ./ref_images/glbench_fixedbad_images/chromium-bug-NNNNN/ \
To push out new reference images place them in the appropriate directories (create a new bug if needed) and run ./update_glbench_image_filelists.sh to update the image filelists.