Clean up artifacts after test execution

Avoid storing artifacts where it's not necessary for the test, and
store them in a temporary folder where it is.

Bug: chromium:973518
Change-Id: I5ab8bf9f9882dd7aa81af808c66f64d6721a60e3
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/1655610
Reviewed-by: Juan Antonio Navarro PĂ©rez <perezju@chromium.org>
Commit-Queue: Mikhail Khokhlov <khokhlov@google.com>
5 files changed
tree: 125c45996a22722b2425e248d5941e84c300b7a4
  1. bin/
  2. catapult_build/
  3. common/
  4. dashboard/
  5. dependency_manager/
  6. devil/
  7. docs/
  8. experimental/
  9. firefighter/
  10. hooks/
  11. infra/
  12. netlog_viewer/
  13. systrace/
  14. telemetry/
  15. third_party/
  16. trace_processor/
  17. tracing/
  18. web_page_replay_go/
  19. .eslintignore
  20. .eslintrc
  21. .gitignore
  22. .vpython
  23. AUTHORS
  24. BUILD.gn
  25. codereview.settings
  26. CONTRIBUTING.md
  27. generate_telemetry_build.py
  28. LICENSE
  29. navbar.md
  30. OWNERS
  31. PRESUBMIT.py
  32. pylintrc
  33. README.md
  34. WATCHLISTS
README.md

Catapult

Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:

These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.

Contributing

Please see our contributor's guide

Current build status