Revert "Fixup XFAIL marking on TestConstVariables for clang version"
Linux with ToT clang (3.8) fails.
This reverts commit r247633.
Differential Revision: http://reviews.llvm.org/D12868
Hmm, looks like we need to pinpoint clang version 3.6, because it succeeds there.
I'm curious why we use an unreleased compiler for lldb build bots. That seems like we're adding instability to what should be a stable test environment.
This is a great illustration of why we should consider moving unexpected
I just did a set of tests on TestConstVariables on Ubuntu 14.04 x86_64.
With clang-3.5, it passes. It was marked XFAIL, and so unexpectedly
With clang-3.6, it passes. It was marked XFAIL (until earlier today, and
(I don't have an easy way to try clang-3.7 on the box I'm using, so not
With TOT clang, it fails. Had the unexpected successes in the clang 3.5+
So the real timeline for this test is it was passing (and should have been
I'll figure out how to mark that up in the test system, and extend it if I
And by more recently started failing, I mean more recent versions of clang are needed to expose the failure, regardless of where exactly the root cause lies.
I have since built a clang 3.7 on that machine. It is busted there as well.
This change is take 2, with all clang versions properly marked. I tested against clang 3.4, 3.5, 3.6, 3.7 and TOT (3.8) on Ubuntu 14.04 x86_64.