Merge pull request #3022 from heplesser/move-tests

Move tests that are irrelevant post-sli to sli2py_ignore

testsuite/regressiontests/ticket-235.sli → testsuite/regressiontests/sli2py_ignore/ticket-235.sli

@@ -31,7 +31,7 @@
 /unittest using
 
 % preparatory work for proper test code in case NEST is complied with MPI support
-% For now we just ignore this test, this will later be replaced 
+% For now we just ignore this test, this will later be replaced
 % by a restart of NEST with a serial binary.
 skip_if_have_mpi
 
@@ -46,4 +46,4 @@ skip_if_have_mpi
 {token_is} failbutnocrash_or_die
 {setguard} failbutnocrash_or_die
 
-endusing
+endusing

testsuite/regressiontests/ticket-475.sli → testsuite/regressiontests/sli2py_ignore/ticket-475.sli

@@ -29,7 +29,7 @@ Synopsis: (ticket-475) run -> NEST exits if test fails
 Description:
 Compilation on Stallo with icpc 11.1 cause crashed when collecting data across
 threads.
- 
+
 Author: Hans Ekkehard Plesser, 2010-10-11
  */
 
@@ -40,10 +40,10 @@ M_INFO setverbosity
 
 
 {
-  /spike_recorder Create 
+  /spike_recorder Create
 %  sd ShowStatus
   %10 Simulate
  % sd GetStatus
 } pass_or_die
 
-endusing
+endusing

testsuite/regressiontests/ticket-537.sli → testsuite/regressiontests/sli2py_ignore/ticket-537.sli

@@ -27,9 +27,9 @@ Name: testsuite::ticket-537 - Regression test for memory allocation/free error i
 Synopsis: (ticket-537) run -> NEST exits if test fails
 
 Description:
-This test detects a memory allocation/freeing problem introduced with the SLI modernization per r9458. 
+This test detects a memory allocation/freeing problem introduced with the SLI modernization per r9458.
 This bug occurred only on certain Linux platforms.
- 
+
 Author: Hans Ekkehard Plesser, 2012-01-12, based on reproduces by Marc-Oliver Gewaltig
  */
 
@@ -58,4 +58,4 @@ pass_or_die
 pass_or_die
 
 
-endusing
+endusing

testsuite/regressiontests/ticket-580.sli → testsuite/regressiontests/sli2py_ignore/ticket-580.sli

@@ -26,13 +26,13 @@ Name: testsuite::ticket-580 - getinterval: No error if range of array is exceede
 
 Synopsis: (ticket-564) run -> NEST exits if test fails
 
-Description: 
-1) This test checks whether the sli functions getinterval and Take perform Range Checks, i.e. whether they throw errors if the requested part of the interval exceeds the original array or not. 
+Description:
+1) This test checks whether the sli functions getinterval and Take perform Range Checks, i.e. whether they throw errors if the requested part of the interval exceeds the original array or not.
 2) Furthermore, it checks whether getinterval throws an error if negative indices are given and whether Takes does not throw an error.
 3) Checks whether Take returns an empty array if n_2 < n_1
 
 In addition, it checks whether they return the same results for a correct usage.
- 
+
 Author: Maximilian Schmidt, 2012-10-16
  */
 
@@ -46,7 +46,7 @@ M_ERROR setverbosity
 (Hallo) /y Set
 
 
-{ 
+{
   x [1 4] Take
 } fail_or_die
 
@@ -70,7 +70,7 @@ M_ERROR setverbosity
   [] eq
 } assert_or_die
 
-{ 
+{
   x 0 4 getinterval
 } fail_or_die
 

testsuite/regressiontests/ticket-733.sli → testsuite/regressiontests/sli2py_ignore/ticket-733.sli

@@ -34,4 +34,4 @@ This test verify that neq returns false when two intvectors or two double vector
 /unittest using
 
 <# 1 2 3 #> <# 1 2 3 #> neq false eq assert_or_die
-<. 1 2 3 .> <. 1 2 3 .> neq false eq assert_or_die
+<. 1 2 3 .> <. 1 2 3 .> neq false eq assert_or_die

testsuite/regressiontests/ticket-784.sli → testsuite/regressiontests/sli2py_ignore/ticket-784.sli

@@ -41,5 +41,3 @@ Author: Marc-Oliver Gewaltig, 2013-12-25
 clear
 { xor } fail_or_die % no arguments
 [ 1 1.0 (a) [] ] { {xor} stopped {errordict /newerror false put} { 3 quit_i } ifelse clear } forall
-
-

testsuite/regressiontests/ticket-785.sli → testsuite/regressiontests/sli2py_ignore/ticket-785.sli

@@ -39,11 +39,8 @@ Author: Marc-Oliver Gewaltig, 2013-12-25
 clear
 
 % the next test shows that {1 neq}  produces an error
-{1 neq } stopped {errordict /newerror false put} { 3 quit_i } ifelse 
-clear 
+{1 neq } stopped {errordict /newerror false put} { 3 quit_i } ifelse
+clear
 
 % the next test shows that the error is not caught by fail_or_die
 { 1 neq } fail_or_die % this one breaks
-
-
-