[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 |
| 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. |