summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/scope/main.cpp
diff options
context:
space:
mode:
authorKeith Wyss <wyssman@gmail.com>2017-04-20 05:59:26 +0000
committerKeith Wyss <wyssman@gmail.com>2017-04-20 05:59:26 +0000
commitdd11cf9022746015f13ff4d73f218c08a4295f69 (patch)
treecc5a2b3f3310f5b0c1522b271caf4237b5a03475 /lldb/packages/Python/lldbsuite/test/lang/cpp/scope/main.cpp
parent9ce5ef947528b629a27318c8c74c545b0f3d9d73 (diff)
downloadbcm5719-llvm-dd11cf9022746015f13ff4d73f218c08a4295f69.tar.gz
bcm5719-llvm-dd11cf9022746015f13ff4d73f218c08a4295f69.zip
[XRay] [compiler-rt] - Fix standalone and non-deterministic test issue
Summary: The thread order test fails sometimes my machine independently of standalone build. From testing both standalone and in-tree build, I see I configured it wrong. The other hypothesis for an issue is that cold starts can interfere with whether record unwriting happens. Once this happens more than once, we can naively FileCheck on the wrong test output, which compounds the issue. While "rm blah.* || true" will print to stderr if the glob can't expand, this is mostly harmless and makes sure earlier failing tests don't sabotage us. Example failure: --- header: version: 1 type: 1 constant-tsc: true nonstop-tsc: true cycle-frequency: 3800000000 records: - { type: 0, func-id: 1, function: 'f1()', cpu: 9, thread: 21377, kind: function-enter, tsc: 2413745203147228 } - { type: 0, func-id: 1, function: 'f1()', cpu: 9, thread: 21377, kind: function-exit, tsc: 2413745203304238 } ... The CMAKE related change fixes the expectation that COMPILER_RT_STANDALONE_BUILD will be explicitly FALSE instead of empty string when it is not "TRUE". Reviewers: dberris Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D32259 llvm-svn: 300822
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/scope/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud