We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Environmental Info: When commits are made to branches in k3s-io, often in depedabot or other automated bot branches.
Describe the bug:
The new docker go tests see the "skew" test consistently fail, as the logic around "Determine parent branch" is does not handle commit branches.
Steps To Reproduce: https://github.com/k3s-io/k3s/actions/runs/12038906686/job/33565935782?pr=11336
Expected behavior: Skew test should find "master" or other "release-1.XX" branch as parent.
Actual behavior: Skew test finds the branch it is currently on as parent
Additional context / logs:
The text was updated successfully, but these errors were encountered:
Validated on #11336 as working again.
Sorry, something went wrong.
dereknola
No branches or pull requests
Environmental Info:
When commits are made to branches in k3s-io, often in depedabot or other automated bot branches.
Describe the bug:
The new docker go tests see the "skew" test consistently fail, as the logic around "Determine parent branch" is does not handle commit branches.
Steps To Reproduce:
https://github.com/k3s-io/k3s/actions/runs/12038906686/job/33565935782?pr=11336
Expected behavior:
Skew test should find "master" or other "release-1.XX" branch as parent.
Actual behavior:
Skew test finds the branch it is currently on as parent
Additional context / logs:
The text was updated successfully, but these errors were encountered: