Accéder au contenu.
Menu Sympa

starpu-devel - Re: [Starpu-devel] parallel_tasks test failures

Objet : Developers list for StarPU

Archives de la liste

Re: [Starpu-devel] parallel_tasks test failures


Chronologique Discussions 
  • From: Cyril Roelandt <cyril.roelandt@inria.fr>
  • To: bicatali@gentoo.org
  • Cc: starpu-devel@lists.gforge.inria.fr
  • Subject: Re: [Starpu-devel] parallel_tasks test failures
  • Date: Fri, 17 Aug 2012 16:45:04 +0200
  • List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel>
  • List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>

On 08/16/2012 09:44 PM, Sébastien Fabbro wrote:
Hello,


Hello,


I'm seeing failures [1] for two tests while running the test suite of starpu:

FAIL: parallel_tasks/parallel_kernels
=====================================

[error] test has been blocked for 600 seconds. Mark it as failed

FAIL: parallel_tasks/parallel_kernels_spmd
==========================================

[error] test has been blocked for 600 seconds. Mark it as failed


Is this something I should worry about?


Thanks for reporting this bug.

These tests use the "Parallel Heft" scheduler, which is still kind of experimental. If you can easily reproduce this bug, could you please run these tests in gdb, wait for them to hang, run "thread apply all bt" and send us the output ? I think this is a mutex problem, and I'd like to know which threads are waiting, and which mutexes are involved.

Cyril Roelandt.





Archives gérées par MHonArc 2.6.19+.

Haut de le page