Open GoogleCodeExporter opened 8 years ago
OMG! Is this truly a bug?! Is this really the way fluint works? I've spent
the last week trying to figure out what is really going wrong in my unit tests,
but usually get a timeout error. It makes debugging fluint almost impossible!!!
Original comment by dtaylor...@gmail.com
on 25 Oct 2012 at 6:32
I just tried this sample TestCase in fluint r269 and it is still doing this
behavior. This makes debugging where and why a test failed nearly impossible
when using async.
I see the original post also included a fix back in 2009, and it still hasn't
been addressed?! Making me very sad that we are using fluint ;-(
Original comment by dtaylor...@gmail.com
on 25 Oct 2012 at 6:58
Original issue reported on code.google.com by
amfr...@gmail.com
on 28 Jul 2009 at 6:58Attachments: