[cfe-dev] tests broken

[John Thompson]

Thanks, Daniel.  I've been experimenting with the patches.

I know the count.bat and not.bat scripts are experimental and that you only
temporarily have the them using hard-coded paths for the Python executable
and the Python scripts they call (i.e. g:\public\llvm\test\Scripts\not.py).

I think the Python executable scripts could just rely on python being in the
path.  (I use Python 2.6, so the path is different.)

I'm not sure what the best solution is for the Python script path, however.
Some possibilities:

1. Use an environment variable for the LLVM root (i.e. LLVM_ROOT) in the
script.  Using environment variables, of course, would be unfortunate.

2. Would setting PYTHONPATH to (prefix)\llvm\test\Scripts and just using a
bare script file name in the batch files work?

3.  Have users edit the scripts manually.

Or perhaps you have a better solution already.

With Baptiste's clang-win32-path.patch and llvm-win32-path.patch files
applied I'm down to 64 failures.

I'm going to put back and try Baptiste's other script patches again, as my
failures might have been due to not noticing the path issue with the
count.bat and not.bat scripts.

-John
On Mon, Aug 10, 2009 at 10:37 PM, Daniel Dunbar <daniel at zuster.org> wrote:

> I attached the llvm and clang patches I have on my Windows box.
> Currently I run the test runner by hand from a cmd prompt, like this:
> --
> c:\python25\python ..\utils\test\MultiTestRunner.py --clang
> g:\public\llvm\build_msvc
> 9\bin\Debug\clang.exe --clang-cc
> g:\public\llvm\build_msvc9\bin\Debug\clang-cc.exe --no-sh --path
> g:\public\llvm\test\Scripts --path g:\public\llvm\buil
> d_msvc9\bin\Debug -j 3 -v .
> --
> The last time I tried it, I had 98 failures.
>
>  - Daniel
>
> --
> John Thompson
> John.Thompson.JTSoftware at gmail.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20090812/1ce5df7d/attachment.html>