Running test suite

[Roshni Uppala]

Hi,

I have again installed Xyce is another cluster , and now when I run the Xyce regression suite, it ends with warning: 2 failed tests and 3 tests exited with an error.

The 2 failed tests are :
Certification_Tests/BUG_407_SON/bug_407_hb........FAILED[sh]      (Time:   1s =   0.34cs +   0vs)
Certification_Tests/BUG_1011/sand23...............FAILED[sh]      (Time:   0s =   0.19cs +   0vs)


The 3 tests that exited with an error :
PREPROC_ADDRES/nodcpath...........................EXITED WITH ERROR[sh] (Time:   1s =   0.35cs +   0vs)
PREPROC_ADDRES/oneterm............................EXITED WITH ERROR[sh] (Time:   0s =   0.36cs +   0vs)
Certification_Tests/BUG_141_SON/bug_141-empty.....EXITED WITH ERROR[sh] (Time:   1s =   0.45cs +   0vs)

Is this something to be worried about or can I just ignore it ?

Thanks

-Roshni

[xyce-users]

Unfortunately,  there is no simple answer to that question.  It depends on the exact nature of each failure.  You'll have to dig through the results and see what is going wrong.

The results should be in the Xyce_Test/Netlists subdirectory of the directory in which you ran "run_xyce_regression" if you used the recommended command line.

The tests most likely to be worrisome are the EXITED WITH ERROR tests --- that message usually means that Xyce crashed in some way, but in some tests it could also mean that some other part of the test process specific to that test case failed.

The FAILED test cases mean that Xyce produced results that do not agree with the "gold standard" to sufficient accuracy.

For the EXITED WITH ERROR cases, look in the test directory (e.g. Xyce_Test/Netlist/PREPROC_ADDRES) and check all the files with "out" or "err" suffixes.  These should tell you what is happening.  The nodcpath and oneterm tests use a lot of helper scripts, and will throw the "EXITED WITH ERROR" if those helper scripts fail, even if Xyce worked.  In those cases, the failure could possibly be unimportant.  The BUG_141_SON test is more likely to be a problem --- it is only going to fail when Xyce itself fails, so you'll have to look through and see what failed. 

For the FAILED tests, look at the ".cir.prn.err" files in the associated directory.  They should tell you what signal is failing comparison, and by how much. 

[Roshni Uppala]

I am not totally confident that I understand these errors. I have seen the bug_141_son folder and there were two files which brought up the error.

From the first file, I think Xyce crashed !

From the second file, I think trilinos was not properly configured?

Also , I wanted to add. There was one different thing I did while building Xyce. Instead of using system lapack (intelmkl), I built a lapack package, and linked its path in the building process of Xyce. Does this make any difference?

Exited with error: BUG_141_SON

1.     bug_141-empty.cir.stdout -Failed mpirun -np 2 /nfs/15/uda0235/XyceParallel/src/Xyce -linsolve aztecoo
2. dig_count.out -
   

 AMD ORDERING: Invalid!!!!
/nfs/15/uda0235/trilinos-11.6.1-Source/packages/belos/epetra/src/BelosEpetraAdapter.cpp:816:

Throw number = 1

Throw test that evaluated to true: info != 0

Belos::OperatorTraits::Apply (Epetra specialization): Calling the Epetra_Operator object's Apply() method failed, returning a nonzero error code of -1.
Developer error: Caught std::exception in N_NLS_NOX::Interface::solve()!

Thanks

-Roshni

--
You received this message because you are subscribed to a topic in the Google Groups "xyce-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/xyce-users/BmvKxYhwces/unsubscribe.
To unsubscribe from this group and all its topics, send an email to xyce-users+...@googlegroups.com.
To post to this group, send email to xyce-...@googlegroups.com.
Visit this group at http://groups.google.com/group/xyce-users.
For more options, visit https://groups.google.com/d/optout.