Mailing-List: contact dev-help@singa.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@singa.incubator.apache.org
Date: Thu, 6 Oct 2016 08:15:20 +0000 (UTC)
From: "wangwei (JIRA)" <jira@apache.org>
To: dev@singa.incubator.apache.org
Message-ID: <JIRA.12949659.1457841114000.751113.1475741720803@Atlassian.JIRA>
In-Reply-To: <JIRA.12949659.1457841114000@Atlassian.JIRA>
References: <JIRA.12949659.1457841114000@Atlassian.JIRA> <JIRA.12949659.1457841114680@arcas>
Subject: [jira] [Closed] (SINGA-148) Race condition between Worker threads
 and Driver
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 06 Oct 2016 08:15:26 -0000


     [ https://issues.apache.org/jira/browse/SINGA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

wangwei closed SINGA-148.
-------------------------
    Resolution: Fixed

> Race condition between Worker threads and Driver
> ------------------------------------------------
>
>                 Key: SINGA-148
>                 URL: https://issues.apache.org/jira/browse/SINGA-148
>             Project: Singa
>          Issue Type: Bug
>         Environment: Tested on Debian 8.3
>            Reporter: Tan Li Boon
>              Labels: newbie
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In the main branch, a thread of execution for each worker is started before information about its device type is passed into it.
> This causes test cases such as MNIST to not use GPUs for calculation, and other test cases such as CIFAR10 to fail when it attempts to perform cudnn-based functions on the CPU.
> A temporary workaround is to make the worker thread sleep for 1 second, but that's not a desirable workaround.
> This issue aims to implement a proper fix.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)