Comment 8 for bug 1064679

This issue persists in Evergreen 3.1