Powershell fails the entire batch file if it sees any output on stderr.
Migrated to powershell because batch files are old, I don't really want
to use batch.
$env:Path = $env:APPVEYOR_BUILD_FOLDER + "\" + $env:configuration + "\Graphviz\bin" + ";" + $env:Path;
dot -c;
cd tests\regression_tests;
- ./regression_tests.bat;
+ ./regression_tests.ps1;
}
artifacts:
+++ /dev/null
-@ECHO OFF
-
-pushd shapes
-python shapes.py
-popd
-
-REM Larger graph testing
-# FIXME: re-enable when https://gitlab.com/graphviz/graphviz/-/issues/1710 is fixed
-#python -m unittest discover large
--- /dev/null
+Push-Location shapes
+python shapes.py
+Pop-Location
+
+# Larger graph testing
+# Python unittest prints to stderr, but Powershell interprets stderr
+# messages as an error, failing the pipeline. So we must redirect
+# stderr to stdout. The line noise at the end does so. See
+# https://stackoverflow.com/a/20950421/171898 for explanation.
+python -m unittest discover large 2>&1 | %{ "$_" }