Comment 2 for bug 1162907

Revision history for this message
Jason Stephenson (jstephenson) wrote :

Since 2.3.4 is the previous release of Evergreen and this was fixed in Evergreen 2.3.5, I would be inclined to set the status of this bug as invalid. I recommend anyone encountering this to install 2.3.5 instead of 2.3.4.