Looking at the testcomponent above, I suspect you are trying to show the absense of an error, which is impossible to do.
Do you remember what property of the scheduler you are trying to confirm here?
Maybe I can turn this test into an confirmation of how the scheduler is supposed to work.
J. Paul Morrison
That's a very good question! I think the key is in the component GenerateSlowly, which does a create and send at 1-second intervals. The deadlock detection basically checks to see if anything is running at 1/2-second intervals, so there was the risk that it might think that a deadlock had occurred. So I believe I had to add code to the deadlock detection logic to make sure that this didn't happen. If this test completes normally, then deadlock detection is not giving false positives (at least not for that reason)! I think that is right - it's been a few years! Not sure how you want to document this...
OK, thanks. I will see if I can turn this into a positive test case.