This is a long-standing intermittent bug somewhere in {DrDr, promises,
rackunit, TR's use of rackunit} that no one has, to my knowledge, made
any progress in tracking down.Perhaps the thread is being killed by DrDr at some point, although I have reproduced it at the command line. Sam On Thu, Apr 4, 2013 at 1:33 PM, Eric Dobson <eric.n.dob...@gmail.com> wrote: > Sometimes TR tests fail with the error > > force: promise's thread terminated without result or exception > > promise: #<promise:!running!...et/optimizer/run.rkt:47:28> > > context...: > > /opt/plt/builds/<current-rev>/trunk/collects/racket/promise.rkt:98:2 > > > /opt/plt/builds/<current-rev>/trunk/collects/tests/typed-racket/optimizer/run.rkt:50:3: > for-loop > > > /opt/plt/builds/<current-rev>/trunk/collects/tests/typed-racket/optimizer/run.rkt:44:0: > mk-suite > > How can this happen? Is the thread getting killed? Also since this > error doesn't have blame information I don't know if this is an > internal promise error or if TR is misusing the promise library. > _________________________ > Racket Developers list: > http://lists.racket-lang.org/dev _________________________ Racket Developers list: http://lists.racket-lang.org/dev
