invoking e2e scripts locally should work #2681
Labels
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
test-infra/hack makes this difficult
ie. in serving running ./test/e2e-upgrade-test.sh doesn't work because the GCP project i'm setting isn't passed to kntest etc.
changing the provider to kind breaks because kntest flags are passed to kubetest2 which aren't supported
The text was updated successfully, but these errors were encountered: