Jordan Rupprecht 817b3a6fe3 [test] Use abspath instead of realpath sometimes ...

In these two cases, use of `os.path.realpath` is problematic:

- The name of the compiler is significant [1] . For testing purposes, we might
  provide a compiler called "clang" which is actually a symlink to some build
  script (which does some flag processing before invoking the real clang). The
  destination the symlink may not be called "clang", but we still want it to be
  treated as such.
- When using a build system that puts build artifacts in an arbitrary build
  location, and later creates a symlink for it (e.g. creates a
  "<lldb root>/lldbsuite/test/dotest.py" symlinks that points to
  "/build/artifact/<hash>/dotest.py"), looking at the realpath will not match
  the "test" convention required here.

[1] See `Makefile.rules` in the lldb tree, e.g. we use different flags if the compiler is named "clang"

Reviewed By: JDevlieghere

Differential Revision: https://reviews.llvm.org/D85175

2020-08-04 08:20:50 -07:00

..

support

[lldb/Python] Remove unused imports (NFC)

2020-01-02 16:55:09 -08:00

test

[test] Use abspath instead of realpath sometimes

2020-08-04 08:20:50 -07:00

test_event

[lldb] add printing of stdout compile errors to lldbsuite

2020-07-22 16:38:20 +02:00

__init__.py

[lldb][test] Prevent infinite loop while looking for use_lldb_suite_root.py.

2020-07-15 09:16:30 -07:00