Closed crandles closed 1 week ago
Hi @crandles. 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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
@crandles this is awesome and thanks for the contribution. At first glance it looks Okay, but I will ask @harshanarayana to take a look as well since he's the E2E provider expert 😉
/retest
Updated copyright, verify-boilerplate passes locally now.
/retest
golangci appears to be passing now for thew new code I've added, though errirng for some existing LOC:
third_party/helm/helm.go:240:9: SA1006: printf-style function with dynamic format string and no further arguments should use print-style function instead (staticcheck)
err = fmt.Errorf(missingHelm)
^
third_party/flux/flux_setup.go:47:16: SA1006: printf-style function with dynamic format string and no further arguments should use print-style function instead (staticcheck)
return ctx, fmt.Errorf(NoFluxInstallationFoundMsg)
^
third_party/flux/flux_setup.go:61:16: SA1006: printf-style function with dynamic format string and no further arguments should use print-style function instead (staticcheck)
return ctx, fmt.Errorf(NoFluxInstallationFoundMsg)
^
pkg/env/env.go:229:11: printf: non-constant format string in call to (*testing.common).Skipf (govet)
t.Skipf(message)
^
pkg/env/env.go:513:22: printf: non-constant format string in call to (*testing.common).Skipf (govet)
internalT.Skipf(message)
Assuming that won't block this PR.
@harshanarayana and @cpanato any idea why golangci failing on previously working code ?
errors were primarily for:
SA1006: printf-style function with dynamic format string and no further arguments should use print-style function instead (staticcheck)
It's possible that I'm using a different toolchain version, but as the warning seemed fair, I've fixed it via https://github.com/kubernetes-sigs/e2e-framework/pull/450/commits/cf9cbf28dfc7a407ed901b2da26b31ef4aabcc35
make verify
now passes locally.
@crandles is this ready to go now ?
Yes, I believe so
rebased due to go.mod conflict
@harshanarayana @ShwethaKumbla @cpanato PTAL I think we need a second reviewer.
I will check by eod tomorrow.
Seems to fail installing vcluster; can't reproduce. Any tips? I think I'm installing vcluster the same way other tools are (ko|kwok|kind)
Seems to fail installing vcluster; can't reproduce. Any tips? I think I'm installing vcluster the same way other tools are (ko|kwok|kind)
@crandles
Helm and flux are installed slightly in a different way, https://github.com/kubernetes-sigs/e2e-framework/blob/777cbcd59fbbe572b71dde89c8f7b0b1a5ddc4a7/hack/install-helm.sh
test: install-helm install-flux ## Runs golang unit tests
./hack/test-go.sh
But you are right about ko or kwok though
/retest
Is there a recommended way to simulate the prow test runner locally?
This looks relevant: https://docs.prow.k8s.io/docs/build-test-update/#running-a-prowjob-locally (and this job), I'll try to follow it.
Trying this out so far, not quite working yet:
# new makefile target
run-pr-tests:
mkdir -p ./build ./build/out ./build/node_dir
curl -s -o build/e2e-framework-presubmits.yaml https://raw.githubusercontent.com/kubernetes/test-infra/master/config/jobs/kubernetes-sigs/e2e-framework/e2e-framework-presubmits.yaml
curl -s -o build/pj-on-kind.sh https://raw.githubusercontent.com/kubernetes-sigs/prow/refs/heads/main/pkg/pj-on-kind.sh
curl -s -o build/prow-config.yaml https://raw.githubusercontent.com/kubernetes/test-infra/refs/heads/master/config/prow/config.yaml
NODE_DIR=$(realpath build/node_dir) OUT_DIR=$(realpath build/out) CONFIG_PATH=$(realpath build/prow-config.yaml) JOB_CONFIG_PATH=$(realpath build/e2e-framework-presubmits.yaml) bash ./build/pj-on-kind.sh pull-e2e-framework-test
found/resolved a couple of issues:
/ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, crandles, vladimirvivien
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Thanks for the reviews!
I will try to rebase next time, and I may follow up with an issue about how to run the pr tests locally. I need to spend more time looking at the pj on kind script.
addition of vcluster provider; interested to see if the CI fails. vcluster needs a "host" cluster to launch into, so I've followed an existing example where a real cluster or kind cluster are utilized as necessary: https://github.com/kubernetes-sigs/e2e-framework/blob/9206e6f6082907a1c77750b7cac0fc44ff4dac02/examples/real_cluster/main_test.go#L39
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR enables a new
E2EClusterProvider
forvcluster
based clusters.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., Usage docs, etc.: