[Swift-devel] job success in the presence of massive brokenness

[Ben Clifford]

I have been interested to see how over the past few days fairly large job 
failure rates (on the order of 30%) have still been able to run successful 
job completions and (with appropriately hacked scheduler) not get stuck at 
an appallingly slow completion rate.

Eventually when some real investigation happens in the scheduler, putting 
in articificially broken job/file transfer submission to see how things 
perform will be an interesting thing to do.

--