Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update xversion test script #140

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update xversion test script #140

wants to merge 1 commit into from

Conversation

rhc54
Copy link
Contributor

@rhc54 rhc54 commented Jul 31, 2022

Don't cross-version with the target branch as that
is the one we are trying to change.

Signed-off-by: Ralph Castain [email protected]

Don't cross-version with the target branch as that
is the one we are trying to change.

Signed-off-by: Ralph Castain <[email protected]>
@rhc54
Copy link
Contributor Author

rhc54 commented Jul 31, 2022

bot:ibm:retest

invalid_pairs.append([bld.branch,"v4.1"])
invalid_tool_pairs.append([bld.branch,"v4.1"])
invalid_pairs.append(["v4.1", bld.branch])
invalid_tool_pairs.append(["v4.1", bld.branch])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not make a more general block outside of the selection logic like:

          # Do not test the Build branch against the Target branch.
          # If we are fixing cross-version issues then this is likely to fail which is correct in this circumstance.
          invalid_pairs.append([bld.branch, target_branch])
          invalid_pairs.append([target_branch, bld.branch])
          invalid_tool_pairs.append([bld.branch, target_branch])
          invalid_tool_pairs.append([target_branch, bld.branch])

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'm not entirely wild about this patch just yet. We don't want to test against the HEAD of the specific target branch as that is what we are changing, but we do want to test against any prior tagged releases in that branch to ensure we aren't breaking compatibility within the series. Still scratching my head over it. Your suggestion would indeed clean things up - just not sure yet what the logic should be to get what we really want.

Hope that makes some sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants