Some more info I discovered.
The files that PETSc downloads are actually correctly installed in the
final installation directory during the configure phase. However,
somewhere between the configure and the install phase, something (I
suspect EasyBuild) deletes them. Is it possible that
Hi Shahzeb,
I looked at this kind of problem some time ago, and I created my own
"framework" (ie set of scripts) based on CTest/CDash.
You can find some slides about it and a video of the talk here:
https://archive.fosdem.org/2014/schedule/event/hpc_devroom_automatic_testing/
The code is
Hello,
I am curious if anyone knows of any Testing framework that can run test for a
particular application.
In order for me to write test I have to learn the software and write
appropriate test cases, this is very time-consuming. Similar to EasyBuild I am
wondering if there is a tool to do
On 17-02-22 14:08, Kenneth Hoste wrote:
Hi Maxime,
On 22/02/2017 17:22, Maxime Boissonneault wrote:
Actually, looking through the log file, I see PETSc which says to run
make install, but easybuild runs "make" without the install option:
3693 make[2]: Leaving directory
Hi Maxime,
On 22/02/2017 17:22, Maxime Boissonneault wrote:
Actually, looking through the log file, I see PETSc which says to run
make install, but easybuild runs "make" without the install option:
3693 make[2]: Leaving directory
'/dev/shm/mboisson/PETSc/3.7.5/iompi-2016.4/petsc-3.7.5'
3694
Actually, looking through the log file, I see PETSc which says to run
make install, but easybuild runs "make" without the install option:
3693 make[2]: Leaving directory
'/dev/shm/mboisson/PETSc/3.7.5/iompi-2016.4/petsc-3.7.5'
3694 =
3695 make[1]:
Hi Alan,
I don't think so. Looking at the source code of petsc.py, that skips the
"make install".
That would be if I wanted to compiled in the source directory and
expected it to remain there.
In the past, I have never done this except for OpenFOAM. Typically, the
"make install" of PETSc
Hi Maxime,
You are probably missing:
sourceinstall = True
in your easyconfig.
Alan
On 22 February 2017 at 17:03, Maxime Boissonneault <
maxime.boissonnea...@calculquebec.ca> wrote:
> Hi Inge,
> Thanks. I am trying to do this. However, while PETSc compiles fine, it
> seems that it does not
Hi Inge,
Thanks. I am trying to do this. However, while PETSc compiles fine, it
seems that it does not install hypre, metis, etc. in the petsc folder.
When I installed it manually (a different version though), it did copy
those files.
Have you run into this ?
Maxime
On 17-02-22 02:10,
Hi
We have a similar problem when building Theano on login nodes: MPI subsystem is
not available, so the sanity check fails.
Our workaround (not approved by Kenneth) is to skip the sanity check, see here:
No it's not submitted to a scheduler (the scheduler is configured in
EasyBuild but I'm not using it, ie. not using --job)
2017-02-22 12:52 GMT+01:00 Robert Schmidt :
> As a default sanity check for python packages, easybuild will try to
> import the main module. In this case
As a default sanity check for python packages, easybuild will try to import
the main module. In this case it seems like the import was enough to
trigger an mpi failure.
It is a bit weird that the import is enough to cause that problem, but
maybe there is something else in the environment that
Hello,
I'm back again with my problem (I had a similar problem with Rmpi), maybe
someone has an idea of what is going on.
I tried to install Theano-0.8.2-foss-2016a-Python-2.7.11.eb and had the
following error:
== 2017-02-22 11:19:25,788 build_log.py:147 ERROR EasyBuild crashed with an
error
13 matches
Mail list logo