maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Diffing against a file that is itself used in the test seems to be a bad 

idea, because it might get locked down and rendered unopenable.

llvm-svn: 309142
This commit is contained in:
Eric Beckmann 2017-07-26 17:47:44 +00:00
parent e06e4df8be
commit 6638ba2d75
1 changed files with 25 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
llvm/test/tools/llvm-mt/single_file.test
View File

@ -2,4 +2,28 @@ REQUIRES: libxml2
UNSUPPORTED: windows
RUN: llvm-mt /manifest %p/Inputs/test_manifest.manifest /out:%t
RUN: diff %p/Inputs/test_manifest.manifest %t
RUN: FileCheck %s --input-file=%t
CHECK: <?xml version="1.0"?>
CHECK-NEXT: <assembly xmlns="urn:schemas-microsoft-com:asm.v1">
CHECK-NEXT: <trustInfo>
CHECK-NEXT: <security>
CHECK-NEXT: <requestedPrivileges>
CHECK-NEXT: <requestedExecutionLevel level="3" uiAccess="1"/>
CHECK-NEXT: </requestedPrivileges>
CHECK-NEXT: </security>
CHECK-NEXT: </trustInfo>
CHECK-NEXT: <dependency>
CHECK-NEXT: <dependentAssembly>
CHECK-NEXT: <assemblyIdentity program="displayDriver"/>
CHECK-NEXT: </dependentAssembly>
CHECK-NEXT: </dependency>
CHECK-NEXT: <compatibility>
CHECK-NEXT: <dependency>
CHECK-NEXT: <assemblyIdentity program="compatibilityCheck1"/>
CHECK-NEXT: </dependency>
CHECK-NEXT: <application>
CHECK-NEXT: <supportedOS Id="FooOS"/>
CHECK-NEXT: </application>
CHECK-NEXT: </compatibility>
CHECK-NEXT: </assembly>