Hi,
I've been going over some of the failed testsuite models under OS X
Tiger:
1. In mofiles, 261 out of 282 tests succeed; failures are:
...
+ Constant6 ... nonzero exit status
...
+ Vectorizable1 ... equation mismatch
+ Vectorizable2 ... equation mismatch
+ Vectorizable3 ... equation mismatch
...
+ FunctionEval1 ... equation mismatch
+ FunctionEval2 ... equation mismatch
...
+ FunctionEval9 ... equation mismatch
...
+ FunctionBubblesort ... equation mismatch
+ FunctionSimplex ... equation mismatch
+ ExternalFunction1 ... equation mismatch
+ ExternalFunction2 ... equation mismatch
+ ExternalFunction3 ... equation mismatch
...
+ MultFuncCall ... equation mismatch
...
+ EquationCall ... equation mismatch
...
+ MultipleResultsFunction ... equation mismatch
+ PolynomialEvaluator1 ... equation mismatch
...
+ FuncMultResults ... equation mismatch
...
+ EqualityEquationsCorrect ... equation mismatch
...
+ FuncDer ... equation mismatch
...
+ InOutBool ... equation mismatch
+ InOutArray ... equation mismatch
It seems like a common thing in these test cases is that somewhere
they call a function with a constant as an argument, e.g. foo(1.2) or
foo(a) where a is, e.g., "constant Real a = 1.2;"
2. In mofiles/msl, everything passes.
3. in mosfiles, 94 out of 105 tests succeeded, and for the most part
the output looks like what has been discussed in previous posts,
along with some function calls with constants as arguments.
4. in meta, everything passes.
I was wondering if anyone has had the passing constants failures like
in item #1 above under Leopard?
Thanks,
Jason
--------------------------------------------
Jason Brown
Georgia Institute of Technology
College of Architecture
[EMAIL PROTECTED]
