[SERVER-22777] Move ASAN builds to Arch Created: 19/Feb/16  Updated: 06/Dec/22  Resolved: 17/Jul/17

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

Type: Task Priority: Major - P3
Reporter: Ernie Hershey Assignee: Backlog - Build Team (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Build
Participants:

 Description   

Ubuntu 14.10 is EOL and we can run with new enough versions of everything on Arch.



 Comments   
Comment by Ramon Fernandez Marina [ 17/Jul/17 ]

ASAN builders were upgraded to Ubuntu 16.04 long ago, closing ticket.

Comment by Ernie Hershey [ 24/Feb/16 ]

We haven't defined yet how Arch updates will work but I think it will be "lurching" more than "rolling," and on-demand until we implement automated image updates from Evergreen. At that point it would be fully rolling, updating on every commit to the packer github repo, which come in batches around once per week.

I put this ticket in at Sam's request who can make a better case for it than me, possibly.

I think unless the goals of the ASAN builder include testing new clang versions, we should just use a sufficiently new non-arch image.

Comment by Andrew Morrow (Inactive) [ 20/Feb/16 ]

I'm generally in favor of the idea, however, I have two questions/concerns:

  • For the arch image, how are we managing rolling upgrade? Do we periodically re-build the image? Or have we just picked Arch at some arbitrary point in time and frozen there?
  • If we are rolliing forward, we may pick up new versions of clang and thus new behaviors out of ASAN. That could lead to strange situations where the ASAN build just suddenly breaks, and we can't get it green again easily.

I'm not sure those are real enough problems to warrant not doing this. An alternative to consider would be to wait a few months until Ubuntu 16.04 which is the new LTS and move ASAN there.

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