[SERVER-47365] Master (v4.5) branch's last-stable is pinned to an old v4.3 binary that lacks the latest v4.4 backported bug fixes Created: 06/Apr/20 Updated: 24/Jul/20 Resolved: 15/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Robert Guo (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | STM 2020-04-20 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 37 | ||||||||
| Description |
|
Per the linked test failure, a fix was committed after the commit chosen for last-stable in master, and so the test continues to fail (in this particular test instance, a lot). It seems like all the v4.4 backported bug fixes since March 1st are not present in the master branch's multiversion tests? The commit being used for last-stable in master is a WT drop from March 1st. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 06/Apr/20 ] | ||
|
Ah, you're right, thanks max.hirschhorn! The failures only go out to March and the variant is green in the present. I'll close the test failure ticket. | ||
| Comment by Max Hirschhorn [ 06/Apr/20 ] | ||
|
dianna.hohensee, it looks like the failures stopped happening after we started download the 4.3.5 version rather than the 4.3.4 version.
|