[llvm-dev] Problem with 'sed' on one Windows bot? (original) (raw)
Robinson, Paul via llvm-dev llvm-dev at lists.llvm.org
Tue Nov 7 14:41:49 PST 2017
- Previous message: [llvm-dev] Questions about code-size optimizations in ARM backend
- Next message: [llvm-dev] Problem with 'sed' on one Windows bot?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
A test I added in r317607 is passing almost everywhere, except for llvm-clang-x86_64-expensive-checks-win. Other Windows bots are happy.
http://lab.llvm.org:8011/builders/llvm-clang-x86_64-expensive-checks-win/builds/6013
The test runs 'sed' on a file to generate variations of the input assembler source for Linux and Darwin. I have to say it looks like 'sed' is being the problem on that one bot. I reverted the test because "don't argue with the bots" but... but... "It's not my fault!"
If anybody has any insight it would be greatly appreciated. Thanks, --paulr
The failure is this:
Command Output (stdout):
$ "sed" "-E" "s/@ELF@(.)/\1/;s/@MACHO@(.)//" "C:\ps4-buildslave2\llvm-clang-x86_64-expensive-checks-win\llvm\test\DebugInfo\X86\dwarfdump-header-64.s" $ "C:\ps4-buildslave2\llvm-clang-x86_64-expensive-checks-win\build\bin\llvm-mc.EXE" "-triple" "x86_64-unknown-linux" "-filetype=obj" "-o" "-"
command stderr:
:17:1: error: unexpected token at start of statement
1
^
:28:1: error: unexpected token at start of statement
1
^
:43:1: error: unexpected token at start of statement
1
^
:53:1: error: unexpected token at start of statement
1
^
:59:1: error: unexpected token at start of statement
1
^
:71:1: error: unexpected token at start of statement
1
^
error: command failed with exit status: 1
- Previous message: [llvm-dev] Questions about code-size optimizations in ARM backend
- Next message: [llvm-dev] Problem with 'sed' on one Windows bot?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]