aboutsummaryrefslogtreecommitdiffhomepage
path: root/infra/bots/recipes/test.expected/Test-Android-Clang-Nexus5x-GPU-Adreno418-arm64-Debug-All-Android_NoGPUThreads.json
Commit message (Collapse)AuthorAge
* Shuffle jobs off Nexus5x.Gravatar Ben Wagner2018-07-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All Golo devices except 2 are AWOL. We added 6 to the Skolo, but they can't keep up. This CL moves the following jobs off Nexus5x: - All ASAN jobs to Pixel. Most other devices we have can't be rooted, so they can't run ASAN. - Vulkan NoGPUThreads arm64 jobs to NVIDIA_Shield. Of the devices that support Vulkan, this has the most available capacity. - I removed the arm32 Vulkan NoGPUThreads jobs because it seems a bit esoteric. - Also removed arm32 Vulkan Debug Perf because I can't imagine it would ever give us info that arm64 doesn't already provide. (We ignore Perf data from Debug builds.) - Other arm32 Vulkan jobs stayed on Nexus5x because we don't have any other Vulkan-capable devices with spare capacity. - Most arm32 jobs to MotoG4 and de-duplicated. This device has an ARMv8 processor but runs everything in arm32 mode, which is exactly what these jobs are trying to test. We have a bunch of MotoG4s in the Skolo; however, they don't support Vulkan or ASAN. - NoGPUThreads and NativeFonts arm64 jobs to GalaxyS6. There are only 6 in the Skolo, but for some reason these devices are particularly fast. They also don't support Vulkan or ASAN. - Currently GalaxyS6 CPU arm64 jobs fail, possibly due to OOM. I will try to move those jobs in a future CL. Sorted jobs.json. Change-Id: If02584a9c04906f4b9c31b4ba3f1da0289a5b8a9 Reviewed-on: https://skia-review.googlesource.com/141281 Commit-Queue: Joe Gregorio <jcgregorio@google.com> Auto-Submit: Ben Wagner <benjaminwagner@google.com> Reviewed-by: Joe Gregorio <jcgregorio@google.com>
* [infra] Determine Android device location based on bot IDGravatar Eric Boren2018-07-10
| | | | | | | | Bug: skia: Change-Id: Ic68bbca59c2fd5d0ffd9bae29fe0f90e090e8b06 Reviewed-on: https://skia-review.googlesource.com/140342 Reviewed-by: Kevin Lubick <kjlubick@google.com> Reviewed-by: Joe Gregorio <jcgregorio@google.com>
* Revert "Update GPU DM/nanobench configs for color testing"Gravatar Brian Osman2018-06-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 5e11777a06d591c1e6ab0523e9c7f4739e164609. Reason for revert: Bots with no F16 support failing (as expected). Original change's description: > Update GPU DM/nanobench configs for color testing > > - Rename '*srgbnl' to '*srgb'. > - Add '*narrow' and '*enarrow' for testing a gamut narrower than sRGB. > - Stopped blacklisting glessrgb. It no longer uses sRGB pixel configs, > so should work fine on all GPUs. > - Also runs 'esrgb' (F16 sRGB) everywhere. This is likely to fail on > some devices that have poor (or no) F16 support. > > Change-Id: I941d0758adb3b0c895c7a8a85ff0ae4aa5bff6e7 > Reviewed-on: https://skia-review.googlesource.com/136171 > Commit-Queue: Brian Osman <brianosman@google.com> > Reviewed-by: Brian Salomon <bsalomon@google.com> > Reviewed-by: Mike Klein <mtklein@google.com> TBR=mtklein@google.com,bsalomon@google.com,brianosman@google.com Change-Id: I091269b93bc9e76c9d42f701d2018610b9c33a89 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://skia-review.googlesource.com/136300 Reviewed-by: Brian Osman <brianosman@google.com> Commit-Queue: Brian Osman <brianosman@google.com>
* Update GPU DM/nanobench configs for color testingGravatar Brian Osman2018-06-20
| | | | | | | | | | | | | | | - Rename '*srgbnl' to '*srgb'. - Add '*narrow' and '*enarrow' for testing a gamut narrower than sRGB. - Stopped blacklisting glessrgb. It no longer uses sRGB pixel configs, so should work fine on all GPUs. - Also runs 'esrgb' (F16 sRGB) everywhere. This is likely to fail on some devices that have poor (or no) F16 support. Change-Id: I941d0758adb3b0c895c7a8a85ff0ae4aa5bff6e7 Reviewed-on: https://skia-review.googlesource.com/136171 Commit-Queue: Brian Osman <brianosman@google.com> Reviewed-by: Brian Salomon <bsalomon@google.com> Reviewed-by: Mike Klein <mtklein@google.com>
* [recipes] Simplify test/perf dirsGravatar Eric Boren2018-06-20
| | | | | | | | Bug: skia:6473 Change-Id: Iee2f195ddf4bbcdabc1580f2a021d2e9a07ff0b2 Reviewed-on: https://skia-review.googlesource.com/133441 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
* Reland [recipes] Isolate build outputs with no subdirsGravatar Eric Boren2018-06-01
| | | | | | | | Bug: skia:6473 Change-Id: I730cb860abc72473aaa9af98527fd220b9a55120 Reviewed-on: https://skia-review.googlesource.com/131389 Reviewed-by: Ben Wagner <benjaminwagner@google.com> Commit-Queue: Eric Boren <borenet@google.com>
* Revert "[recipes] Isolate build outputs with no subdirs"Gravatar Eric Boren2018-06-01
| | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 0c9d2805e81e15e3afdf7ebcdc030771dbe7750b. Reason for revert: Broke iOS and SwiftShader (and maybe others) Original change's description: > [recipes] Isolate build outputs with no subdirs > > Bug: skia:6473 > Change-Id: If243b6afb748529d2bdb212e360cd4338edc929c > Reviewed-on: https://skia-review.googlesource.com/130942 > Reviewed-by: Ben Wagner <benjaminwagner@google.com> > Commit-Queue: Eric Boren <borenet@google.com> TBR=borenet@google.com,benjaminwagner@google.com Change-Id: Icf9490f2f88dc454c6d971f35258e219137b0c0e No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: skia:6473 Reviewed-on: https://skia-review.googlesource.com/131400 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Eric Boren <borenet@google.com>
* [recipes] Isolate build outputs with no subdirsGravatar Eric Boren2018-06-01
| | | | | | | | Bug: skia:6473 Change-Id: If243b6afb748529d2bdb212e360cd4338edc929c Reviewed-on: https://skia-review.googlesource.com/130942 Reviewed-by: Ben Wagner <benjaminwagner@google.com> Commit-Queue: Eric Boren <borenet@google.com>
* Specify the ADB keys to use for ADBGravatar Kevin Lubick2018-05-17
| | | | | | | | | | | | | | | In the golo, specifically, the adb keys used by swarming are different than those used in the docker instance, unless configured otherwise. This means swarming can think a device is ready (authorized) but the adb we called was not (authorized) BUG: 843284 Change-Id: I697d5075258a176e7fc7a4b51a9e2c926e1b8fd0 Reviewed-on: https://skia-review.googlesource.com/128930 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
* [recipes] BUILDTYPE and SKIA_OUT are no longer usedGravatar Eric Boren2018-05-15
| | | | | | | | | Bug: skia:6473 Change-Id: I67b0dbf6dba26233df1d8e44f3e2f69ca0cc9d3e Reviewed-on: https://skia-review.googlesource.com/128320 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Stephan Altmueller <stephana@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
* [recipes] Remove core.setup()Gravatar Eric Boren2018-05-04
| | | | | | | | | | Each recipe now includes its own setup steps. Bug: skia:6473 Change-Id: I97eab2cd63f5004c07408e844cbbed735aac355f Reviewed-on: https://skia-review.googlesource.com/125660 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com>
* Reland "[infra] Run recipes through Kitchen"Gravatar Eric Boren2018-04-19
| | | | | | | | Bug: skia:7050 Change-Id: Icf0bcfbbc505c90a4e8cee7437037a3037bdf33b Reviewed-on: https://skia-review.googlesource.com/121781 Reviewed-by: Ben Wagner <benjaminwagner@google.com> Commit-Queue: Eric Boren <borenet@google.com>
* Revert "Reland "[infra] Run recipes through Kitchen""Gravatar Eric Boren2018-04-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit f39bbe5a31542396a8aabf8066ee46862312d7d8. Reason for revert: Broke lots of bots Original change's description: > Reland "[infra] Run recipes through Kitchen" > > Bug: skia:7050 > Change-Id: I331014c408dd5b6f7baafd78ffd12f1235c5bfe7 > Reviewed-on: https://skia-review.googlesource.com/121481 > Commit-Queue: Eric Boren <borenet@google.com> > Reviewed-by: Ben Wagner <benjaminwagner@google.com> > Reviewed-by: Ravi Mistry <rmistry@google.com> TBR=borenet@google.com,benjaminwagner@google.com,rmistry@google.com Change-Id: I4548c66a9cb0b4f105e2bc3b1c7185d14549172f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: skia:7050 Reviewed-on: https://skia-review.googlesource.com/121463 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Eric Boren <borenet@google.com>
* Reland "[infra] Run recipes through Kitchen"Gravatar Eric Boren2018-04-17
| | | | | | | | | Bug: skia:7050 Change-Id: I331014c408dd5b6f7baafd78ffd12f1235c5bfe7 Reviewed-on: https://skia-review.googlesource.com/121481 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Ben Wagner <benjaminwagner@google.com> Reviewed-by: Ravi Mistry <rmistry@google.com>
* Revert "[infra] Run recipes through Kitchen"Gravatar Eric Boren2018-04-16
| | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 7bbb26fee0dcd7c53c1f5b80f62966654dd823ba. Reason for revert: uploads broke task scheduler Original change's description: > [infra] Run recipes through Kitchen > > Bug: skia:7050 > Change-Id: I50632444eb4ca7f9ae2b1b30b766e531092ccad4 > Reviewed-on: https://skia-review.googlesource.com/82500 > Commit-Queue: Eric Boren <borenet@google.com> > Reviewed-by: Ravi Mistry <rmistry@google.com> TBR=borenet@google.com,rmistry@google.com Change-Id: Ic3a5404fde844f01eca551d50039a84a20e84e11 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: skia:7050 Reviewed-on: https://skia-review.googlesource.com/121423 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Eric Boren <borenet@google.com>
* [infra] Run recipes through KitchenGravatar Eric Boren2018-04-16
| | | | | | | | Bug: skia:7050 Change-Id: I50632444eb4ca7f9ae2b1b30b766e531092ccad4 Reviewed-on: https://skia-review.googlesource.com/82500 Commit-Queue: Eric Boren <borenet@google.com> Reviewed-by: Ravi Mistry <rmistry@google.com>
* [recipes] Add asset_version utility function.Gravatar Ben Wagner2018-03-20
| | | | | | | | Bug: skia:7720 Change-Id: I044ca5281354b21c9deffa408ad7ec20c51d2e2e Reviewed-on: https://skia-review.googlesource.com/115122 Reviewed-by: Eric Boren <borenet@google.com> Commit-Queue: Ben Wagner <benjaminwagner@google.com>
* Make sure we get the LITTLE cores out of powersaveGravatar Kevin Lubick2017-12-19
| | | | | | | | | Bug: skia:7420 NOTRY=true Change-Id: I785135a3abc17f63d715d459668c768a6014d9b3 Reviewed-on: https://skia-review.googlesource.com/87001 Reviewed-by: Ravi Mistry <rmistry@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
* Revert "Revert "Disable extra CPUs during Nanobench""Gravatar Kevin Lubick2017-12-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 43307c09b97c5a5c5174f0c4ccb79bdaf3ebf557. Reason for revert: Fixed this time. Echo 1 > already online cpu returns exit code 1, which makes python over-react. Original change's description: > Revert "Disable extra CPUs during Nanobench" > > This reverts commit 32af335e7abbf562dad8f1bd21bb013610b8b021. > > Reason for revert: many unhappy android bots > > Original change's description: > > Disable extra CPUs during Nanobench > > > > The previous experiment revealed that nanobench can > > run on any of the online CPUs, so rather than put > > the ones we don't need/want into powersave mode, just > > disable them. > > > > Maybe in the future we can run CPU tests on the big > > or LITTLE cpus to get perf data on higher end or > > lower end cpus, but only if we get very stable > > results from this. > > > > Bug: skia:7378 > > Change-Id: I057513a691093e7f73c0f5790e17fab1a5ec0bc4 > > Reviewed-on: https://skia-review.googlesource.com/84820 > > Reviewed-by: Kevin Lubick <kjlubick@google.com> > > Commit-Queue: Kevin Lubick <kjlubick@google.com> > > TBR=borenet@google.com,mtklein@google.com,kjlubick@google.com > > Change-Id: I23c37a6bde631e95f0b4ae7277ec8fcf325a00e9 > Bug: skia:7378 > Reviewed-on: https://skia-review.googlesource.com/84921 > Reviewed-by: Mike Klein <mtklein@google.com> > Commit-Queue: Mike Klein <mtklein@google.com> No-Tree-Checks: true Change-Id: Ie7f0a3dc6ba55c124c796aba16a0f0497f285f3a Bug: skia:7378 Reviewed-on: https://skia-review.googlesource.com/84865 Commit-Queue: Kevin Lubick <kjlubick@google.com> Reviewed-by: Kevin Lubick <kjlubick@google.com> Reviewed-by: Mike Klein <mtklein@google.com>
* Revert "Disable extra CPUs during Nanobench"Gravatar Mike Klein2017-12-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 32af335e7abbf562dad8f1bd21bb013610b8b021. Reason for revert: many unhappy android bots Original change's description: > Disable extra CPUs during Nanobench > > The previous experiment revealed that nanobench can > run on any of the online CPUs, so rather than put > the ones we don't need/want into powersave mode, just > disable them. > > Maybe in the future we can run CPU tests on the big > or LITTLE cpus to get perf data on higher end or > lower end cpus, but only if we get very stable > results from this. > > Bug: skia:7378 > notry=true > notreechecks=true > Change-Id: I057513a691093e7f73c0f5790e17fab1a5ec0bc4 > Reviewed-on: https://skia-review.googlesource.com/84820 > Reviewed-by: Kevin Lubick <kjlubick@google.com> > Commit-Queue: Kevin Lubick <kjlubick@google.com> TBR=borenet@google.com,mtklein@google.com,kjlubick@google.com Change-Id: I23c37a6bde631e95f0b4ae7277ec8fcf325a00e9 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: skia:7378 Reviewed-on: https://skia-review.googlesource.com/84921 Reviewed-by: Mike Klein <mtklein@google.com> Commit-Queue: Mike Klein <mtklein@google.com>
* Disable extra CPUs during NanobenchGravatar Kevin Lubick2017-12-14
| | | | | | | | | | | | | | | | | | | | The previous experiment revealed that nanobench can run on any of the online CPUs, so rather than put the ones we don't need/want into powersave mode, just disable them. Maybe in the future we can run CPU tests on the big or LITTLE cpus to get perf data on higher end or lower end cpus, but only if we get very stable results from this. Bug: skia:7378 notry=true notreechecks=true Change-Id: I057513a691093e7f73c0f5790e17fab1a5ec0bc4 Reviewed-on: https://skia-review.googlesource.com/84820 Reviewed-by: Kevin Lubick <kjlubick@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
* Fix scaling logic for NexusPlayer and AndroidOneGravatar Kevin Lubick2017-12-12
| | | | | | | | | | | | They seem to be their own special cases for what governors they support. Bug: skia: NOTRY=true Change-Id: I7bb220e1d3ba6851c17c7e6ef327aab24ffdba42 Reviewed-on: https://skia-review.googlesource.com/83900 Reviewed-by: Kevin Lubick <kjlubick@google.com> Commit-Queue: Kevin Lubick <kjlubick@google.com>
* Scale extra CPUs to powersave during nanobench.Gravatar Kevin Lubick2017-12-12
| | | | | | | | | | | | | | | | | | | | | | | | This scaling logic correctly accounts for some devices which have multiple CPUs. Previously, we were scaling the smaller of these CPUs, which likely had a negative impact on nanobench, given nanobench was single threaded and the CPUs weren't allowed to idle much (because we set the CPU). This CL sets those additional CPUs to powersave when we run nanobench and then correctly scales down the beefier CPU we want to run nanobench on. For DM, we just run it in ondemand mode, which will hopefully be "as fast as possible", but allow the CPU governor to scale down if overheating becomes a problem. Bug: skia:7378 notry=TRUE Change-Id: I45ca5d9fb32182233d1b2d094842c879f2b84da4 Reviewed-on: https://skia-review.googlesource.com/83240 Commit-Queue: Kevin Lubick <kjlubick@google.com> Reviewed-by: Mike Klein <mtklein@chromium.org>
* Re-add '--gpuThreads 0' tests.Gravatar Ben Wagner2017-12-11
Bug: skia:7394 Change-Id: I2e7ed586d81d19a0b7895ff81ce6670eb7cc5003 No-Try: true Reviewed-on: https://skia-review.googlesource.com/83445 Reviewed-by: Brian Osman <brianosman@google.com> Commit-Queue: Ben Wagner <benjaminwagner@google.com>
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-07 20:16:33 +0000