Deadlock analysis only runs in the Exit phase

[wthrowe]

This is documented, but it doesn't seem like desirable behavior. If the executable hangs in anything other than the last phase, run_deadlock_analysis_simple_actions is not called. A workaround is to remove all the phases after the one that locks up from the executable's default_phase_order.

[knelli2]

So basically after every phase, all elements must report to the Main chare that they have successfully completed, otherwise deadlock analysis is run?

[wthrowe]

Hmm, yeah, I guess that would be required, which is a bit unpleasant.

I don't remember what the meanings of all the terminate-like flags are. Does each element know when the phase is over, independent of quiescence, or are all of the phase termination types potentially temporary? If they do, we could do the check at the end of the phase without needing an extra round trip message to Main.

[knelli2]

No, each individual element doesn't know when the phase is over. They just know if they have completed or are waiting for another communication. Only Main knows when there's a phase change because it is the one that starts the next phase.