[SERVER-83127] enterprise-rhel-80-64-bit-future-git-tag-multiversion runs old jstests against newer versions of the server Created: 10/Nov/23 Updated: 16/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | George Wangensteen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Correctness
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 13 | ||||
| Description |
|
This build variant uses `db-contrib-tool` to pull down existing branch binaries that may be newer than the server commit that it is building from. It then builds from that commit with a new git-tag to simulate a higher-version release, and runs it in a multiversion cluster with the existing branch binaries to try and ensure that new release tags don't break tests. However, because the existing branch binaries may actually be newer than the version it is building from, it may be running jstests that are out-of-date relative to the binaries it pulled. For example, if a failpoint is renamed from "name1" to "name2" in a commit between the one being tested and the one the existing-branch-builds are from, the pulled binaries will expect "name2" but the jstests will use "name1", therefore breaking the tests. |
| Comments |
| Comment by Janna Golden [ 14/Nov/23 ] |
|
I also saw a failure where the git hash picked by the db contrib tool for the "older" version was too old (see BF-30804 for an explanation). We should use the same git hash for both "older" and "newer" versions, and just fake the version number. |