Two strategies:
1. Don't configure with VTK (that test depends on VTK and won't run if you
haven't configured with VTK)
2. You can run make check in the subdirectories directly and bypass that
example, using a shell script, for example.
John: Should I go ahead and change that one to XFAIL? I'm not sure it will
cause less confusion for users, but it would permit a blanket `make check`.
Downside is it won't show up as a failure on CIVET testing.
On Mon, Jan 22, 2018 at 12:42 PM, Daniel Vasconcelos <
daniel.f...@outlook.com> wrote:
> Thank you for the quick reply, I appreciate it.
>
> Is there a way to run the make check command and skip this example?
>
> Regards,
>
> Daniel F. M. Vasconcelos.
>
>
>
> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
> From: John Peterson<mailto:jwpeter...@gmail.com>
> Sent: Monday, January 22, 2018 15:38
> To: Daniel Vasconcelos<mailto:daniel.f...@outlook.com>
> Cc: libmesh-users<mailto:libmesh-us...@lists.sourceforge.net>;
> libmesh-devel<mailto:libmesh-devel@lists.sourceforge.net>
> Subject: Re: [Libmesh-users] Example fem_system_ex2 failing to run
>
>
>
> On Mon, Jan 22, 2018 at 10:35 AM, Daniel Vasconcelos <
> daniel.f...@outlook.com<mailto:daniel.f...@outlook.com>> wrote:
> Sorry, I have forgotten to include the actual libMesh configuration log.
>
> Once again. thanks in advance.
>
> Daniel F. M. Vasconcelos.
>
> 2018-01-22 15:28 GMT-02:00 Daniel Vasconcelos <daniel.f...@outlook.com<
> mailto:daniel.f...@outlook.com><mailto:daniel.f...@outlook.com<mailto:
> daniel.f...@outlook.com>>>:
> Dear libMesh users,
>
> Currently I am with problems when running example fem_system_ex2.
> MPI_ABORT is invoked in step 1 right after assembling the system (see
> attached file).
>
> Below is the setup I am using:
>
> * CPU: Intel i7
> * Oracle Virtual Box 5.2.6 r120293
> * Host system: Windows 10
> * Guest system: Linux Mint 18.3 Mate
> * Cloned libMesh master branch as per 01-21-2018
> * All libMesh optional libraries installed using apt-get (VTK,
> openMPI, PETSc, HDF5, …)
>
> I have also attached the libMesh configuration log and the fem_system_ex2
> traceout file.
>
> Thanks, we are aware of the issue, but not sure what the right fix is yet.
>
> (https://github.com/libMesh/libmesh/issues/1559<https://
> nam01.safelinks.protection.outlook.com/?url=https%3A%2F%
> 2Fgithub.com%2FlibMesh%2Flibmesh%2Fissues%2F1559&data=02%7C01%7C%
> 7C4f2c2890c38d4b31d54c08d561bf00ce%7C84df9e7fe9f640afb435aaaaaaaa
> aaaa%7C1%7C0%7C636522395328398299&sdata=eTEd2aYe3xE23iCBlf%
> 2FVhUAuZh9wIxYyFwOtLUPXF7s%3D&reserved=0>)
>
> --
> John
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Libmesh-users mailing list
> libmesh-us...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libmesh-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
