tast-tests: Add kallsyms from DUT to testing output directory in perf.

Copied /proc/kallsyms/ from the DUT to the output directory in perf
profiler class. This file is needed for symbolization in perf.

BUG=b:138821167
TEST=tast -verbose run $DUT example.Profiler

Change-Id: I903c243277b0233457cd7d3b6a2d5a2eea7f7ad6
Reviewed-on: https://chromium-review.googlesource.com/1757583
Tested-by: Andre Le <leandre@google.com>
Commit-Ready: Andre Le <leandre@google.com>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Shuhei Takahashi <nya@chromium.org>
1 file changed
tree: e06122818898688a3c0c383392da429246297020
  1. helpers/
  2. src/
  3. tools/
  4. .gitignore
  5. OWNERS
  6. PRESUBMIT.cfg
  7. README.md
README.md

Tast (tests)

This repository contains integration tests that are run by Tast.

Directory structure

  • helpers/ - Source code for binaries executed by tests.
    • local/ - Helpers for local tests that are compiled and installed to /usr/local/libexec/tast/helpers/local/cros by the tast-local-helpers-cros package.
  • src/chromiumos/tast/
    • local/ - Code related to local (i.e. on-device or “client”) tests.
      • bundles/ - Local test bundles.
        • cros/ - The “cros” local test bundle, containing standard Chrome OS tests. Tests are packaged by category.
      • ... - Packages used only by local tests.
    • remote/ - Code related to remote (i.e. off-device or “server”) tests.
      • bundles/ - Remote test bundles.
        • cros/ - The “cros” remote test bundle, containing standard Chrome OS tests. Tests are packaged by category.
      • ... - Packages used only by remote tests.

Shared code, the main tast executable, the local_test_runner and remote_test_runner executables responsible for running bundles, and documentation are located in the tast repository.

GoDoc