Piro: Failing test Piro_EpetraSolver_MPI_4 in SEMS MPI_RELEASE_DEBUG_SHARED_ST build

[bartlettroscoe]

Next Action Status:

Disabled failing test for the checkin-test-sems.sh script. Next: Fix the failing test?

CC: @trilinos/framework, @trilinos/thyra, @agsalin

Description:

When trying to push a change to Trilinos enabling all of the packages, I got a failing test Piro_EpetraSolver_MPI_4. This was generated on the machine muir using:

$ ./checkin-test-sems.sh --default-bulids= \
  --st-extra-builds=MPI_RELEASE_DEBUG_SHARED_ST \
  --enable-all-packages=off --no-enable-fwd-packages --enable-packages=Piro \
  --local-do-all

The Trilinos version was:

307a5b3 "Fixed a bug in the OED objective where a vector was cloned [...]"
Author: Denis Ridzal <dridzal@sandia.gov>
Date:   Wed Jul 13 19:04:03 2016 -0600 (11 hours ago)

M       packages/rol/example/PDE-OPT/adv-diff-react/ROL_ExperimentDesignObjective.hpp

The failing test shows:

p=0: *** Caught standard std::exception of type 'Thyra::Exceptions::IncompatibleVectorSpaces' :

 /home/rabartl/Trilinos.base.again/Trilinos/packages/thyra/adapters/epetra/src/Thyra_EpetraThyraWrappers.cpp:634:

 Throw number = 1

 Throw test that evaluated to true: !l_isCompatible

 Thyra::get_Epetra_MultiVector(map,mv)

 Error, the following vector spaces are not compatible:

  *epetra_vs : Thyra::DefaultSpmdVectorSpace<double>{globalDim=1,localSubDim=1,localOffset=0,comm=Teuchos::MpiComm<long>{size=4,rank=0,rawMpiComm=0x6a2120}}

  *mv->range() : Thyra::DefaultSpmdVectorSpace<double>{globalDim=2,localSubDim=2,localOffset=0,comm=Teuchos::MpiComm<long>{size=4,rank=0,rawMpiComm=0x6a2120}}

It does not looks like a debug-mode (-DTrilinos_ENABLE_DEBUG=ON) ever gets run in post-push automated testing from looking at:

• http://testing.sandia.gov/cdash/queryTests.php?project=Trilinos&date=2016-07-11&limit=200&filtercount=1&showfilters=1&limit=200&field1=testname/string&compare1=61&value1=Piro_EpetraSolver_MPI_4

So the only build that Piro tests are ever run in is the one CI build (that does not even turn on debug-mode checking)!

Tasks:

1. Disable failing test for the checkin-test-sems.sh script to allow pushes (see below) [Done]
2. Fix failing test and reenable ...

[bartlettroscoe]

This stopped my push related to #441 and #87. Therefore, I will disable in the checkin-test-sems.sh script to allow my push.

[bartlettroscoe]

I disabled this test for the debug builds in the commit 7e004c4. Now someone just needs to fix this.

Since there appears to be no post-push automated testing that will see this failure, someone will need to reproduce the failure themselves. They can do that by reverting the commit 7e004c4 and then running the checkin-test-sems.sh script as described in the description above.

Who should be assigned this Issue ticket? Since the test is disabled in pre-push testing, it is no urgency to fix from my perspective (but Piro developers should care).

[github-actions]

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.

[github-actions]

This issue was closed due to inactivity for 395 days.