[SERVER-50397] Move Jepsen smoke test to a separate builder Created: 20/Aug/20  Updated: 27/Oct/23  Resolved: 30/Jan/23

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

Type: Task Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Robert Guo (Inactive)
Resolution: Gone away Votes: 0
Labels: tig-evgconfig
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Story Points: 1

 Description   

The Jepsen smoke test currently runs on the AUBsan builder but has been consistently purple due to timing issues even though the real Jepsen tasks has been green. We should move it to a separate builder to avoid stability issues.



 Comments   
Comment by Jeffrey Zambory [ 30/Jan/23 ]

Gotcha, that makes sense, thanks max.hirschhorn@mongodb.com !

I'm closing this ticket as "Gone Away" alexander.neben@mongodb.com , feel free to re-open if you think you'd like to re-enable that task one day.

Comment by Max Hirschhorn [ 30/Jan/23 ]

jeff.zambory@mongodb.com, my understanding is the jepsen-smoke Evergreen task wasn't stable and got disabled as part of SERVER-49203. I don't know of a ticket to re-enable it and so if SDP is happy to keep it disabled then I think we can close SERVER-50397 as "Gone away". The intention behind the jepsen-smoke Evergreen task was to ensure server code changes don't break Jepsen running as there had been one or two instances where this had happened before.

Comment by Jeffrey Zambory [ 30/Jan/23 ]

max.hirschhorn@mongodb.com Do you know if this is still occurring and still should be something we're tracking? 

Comment by Robert Guo (Inactive) [ 03/Sep/20 ]

Moving this to the backlog for now given the additional complexity with dynamic builds.

Generated at Thu Feb 08 05:22:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.