Write a message when an xUnit invocation fails

Previously finding out which xunit projects failed was difficult because
unlike Windows we didn't write a message when xUnit returned with a non
zero exit code.  In cases where tests failed, it was somewhat easy to
search the logs for xUnits "a test failed" messages but if the runtime
crashed, things were much harder.

Update run-test.sh to write an error message in the same style as what
we do on windows as part of the xUnit invocation from MSBuild.

While I was in the area, I reduced some noise in the log by pushing the
output of a grep for supported platforms to /dev/null. We print a
message anyway when we detect a project is unsupported, so the output of
grep is not interesting.

1 files changed, 7 insertions, 1 deletions

diff --git a/run-test.sh b/run-test.sh
index 444b13d04f..0c7e529360 100755
--- a/run-test.sh
+++ b/run-test.sh
@@ -174,7 +174,7 @@ runtest()
 
   # Check here to see whether we should run this project
 
-  if grep "UnsupportedPlatforms.*$OS.*" $1
+  if grep "UnsupportedPlatforms.*$OS.*" $1 > /dev/null
   then
     echo "Test project file $1 indicates this test is not supported on $OS, skipping"
     exit 0
@@ -223,6 +223,12 @@ runtest()
   echo
   ./corerun xunit.console.netcore.exe $testDllName -xml testResults.xml -notrait category=failing -notrait category=OuterLoop -notrait category=$xunitOSCategory
   exitCode=$?
+
+  if [ $exitCode -ne 0 ]
+  then
+      echo "One or more tests failed while running tests from '$fileNameWithoutExtension'.  Exit code $exitCode."
+  fi
+
   popd > /dev/null
   exit $exitCode
 }