-
Notifications
You must be signed in to change notification settings - Fork 492
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
conformance-profile: Remove experimental build tag #2327
conformance-profile: Remove experimental build tag #2327
Conversation
Hi @sayboras. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
Thanks for this PR, @sayboras!
/ok-to-test |
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.
...hmmmm. When I tried a conformance run from the CLI with the experimental
build tag enabled, it tried to run TestConformance
and then TestExperimentalConformance
, and TestExperimentalConformance
failed because it was expecting an empty cluster to play in.
This PR leaves both functions intact, and I would expect it to fail because of that. If the idea is that the stuff previously tagged with experimental
is now OK to include everywhere, I'd expect to see TestExperimentalConformance
go away?
Yes, understand that cleaning up of similar/duplicated code is required to |
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 thanks !
/approve
d90f0f4
to
231624f
Compare
231624f
to
d0c1ce1
Compare
This is to make it easier for some implementation that imports the conformance test framework and run tests in the same codebase. Understand that cleaning up of similar/duplicated code is required to have a clean conformance test framework, however, such work might delay v1.0.0 GA release, hence, I only remove the build tag to remove the soft blocker in this PR. Subsequent cleanup/optimization can be done later. Relates: kubernetes-sigs#2242 Signed-off-by: Tam Mach <[email protected]>
d0c1ce1
to
f9a8505
Compare
The previous CI failure was due to recent renaming in main (e.g. HTTPExtendedFeatures -> HTTPRouteExtendedFeatures). The current failure seems to be unrelated to this PR. |
@sayboras, the linter is complaining. It looks like you need to do some |
Signed-off-by: Tam Mach <[email protected]>
bcf09fd
to
14c1d85
Compare
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.
/approve
/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.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: arkodg, sayboras, shaneutt 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 |
What type of PR is this?
/kind test
/area conformance
What this PR does / why we need it:
Which issue(s) this PR fixes:
Relates: #2242
Does this PR introduce a user-facing change?:
Testing was done as part of cilium/cilium#27596