[LLVMdev] LLVM / CLANG Test Infrastructure Question

[Sundeep]

> > 1. I checked out and built llvm, clang, and test-suite from svn tip.
> When I
> > run llvm/test *without* my changes on x86, I see 3 failures. Is it
> expected?
> > I was expecting svn tip on x86 to be clean. Is there a nightly
> regression
> > result available somewhere that I can check for broken tests. Here is
> the
> > report from my log:
> >
> > Failing Tests (3):
> >    Clang :: Analysis/iterators.cpp
> >    Clang :: Driver/hello.c
> >    Clang :: Preprocessor/macro_paste_c_block_comment.c
> >
> >  Expected Passes    : 8757
> >  Expected Failures  : 69
> >  Unsupported Tests  : 551
> >  Unexpected Failures: 3
> >
> 
> Because you're living life on the bleeding edge (i.e., pulling code
> from the svn repository) it's possible for this to happen from time to
> time.  A fix is probably already in the works.  One way to ensure you
> don't introduce a new error is to maintain a clean (i.e., unmodified
> version of llvm/clang), which you can use as a baseline.  Run
> regressions on both the clean and modified versions to see if you cause
> any additional failures.

Makes sense.
 
> > 2. I see clang has its own test suite under clang/test. I assume when
> I run
> > llvm/test, the test infrastructure also runs clang/test.
> 
> How are you invoking the tests?  I typically do 'make check-all' from
> my build directory, which runs both regression suites.

Yes, I am doing "make check-all".
 
> > 3. For running projects/test-suite, the instruction guide directs to
> build
> > llvm-gcc. Why is llvm-gcc required? Why is clang not being used?
> 
> Very possible the documentation needs updating.

I see. Do you run projects/test-suite with clang?

> > 4. I see many compile errors when running projects/test-suite. Is it
> > expected?
> 
> No.

I will try to debug. Do you have a log file from your previous runs that I
can use?

Thanks Chad. I appreciate it.

-Sundeep