HomePhabricator

[lldb] [lldbsuite] Use a unique class name for TestBacktraceAll

Description

[lldb] [lldbsuite] Use a unique class name for TestBacktraceAll

It looks like when this test was added, it was based on TestBreakAfterJoin and it ended up with the same class name. This is an issue because the logs associated with the tests use the class name as the identifier for the file and if two tests have the same name their logs overwrite each other. On non-windows, this just means we lose one of the logs, but on Windows this means that one of the tests will fail occasionally because the file are locked by the other test.

Details

Committed
stella.stamenovaJul 1 2019, 11:13 AM
Parents
rL364825: AMDGPU/GlobalISel: Fix allowing non-boolean conditions for G_SELECT
Branches
Unknown
Tags
Unknown