Idris2/tests/base/system_info_os001/run

rm -rf build

case "$(uname)" in
  Linux*) EXPECTED_OS=unix ;;
  OpenBSD*) EXPECTED_OS=unix ;;
  FreeBSD*) EXPECTED_OS=unix ;;
  NetBSD*) EXPECTED_OS=unix ;;
  Darwin*) EXPECTED_OS=darwin ;;
  CYGWIN*) EXPECTED_OS=windows ;;
  MINGW*) EXPECTED_OS=windows ;;
  *) echo "unknown uname $(uname)" >&2; exit 1; ;;
esac
export EXPECTED_OS

$1 --no-banner --no-color --console-width 0 Os.idr --exec main
Move rm -rf to the beginning of the test While the discussion about how to refactor test framework is not finished (#1654), make this change: move `rm -rf build` in the beginning of the test. For these reasons: * it is useful to inspect the contents of the `build` directory especially after the test failure * if build crashes mid-test (e.g. process killed), next run should not be affected by the `build` directory from the previous run 2021-07-14 00:54:53 +03:00			`rm -rf build`

Test for System.Info.os 2021-06-29 02:18:14 +03:00			`case "$(uname)" in`
			`Linux*) EXPECTED_OS=unix ;;`
system_info_os001: Add all the OSs that System.Info.os knows about 2021-12-26 04:32:05 +03:00			`OpenBSD*) EXPECTED_OS=unix ;;`
			`FreeBSD*) EXPECTED_OS=unix ;;`
			`NetBSD*) EXPECTED_OS=unix ;;`
Test for System.Info.os 2021-06-29 02:18:14 +03:00			`Darwin*) EXPECTED_OS=darwin ;;`
			`CYGWIN*) EXPECTED_OS=windows ;;`
			`MINGW*) EXPECTED_OS=windows ;;`
			`*) echo "unknown uname $(uname)" >&2; exit 1; ;;`
			`esac`
			`export EXPECTED_OS`

			`$1 --no-banner --no-color --console-width 0 Os.idr --exec main`