Skip to content
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.

Sign up for GitHub

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

Jump to bottom

invoking e2e scripts locally should work #2681

Open
dprotaso opened this issue Mar 1, 2021 · 3 comments
Open

invoking e2e scripts locally should work #2681

dprotaso opened this issue Mar 1, 2021 · 3 comments
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.

Comments

@dprotaso
Copy link
Member

dprotaso commented Mar 1, 2021

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
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen.Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 30, 2021
@dprotaso
Copy link
Member Author

/lifecycle frozen

@knative-prow-robot knative-prow-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 31, 2021
@upodroid
Copy link
Member

/assign @upodroid

@upodroid upodroid moved this to In Design/Discussion in Infra (Productivity) Jun 6, 2022
@upodroid upodroid added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jun 15, 2022
@upodroid upodroid mentioned this issue Sep 27, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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.
Projects
Infra (Productivity)
Status: In Design/Discussion
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dprotaso @upodroid @knative-prow-robot