summaryrefslogtreecommitdiff
path: root/netci.groovy
diff options
context:
space:
mode:
authorBruce Forstall <brucefo@microsoft.com>2017-11-21 15:20:24 -0800
committerBruce Forstall <brucefo@microsoft.com>2017-11-21 23:18:00 -0800
commit2d28395b45ceddbfe9463274dcbeebc05403354a (patch)
treeecc981863c03a1737285b3a2079306288467f3b0 /netci.groovy
parent30d20fd832b4dba9e6d5f9c77f88d8b3ccd1066e (diff)
downloadcoreclr-2d28395b45ceddbfe9463274dcbeebc05403354a.tar.gz
coreclr-2d28395b45ceddbfe9463274dcbeebc05403354a.tar.bz2
coreclr-2d28395b45ceddbfe9463274dcbeebc05403354a.zip
Archive smarty directory for arm/armlb/arm64 runs
Currently, we only archive the *.smrt files, which is not enough to see why a test failed, only that it did. Instead, ZIP the entire Smarty.run.0 directory, and upload that (it's about 26MB for a Pri-1 test run). This allows us to see the actual output of each test, as generated by smarty.
Diffstat (limited to 'netci.groovy')
-rwxr-xr-xnetci.groovy9
1 files changed, 9 insertions, 0 deletions
diff --git a/netci.groovy b/netci.groovy
index d31f74cead..8c9b83e12c 100755
--- a/netci.groovy
+++ b/netci.groovy
@@ -2512,6 +2512,10 @@ Constants.allScenarios.each { scenario ->
addCommand("pushd bin\\tests\\${osGroup}.${architecture}.${configuration}")
addCommand("${smartyCommand}")
+ // ZIP up the smarty output. Note that the current directory was changed above by "pushd", so we are
+ // in the correct directory where the "Smarty.run.0" directory is.
+ buildCommands += "powershell -Command \"Add-Type -Assembly 'System.IO.Compression.FileSystem'; [System.IO.Compression.ZipFile]::CreateFromDirectory('.\\Smarty.run.0', '.\\Smarty.run.0.zip')\"";
+
batchFile(buildCommands)
}
}
@@ -2558,6 +2562,11 @@ Constants.allScenarios.each { scenario ->
}
else {
Utilities.addArchival(newJob, "bin/tests/${osGroup}.${architecture}.${configuration}/Smarty.run.0/*.smrt", '', true, false)
+
+ // Archive a ZIP file of the entire Smarty.run.0 directory. This is possibly a little too much,
+ // but there is no easy way to only archive the HTML/TXT files of the failing tests, so we get
+ // all the passing test info as well. Not necessarily a bad thing, but possibly somewhat large.
+ Utilities.addArchival(newJob, "bin/tests/${osGroup}.${architecture}.${configuration}/Smarty.run.0.zip", '', true, false)
}
// Create a build flow to join together the build and tests required to run this test.