-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Closed
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillaobsoleteIssues with old (unsupported) versions of LLVMIssues with old (unsupported) versions of LLVMwontfixIssue is real, but we can't or won't fix it. Not invalidIssue is real, but we can't or won't fix it. Not invalid
Description
| Bugzilla Link | 10078 |
| Version | trunk |
| OS | MacOS X |
| Reporter | LLVM Bugzilla Contributor |
Extended Description
If you check out LLVM into a directory with '.' characters in the path, the %p variable seems to be mis-expanded when running the LLVM test suite. This causes bogus failures in the test suite.
Specifically, I had a copy of LLVM on my disk in
/Volumes/sandbox/stuart/llvmCore.clang.test2
I believe (at least) these failures were caused by the directory name with period characters:
LLVM :: LLVMC/Alias.td
LLVM :: LLVMC/AppendCmdHook.td
LLVM :: LLVMC/EmptyCompilationGraph.td
LLVM :: LLVMC/EnvParentheses.td
LLVM :: LLVMC/ForwardAs.td
LLVM :: LLVMC/ForwardTransformedValue.td
LLVM :: LLVMC/ForwardValue.td
LLVM :: LLVMC/HookWithArguments.td
LLVM :: LLVMC/HookWithInFile.td
LLVM :: LLVMC/Init.td
LLVM :: LLVMC/LanguageMap.td
LLVM :: LLVMC/MultiValuedOption.td
LLVM :: LLVMC/MultipleCompilationGraphs.td
LLVM :: LLVMC/MultipleOutputLanguages.td
LLVM :: LLVMC/NoActions.td
LLVM :: LLVMC/NoCompilationGraph.td
LLVM :: LLVMC/OneOrMore.td
LLVM :: LLVMC/OptionPreprocessor.td
LLVM :: LLVMC/OutputSuffixHook.td
Obvious workaround: avoid period characters in directory names.
Metadata
Metadata
Assignees
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillaobsoleteIssues with old (unsupported) versions of LLVMIssues with old (unsupported) versions of LLVMwontfixIssue is real, but we can't or won't fix it. Not invalidIssue is real, but we can't or won't fix it. Not invalid