Re: What GPU can be assumed for autopkgtests

2017-01-15 Thread Nicholas Breen
On Mon, Jan 16, 2017 at 10:21:57AM +0800, Paul Wise wrote:
> On Mon, Jan 16, 2017 at 12:12 AM, Andreas Tille wrote:
> 
> > I remember these messages in connection with some (other?) package on
> > autobuilders but I can't make up my mind which one and I'm obviously
> > doing the wrong web search queries.
> 
> I don't know enough about OpenMPI and the logs you posted don't seem
> to mention the underlying cause of not being able to start the daemon,
> so I'm not sure, sorry. Maybe try stracing it?

Perhaps #494046 ?  One of my packages still requires the suggested workaround,
setting OMPI_MCA_plm_rsh_agent=/bin/false .

#839387 is also relevant when it gets to autobuilding on the non-Linux kernels.



-- 
Nicholas Breen
nbr...@debian.org



Re: What GPU can be assumed for autopkgtests

2017-01-15 Thread Paul Wise
On Mon, Jan 16, 2017 at 12:12 AM, Andreas Tille wrote:

> I remember these messages in connection with some (other?) package on
> autobuilders but I can't make up my mind which one and I'm obviously
> doing the wrong web search queries.

I don't know enough about OpenMPI and the logs you posted don't seem
to mention the underlying cause of not being able to start the daemon,
so I'm not sure, sorry. Maybe try stracing it?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



Re: What GPU can be assumed for autopkgtests

2017-01-15 Thread Andreas Tille
Hi Paul,

On Sun, Jan 15, 2017 at 09:17:27PM +0800, Paul Wise wrote:
> 
> It is unlikely any buildd, puiparts host or debci host has a GPU.
> Often they are virtual machines with only serial console for input if
> any. So the safe bet for OpenCL is the CPU-based ICD, pocl-opencl-icd.

OK, seems I'm at least half-way through.  Now I get:


DNA interleaved sequence file, default parameters :
Could not create topdir for cache[autopkgtest-lxc-kivtvg:02003] 
[[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node 
in file ess_singleton_module.c at line 597
[autopkgtest-lxc-kivtvg:02003] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to 
start a daemon on the local node in file ess_singleton_module.c at line 168
--
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  orte_ess_init failed
  --> Returned value Unable to start a daemon on the local node (-127) instead 
of ORTE_SUCCESS
--
--
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems.  This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):

  ompi_mpi_init: ompi_rte_init failed
  --> Returned "Unable to start a daemon on the local node" (-127) instead of 
"Success" (0)
--
*** An error occurred in MPI_Init
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***and potentially your MPI job)
[autopkgtest-lxc-kivtvg:2003] Local abort before MPI_INIT completed completed 
successfully, but am not able to aggregate error messages, and not able to 
guarantee that all other processes were killed!


I remember these messages in connection with some (other?) package on
autobuilders but I can't make up my mind which one and I'm obviously
doing the wrong web search queries.

Any further hints?

Thanks so far in any case

  Andreas.


-- 
http://fam-tille.de



Re: What GPU can be assumed for autopkgtests

2017-01-15 Thread Paul Wise
On Sun, Jan 15, 2017 at 9:07 PM, Andreas Tille wrote:

> Is there any hint how this test can be run on the autopkgtest
> hardware?

It is unlikely any buildd, puiparts host or debci host has a GPU.
Often they are virtual machines with only serial console for input if
any. So the safe bet for OpenCL is the CPU-based ICD, pocl-opencl-icd.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise