test/conformance/api/v1beta1.TestDomainMapping is being skipped in Prow but passing in Kind #15203
Labels
kind/question
Further information is requested
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
Question
Can we consider removing the snippet that drops the
enable-alpha
andenable-beta
flags from e2e-tests.sh script for gateway-api testing?Context
Currently, tests such as
test/conformance/api/v1beta1.TestDomainMapping
and a few others tests related to alpha and beta features are currently being skipped in Prow, as observed in gateway-api-contour and gateway-api-istio. This skipping appears to be due to the removal ofenable-alpha
andenable-beta
flags for gateway-api in the e2e-tests.sh script here:serving/test/e2e-tests.sh
Lines 45 to 49 in 40088e3
However, some tests that run in Kind (GitHub Actions) don't use the e2e-tests.sh script to run the tests and explicitly set the above-mentioned flags, resulting in successful test execution.
Important to note that in Kind, we only run end-to-end tests, not conformance tests. However, some alpha and beta features are successfully tested in Kind. The specific test mentioned in this issue, test/conformance/api/v1beta1.TestDomainMapping, is not run in Kind since it is a conformance test. Nevertheless, it was tested locally and passed.
serving/.github/workflows/kind-e2e.yaml
Lines 212 to 221 in 40088e3
Test PR with tests passing in Kind: #15202
The text was updated successfully, but these errors were encountered: