LIT tests fail on Windows X86_64

[David Blaikie]

On Mon, Jun 24, 2013 at 12:05 AM, Demikhovsky, Elena
<elena.demikhovsky at intel.com> wrote:
> This one is fixed, thank you. The second failure is still in:
>
> FAIL: LLVM :: DebugInfo/arguments.ll (4520 of 8258)
> 134>  ******************** TEST 'LLVM :: DebugInfo/arguments.ll' FAILED ********************
> 134>  Script:
> 134>  --
> 134>  W:/LLVM_now/build64/bin/Debug/llc.EXE -O0 -filetype=obj < W:\LLVM_now\llvm\test\DebugInfo\arguments.ll > W:\LLVM_now\build64\test\DebugInfo\Output\arguments.ll.tmp
> 134>  W:/LLVM_now/build64/bin/Debug/llvm-dwarfdump.EXE W:\LLVM_now\build64\test\DebugInfo\Output\arguments.ll.tmp | W:/LLVM_now/build64/bin/Debug/FileCheck.EXE W:\LLVM_now\llvm\test\DebugInfo\arguments.ll

Yep, this is known (sorry, hadn't realized it was falling bot fallout
until Duncan brought it to my attention). It can be xfailed for now,
but I think there's a fairly obvious fix to this.

> 134>  --
> 134>  Exit Code: 1
> 134>  Command Output (stdout):
> 134>  --
> 134>  Command 0: "W:/LLVM_now/build64/bin/Debug/llc.EXE" "-O0" "-filetype=obj"
> 134>  Command 0 Result: 0
> 134>  Command 0 Output:
> 134>  None
> 134>
> 134>  Command 0 Stderr:
> 134>
> 134>
> 134>  Command 1: "W:/LLVM_now/build64/bin/Debug/llvm-dwarfdump.EXE" "W:\LLVM_now\build64\test\DebugInfo\Output\arguments.ll.tmp"
> 134>  Command 1 Result: 0
> 134>  Command 1 Output:
> 134>
> 134>
> 134>  Command 1 Stderr:
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_SECREL
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR64
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR64
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>CUSTOMBUILD : error : failed to compute relocation: IMAGE_REL_AMD64_ADDR32
> 134>
> 134>
> 134>  Command 2: "W:/LLVM_now/build64/bin/Debug/FileCheck.EXE" "W:\LLVM_now\llvm\test\DebugInfo\arguments.ll"
> 134>  Command 2 Result: 1
> 134>  Command 2 Output:
> 134>
> 134>
> 134>  Command 2 Stderr:
> 134>  <stdin>:102:13: error: CHECK-NOT: string occurred!
> 134>  0x00000050: NULL
> 134>              ^
> 134>  W:\LLVM_now\llvm\test\DebugInfo\arguments.ll:22:14: note: CHECK-NOT: pattern specified here
> 134>  ; CHECK-NOT: NULL
> 134>               ^
> 134>
> 134>
> 134>  --
> 134>
> 134>  ********************
> 134>
> 134>  Testing Time: 138.48s
> 134>  ********************
> 134>  Failing Tests (1):
> 134>      LLVM :: DebugInfo/arguments.ll
> 134>
> 134>    Expected Passes    : 8171
> 134>    Expected Failures  : 51
> 134>    Unsupported Tests  : 35
> 134>    Unexpected Failures: 1
> 134>  lit.py: LitConfig.py:103: note: Unable to find 'bash.exe'.
> 134>
> 134>Build FAILED.
>
> -  Elena
>
>
> -----Original Message-----
> From: Tim Northover [mailto:t.p.northover at gmail.com]
> Sent: Sunday, June 23, 2013 18:34
> To: Demikhovsky, Elena
> Cc: llvm-commits at cs.uiuc.edu
> Subject: Re: LIT tests fail on Windows X86_64
>
> Hi Elena,
>
>> 20>  FAIL: LLVM :: MC/AArch64/tls-relocs.s (4886 of 8256)
>
> Thanks, I think I've seen something like this problem before and fixed the test in r184667 (hopefully, I don't have Windows to do any testing on). From what I remember, for some reason Windows output often gets extra newlines in it; I'd be interested in the reasoning behind that, if anyone knows.
>
> Cheers.
>
> Tim.
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>