After Jeff Godin asked about this bug in IRC today (), I decided to remove its duplicate status with bug bug 1766716. While that other bug does rectify this behavior, it does so only in Evergreen 3.2 and later releases. This issue is still open in Evergreen 3.1.
I believe that this bug should still stand on its own so it can be found via bug search, etc.
There is also the chance that someone may fix this bug in 3.1.
After Jeff Godin asked about this bug in IRC today (), I decided to remove its duplicate status with bug bug 1766716. While that other bug does rectify this behavior, it does so only in Evergreen 3.2 and later releases. This issue is still open in Evergreen 3.1.
I believe that this bug should still stand on its own so it can be found via bug search, etc.
There is also the chance that someone may fix this bug in 3.1.