blob: c6e0f7a3c635fe1f07100312673d68be07734170 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
|
<!--
***********************************************************************************************
CLRTest.Execute.targets
WARNING: DO NOT MODIFY this file unless you are knowledgeable about MSBuild and have
created a backup copy. Incorrect changes to this file will make it
impossible to load or build your projects from the command-line or the IDE.
This file contains the logic for providing Execution Script generation.
WARNING: When setting properties based on their current state (for example:
<Foo Condition="'$(Foo)'==''>Bar</Foo>). Be very careful. Another script generation
target might be trying to do the same thing. It's better to avoid this by instead setting a new property.
Additionally, be careful with itemgroups. Include will propagate outside of the target too!
***********************************************************************************************
-->
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<!--
Target: GetExecuteShFullPath
Return Executed Sh Relative Full Path
We can use this target get its toRun Project's Sh Full Path to avoid hard-code
-->
<Target
Name="GetExecuteShFullPath"
Returns="$(ExecuteShFullPath)">
<PropertyGroup>
<ExecuteShFullPath>$(OutputPath)\$(AssemblyName).sh</ExecuteShFullPath>
</PropertyGroup>
</Target>
<!--
*******************************************************************************************
TARGET: GenerateExecutionScriptInternal
For tests that "run" we will generate an execution script that wraps any arguments or other
goo. This allows generated .lst files to be very simple and reusable to invoke any "stage"
of test execution.
Notice this is hooked up to run after targets that generate the stores that are marked with GenerateScripts metadata.
Note also that this means it will run after the first of such targets.
-->
<Target Name="GenerateBashExecutionScript"
Inputs="$(MSBuildProjectFullPath)"
Outputs="$(OutputPath)\$(AssemblyName).sh">
<PropertyGroup>
<!-- TODO:2 build in debugger experience support -->
<BashCLRTestExitCodePrep Condition="$(_CLRTestNeedsToRun)">
<![CDATA[CLRTestExpectedExitCode=$(CLRTestExitCode)
echo BEGIN EXECUTION]]>
</BashCLRTestExitCodePrep>
<BashCLRTestArgPrep Condition=" '$(CLRTestExecutionArguments)'!='' ">
<![CDATA[CLRTestExecutionArguments=$(CLRTestExecutionArguments)]]>
</BashCLRTestArgPrep>
<!-- By default, be prepared to do a full check -->
<BashCLRTestExitCodeCheck><![CDATA[
echo Expected: $CLRTestExpectedExitCode
echo Actual: $CLRTestExitCode
if [ ! $CLRTestExitCode == $CLRTestExpectedExitCode ]
then
echo END EXECUTION - FAILED
echo FAILED
exit 1
else
echo END EXECUTION - PASSED
echo PASSED
exit 0
fi
]]></BashCLRTestExitCodeCheck>
</PropertyGroup>
<ItemGroup Condition="$(_CLRTestNeedsToRun)">
<Clean Include="$(OutputPath)\$(AssemblyName).sh"/>
<BashCLRTestExecutionScriptArgument Include="debug">
<HasParam>true</HasParam>
<ParamText>=*</ParamText> <!-- Bash specific -->
<ParamName>debuggerFullPath</ParamName>
<Command><![CDATA[ _DebuggerFullPath="${i#*=}"
if [ ! -f DebuggerFullPath ]
then
echo The Debugger FullPath \"$_DebuggerFullPath\" doesn\'t exist
usage
fi]]></Command>
<Description>Run testcases under debugger.</Description>
</BashCLRTestExecutionScriptArgument>
</ItemGroup>
<!--Call GetExecuteShFullPath to get ToRunProject cmd file Path -->
<MSBuild Projects="$(CLRTestProjectToRun)" Targets="GetExecuteShFullPath" Condition="'$(_CLRTestNeedsProjectToRun)' == 'True'">
<Output TaskParameter="TargetOutputs" PropertyName="_CLRTestToRunFileFullPath"/>
</MSBuild>
<PropertyGroup>
<!-- Calculate the thing we're going to run -->
<_CLRTestRunFile Condition="'$(_CLRTestNeedsProjectToRun)' != 'True'">"$(AssemblyName).exe"</_CLRTestRunFile>
<!-- TODO: make this better? -->
<_CLRTestRunFile Condition=" '$(CLRTestIsHosted)'=='true' And !$(_CLRTestNeedsProjectToRun) ">"$Core_Root\mono" $(_CLRTestRunFile)</_CLRTestRunFile>
<BashCLRTestLaunchCmds Condition=" '$(BashCLRTestLaunchCmds)'=='' "><![CDATA[
echo $(_CLRTestRunFile) $CLRTestExecutionArguments $Host_Args
$_DebuggerFullPath $(_CLRTestRunFile) $CLRTestExecutionArguments $Host_Args
CLRTestExitCode=$?
]]></BashCLRTestLaunchCmds>
</PropertyGroup>
<Message Text="MSBuildProjectDirectory:$(MSBuildProjectDirectory)" />
<Message Text="_CLRTestToRunFileFullPath:$(_CLRTestToRunFileFullPath)"/>
<Message Text="_CLRTestRunFile:$(_CLRTestRunFile)" />
<ItemGroup>
<_RequiredProperties Include="_CLRTestRunFile">
<Value>$(_CLRTestRunFile)</Value>
</_RequiredProperties>
</ItemGroup>
<!-- Raise an error if any value in _RequiredProperties is missing -->
<Error Condition=" '%(_RequiredProperties.Value)'=='' "
Text="Missing required test property [%(_RequiredProperties.Identity)]. Something isn't plumbed through correctly. Contact $(_CLRTestBuildSystemOwner)." />
<!-- TODO: this is weird. Consider eliminating it. -->
<GenerateParamList ArgumentItems="@(BashCLRTestExecutionScriptArgument)">
<Output TaskParameter="ParamList" PropertyName="_CLRTestParamList"/>
</GenerateParamList>
<PropertyGroup>
<!--
This generates the script portion to parse all of the command line arguments.
The Command metadata for BashCLRTestExecutionScriptArgument items is executed
when the argument is found.
-->
<BashCLRTestArgPrep><![CDATA[
usage()
{
echo "Usage: $0 $(_CLRTestParamList)"
echo
echo "Arguments:"
@(BatchCLRTestExecutionScriptArgument -> ' echo "-%(Identity) %(ParamName)"
echo "%(Description)"', '
')
echo " -?,-h,--help show this message"
exit 1
}
# Parse Command Line
for i in "$@"
do
case $i in
-?|-h|--help)
usage
%3B%3B
@(BashCLRTestExecutionScriptArgument -> ' -%(Identity)%(ParamText)|/%(Identity)%(ParamText))
%(Command)
%3B%3B')
*)
CLRTestExecutionArguments="$CLRTestExecutionArguments $i"
esac
done
$(BashCLRTestArgPrep)
]]></BashCLRTestArgPrep>
<!-- NOTE! semicolons must be escaped with %3B boooo -->
<_CLRTestExecutionScriptText><![CDATA[
$(BashCLRTestArgPrep)
$(BashCLRTestExitCodePrep)
# Precommands
$(_CLRTestPreCommands)
# Launch
$(BashCLRTestLaunchCmds)
# PostCommands
$(_CLRTestPostCommands)
$(BashCLRTestExitCodeCheck)
]]></_CLRTestExecutionScriptText>
</PropertyGroup>
<!-- Write the file -->
<WriteLinesToFile
File="$(OutputPath)\$(AssemblyName).sh"
Lines="$(_CLRTestExecutionScriptText)"
Overwrite="true" />
</Target>
</Project>
|
