This repository has been archived by the owner on Sep 5, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 159
test/e2e-tests.sh fails when run locally #286
Labels
Comments
google-prow-robot
added
area/test-and-release
Test infrastructure, tests or release
kind/bug
Something isn't working
labels
Jul 25, 2018
I can't reproduce, the environment spins up and the tests run as expected. Could it be that we have different
|
Just saw the line in the log, maybe it's
Can you please try |
e2e tests aren't running locally anymore (getting from HEAD):
|
knative/test-infra#87 should have fixed that. |
For the record, 87 is part of the fix, thus 115 was necessary. |
knative-prow-robot
pushed a commit
that referenced
this issue
Sep 14, 2018
* Ignore not found entities when cleaning up namespace for the e2e tests * Group test logging messages, making them consistent * Update knative/test-infra to the latest version mostly to to * fix the test cluster authentication when running e2e tests locally * fix the parsing of e2e test results in same cases Fixes #286
vdemeester
pushed a commit
to vdemeester/knative-build
that referenced
this issue
Apr 3, 2019
* Ignore not found entities when cleaning up namespace for the e2e tests * Group test logging messages, making them consistent * Update knative/test-infra to the latest version mostly to to * fix the test cluster authentication when running e2e tests locally * fix the parsing of e2e test results in same cases Fixes knative#286
vdemeester
pushed a commit
to vdemeester/knative-build
that referenced
this issue
Apr 3, 2019
* Ignore not found entities when cleaning up namespace for the e2e tests * Group test logging messages, making them consistent * Update knative/test-infra to the latest version mostly to to * fix the test cluster authentication when running e2e tests locally * fix the parsing of e2e test results in same cases Fixes knative#286
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Expected Behavior
I can run
./test/e2e-tests.sh
to run end-to-end tests before submitting a PR.Actual Behavior
Script creates a cluster, network, firewall rules, etc., then fails due to an unknown flag:
This seems to come from
library.sh
here, at least that's the only instance of--username
I could find anywhere in the test-infra repo.The text was updated successfully, but these errors were encountered: