[SERVER-23524] Compare version string in compile_expansions.yml to version string from MongoDB binary Created: 04/Apr/16  Updated: 21/Nov/16  Resolved: 20/Apr/16

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.0.13, 3.2.7, 3.3.5

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Jonathan Abrahams
Resolution: Done Votes: 1
Labels: test-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Backport Completed:
Sprint: TIG 13 (04/22/16)
Participants:
Linked BF Score: 0

 Description   

There have been a few cases recently where we somehow (on the mongodb-mongo-v3.2 project) end up running the 3.2 MongoDB binaries against tests from master. Until EVG-943 is implemented, all Evergreen projects are responsible for cleaning up directories they'll use themselves. We should add a check after extracting the artifacts and binaries that asserts the version string in compile_expansions.yml from the artifacts is identical to the version string from one of the MongoDB binaries (e.g. the mongo shell).

compile_expansions.yml

suffix: latest
src_suffix: latest
version: 3.3.3-217-gae3ee1c



 Comments   
Comment by Githook User [ 09/May/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-23524 Compare version string in compile_expansions.yml to version string from MongoDB binary

(cherry picked from commit e09d6916fdf3ea6502dfd44d4a6d28907bf3d13f)
Branch: v3.0
https://github.com/mongodb/mongo/commit/6cfb60e1cb3a71d03015287606c2f69f04b12ee8

Comment by Githook User [ 28/Apr/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-23524 Compare version string in compile_expansions.yml to version string from MongoDB binary

(cherry picked from commit e09d6916fdf3ea6502dfd44d4a6d28907bf3d13f)
Branch: v3.2
https://github.com/mongodb/mongo/commit/7748779894ce6e5b21cf75d93040c5fe1826d0a2

Comment by Githook User [ 20/Apr/16 ]

Author:

{u'username': u'hptabster', u'name': u'Jonathan Abrahams', u'email': u'jonathan@mongodb.com'}

Message: SERVER-23524 Compare version string in compile_expansions.yml to version string from MongoDB binary
Branch: master
https://github.com/mongodb/mongo/commit/e09d6916fdf3ea6502dfd44d4a6d28907bf3d13f

Comment by Michael O'Brien [ 06/Apr/16 ]

It looks like the pre-task cleanup step ( https://github.com/mongodb/mongo/blob/9ae3e32320a71a46c6a236187b0dc00f8844ddb7/etc/evergreen.yml#L444 ) didn't effectively remove the data from the previous run, because regardless of what happened in the last task than ran (system timeout) the rm -rf should have deleted any old binaries, but it didn't. Since we are using an explicit exit 0 in the script block, its possible that rm -rf actually failed but the task proceeded anyway.
It's not clear to me what state the previous agent run could have created that would cause rm -rf to be ineffective, so I don't have an underlying evergreen issue to point to. In any case EVG-943 should take care of it completely.

Generated at Thu Feb 08 04:03:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.