-
Notifications
You must be signed in to change notification settings - Fork 114
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
Remove multi-hypervisor testing in molecule #1754
Remove multi-hypervisor testing in molecule #1754
Conversation
Skipping CI for Draft Pull Request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Patch looks good, before merging it would be good to update these two (any any others you know of) saying this feature isn't tested/supported:
This feature will make IPv6 support addition far too complicated for now, and since it's apparently not used nor really advertised, let's "just" stop testing it. Reverting the whole feature would be too complicated as well - and we might want to get it back in the future.
ef34039
to
c1ef8b7
Compare
@lewisdenny there's also an open MR in downstream doc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pablintino The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This feature will make IPv6 support addition far too complicated for
now, and since it's apparently not used nor really advertised, let's
"just" stop testing it.
Reverting the whole feature would be too complicated as well - and
we might want to get it back in the future.
As a pull request owner and reviewers, I checked that: