1. 14 Nov, 2017 1 commit
  2. 26 Sep, 2017 1 commit
  3. 25 Sep, 2017 1 commit
    • Stephen Martinis's avatar
      Add new telemetry_perf_tests isolate and script · 0b18efa1
      Stephen Martinis authored
      This CL adds a new isolate called telemetry_perf_tests_new. This
      is a temporary name, so that we can test it out while keeping the
      old isolate name. Eventually, this isolate will probably replace the
      existing isolate.
      
      The main difference between this and the current telemetry_perf_tests
      is the script it's running, which is named
      run_multiple_telemetry_benchmarks_as_googletest.py. As the name
      suggests, the script runs multiple telemetry benchmarks, which is the
      plan for a single swarming task in the future.
      
      Bug: 758630
      Change-Id: If3a8afbb22ae2dbf0ce9e69f9036449d47914d03
      Reviewed-on: https://chromium-review.googlesource.com/668111Reviewed-by: default avatarDirk Pranke <dpranke@chromium.org>
      Reviewed-by: default avatarEmily Hanley <eyaich@chromium.org>
      Commit-Queue: Stephen Martinis <martiniss@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#504196}
      0b18efa1
  4. 29 Aug, 2017 1 commit
  5. 24 Aug, 2017 1 commit
  6. 14 Aug, 2017 1 commit
  7. 07 Aug, 2017 1 commit
  8. 03 Aug, 2017 1 commit
  9. 02 Aug, 2017 1 commit
    • Ashley Enstad's avatar
      Updating run_telemetry_benchmark_as_googletest to resolve crash. · 8148f5fd
      Ashley Enstad authored
      Previously, run_telemetry_benchmark_as_googletest would check the
      validity of the benchmark run by opening results.json. This file
      was generated using the --output-format=json flag. By removing
      that flag in https://chromium-review.googlesource.com/c/589820,
      I broke all the Telemetry benchmarks on the perf waterfall o.O my
      bad. This change should fix the failing tests by checking the
      validity of the benchmark run by opening test-results.json,
      generated using the --output-format=json-test-results flag now
      being used for all Telemetry benchmark runs on the waterfall.
      
      BUG=751346, 748638
      
      NOTRY=true  # This script is not run on trybot/CQ, hence should be safe to notry
      
      Change-Id: I75e0abb5801f1cbaa480e65ade1827335a1195fd
      Reviewed-on: https://chromium-review.googlesource.com/597428
      Commit-Queue: Ashley Enstad <ashleymarie@chromium.org>
      Reviewed-by: default avatarNed Nguyen <nednguyen@google.com>
      Cr-Commit-Position: refs/heads/master@{#491242}
      8148f5fd
  10. 01 Aug, 2017 2 commits
  11. 12 Jul, 2017 1 commit
  12. 04 Apr, 2017 1 commit
  13. 04 Oct, 2016 1 commit
  14. 23 Sep, 2016 1 commit
  15. 20 Sep, 2016 1 commit
    • eyaich's avatar
      Updating the script that gets run in the benchmark isolate to also read in · 4e29701c
      eyaich authored
      chartjson results if available and add a chartjson result to the results
      json when present.
      
      I need these results in the chromium_tests SwarmingIsolatedScript class so
      that I can upload results to the perf dashboard after a successful swarming
      task.  I am not completely replacing the json with chartjson instead of
      just json becuase I am not sure if the json form is still needed yet.  This
      will be an iterative approach while I try and get a successful swarmed
      bencmark on the waterfall.
      
      BUG=chromium:633253
      
      Review-Url: https://codereview.chromium.org/2331993003
      Cr-Commit-Position: refs/heads/master@{#419740}
      4e29701c
  16. 01 Jun, 2016 1 commit
    • j.isorce's avatar
      allow usage of transparent visuals when using xvfb · b767ddc6
      j.isorce authored
      For the switch kEnableTransparentVisuals to be effective it requires
      a compositing manager to run. Indeed ui::ChooseVisualForWindow checks
      for the presence of the Atom _NET_WM_CM_S0 before looking for a 32
      bit depth compatible visual.
      
      BUG=589509
      
      R=dpranke@chromium.org, piman@chromium.org, sky@chromium.org, danakj@chromium.org
      
      Review-Url: https://codereview.chromium.org/2008833002
      Cr-Commit-Position: refs/heads/master@{#397073}
      b767ddc6
  17. 10 Dec, 2015 1 commit
    • kbr's avatar
      Skip the screenshot_sync test properly. · 34f722f1
      kbr authored
      Use test expectations instead of the benchmark.Disabled annotation.
      
      Signal a non-zero exit code from
      run_telemetry_benchmark_as_googletest.py when the target script produces
      no output. This will allow recipes to detect this failure case more
      automatically.
      
      BUG=459820,561863
      R=dpranke@chromium.org
      TBR=bajones@chromium.org,nednguyen@google.com
      
      Review URL: https://codereview.chromium.org/1513943002
      
      Cr-Commit-Position: refs/heads/master@{#364304}
      34f722f1
  18. 08 Dec, 2015 1 commit
  19. 26 Nov, 2015 1 commit
    • kbr's avatar
      New isolate and wrapper script for Telemetry based GPU tests. · 213b4f29
      kbr authored
      This follows the "isolated script test" contract in recipes'
      chromium_tests/steps.py. Once the recipes are switched over to run
      this new isolate, a lot of GPU-specific code can be deleted from the
      tools/build workspace. After the cutover, this new name will be
      removed. This is the first step in deleting the GPU recipe entirely.
      
      Tested locally on Linux with GN build, including multiple kinds of
      failure injection to ensure that the output JSON is produced as
      desired.
      
      BUG=560598
      NOTRY=true
      
      Review URL: https://codereview.chromium.org/1472263003
      
      Cr-Commit-Position: refs/heads/master@{#361771}
      213b4f29