mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Olivier <cjolivie...@gmail.com>
Subject Re: Killed builds
Date Thu, 29 Mar 2018 22:17:38 GMT
Kellen got the call stacks. I reproduced once so far locally.

On Thu, Mar 29, 2018 at 2:55 PM, Marco de Abreu <
marco.g.abreu@googlemail.com> wrote:

> Thank you, Chris!
>
> What's interesting here (e.g. at [1]) is the matter of the fact that all
> tests are actually finishing, but the process does not terminate. I have
> experienced such a behaviour in my past C# and Java projects. In these
> cases, it was related to threads being created as non-foreground-threads or
> threadpools that have not been disposed and thus causing the process to
> stay alive until explicitly terminated. Does anybody remember a change to
> the threading in the last days or has a better idea what this could be
> related to?
>
> -Marco
>
> [1]:
> http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/
> incubator-mxnet/detail/PR-10308/5/pipeline/586
>
> On Thu, Mar 29, 2018 at 7:44 PM, Chris Olivier <cjolivier01@gmail.com>
> wrote:
>
> > I killed several builds which were > 11 hours old -- all stuck at this
> > python3 GPU hang problem
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message