That could be right -- sorry, haven't had time to unwind it further.  If I'm understanding correctly, that would make the double postStop a testing-only occurrence; but I don't think that it will hurt anything to always remove jobs from activeJobs after they are handled in postStop, so that if/when postStop does run more than once there is nothing more to do in `for (job <- dagScheduler.activeJobs)`.