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

When running integration tests, failure to find package error #784

Closed
jaypipes opened this issue Jan 1, 2020 · 2 comments
Closed

When running integration tests, failure to find package error #784

jaypipes opened this issue Jan 1, 2020 · 2 comments
Assignees
@jaypipes
Labels
bug testing

Comments

@jaypipes
Copy link
Contributor

jaypipes commented Jan 1, 2020

Getting the following after finally successfully getting aws-k8s-tester v0.5.2 to set up a cluster successfully:

Running integration tests

~/go/src/github.com/aws/amazon-vpc-cni-k8s/test/integration ~/go/src/github.com/aws/amazon-vpc-cni-k8s
# github.com/aws/amazon-vpc-cni-k8s/test/integration
integration_test.go:12:2: cannot find package "k8s.io/api/core/v1" in any of:
	/usr/local/go/src/k8s.io/api/core/v1 (from $GOROOT)
	/home/jaypipes/go/src/k8s.io/api/core/v1 (from $GOPATH)
FAIL	github.com/aws/amazon-vpc-cni-k8s/test/integration [setup failed]
@jaypipes
Copy link
Contributor Author

jaypipes commented Jan 2, 2020

the GO111MODULE=on env var needs to be set in the run-integration-tests.sh script I believe. Testing now...

@jaypipes jaypipes self-assigned this Jan 2, 2020
@jaypipes
Copy link
Contributor Author

jaypipes commented Jan 2, 2020

Yep, that was it. Adding to the script now.

jaypipes added a commit to jaypipes/amazon-vpc-cni-k8s that referenced this issue Jan 3, 2020
@jaypipes
update script to work with 0.5.4 aws-k8s-tester
5b7a46f 
The names of environment variables accepted by aws-k8s-tester changed
when the managed node group functionality was introduced. This commit
updates the integration testing scripts to call aws-k8s-tester (v.0.5.4
which is the release needed with the fix for aws/aws-k8s-tester#70) with
these updated environment variables.

We decrease the number of parallel builds of the echo job from 100 to
3 and the number of completions for that job from 1000 to 30. This
decreases the setup time of the cluster by about 10 minutes.

Finally, I added in a short-circuit to prevent double-deprovisioning of
the cluster if, say, a stacktrace occurred when running the
aws-k8s-tester tool.

Issue aws#686
Issue aws#784
Issue aws#786
@jaypipes jaypipes mentioned this issue Jan 3, 2020
Merged
jaypipes added a commit to jaypipes/amazon-vpc-cni-k8s that referenced this issue Jan 17, 2020
@jaypipes
update script to work with 0.5.4 aws-k8s-tester
3fb53de 
The names of environment variables accepted by aws-k8s-tester changed
when the managed node group functionality was introduced. This commit
updates the integration testing scripts to call aws-k8s-tester (v.0.5.4
which is the release needed with the fix for aws/aws-k8s-tester#70) with
these updated environment variables.

We decrease the number of parallel builds of the echo job from 100 to
3 and the number of completions for that job from 1000 to 30. This
decreases the setup time of the cluster by about 10 minutes.

Finally, I added in a short-circuit to prevent double-deprovisioning of
the cluster if, say, a stacktrace occurred when running the
aws-k8s-tester tool.

Issue aws#686
Issue aws#784
Issue aws#786
jaypipes added a commit to jaypipes/amazon-vpc-cni-k8s that referenced this issue Jan 17, 2020
@jaypipes
update script to work with 0.5.4 aws-k8s-tester
cf66674 
The names of environment variables accepted by aws-k8s-tester changed
when the managed node group functionality was introduced. This commit
updates the integration testing scripts to call aws-k8s-tester (v.0.5.4
which is the release needed with the fix for aws/aws-k8s-tester#70) with
these updated environment variables.

We decrease the number of parallel builds of the echo job from 100 to
3 and the number of completions for that job from 1000 to 30. This
decreases the setup time of the cluster by about 10 minutes.

Finally, I added in a short-circuit to prevent double-deprovisioning of
the cluster if, say, a stacktrace occurred when running the
aws-k8s-tester tool.

Issue aws#686
Issue aws#784
Issue aws#786
mogren pushed a commit that referenced this issue Jan 20, 2020
@jaypipes @mogren
update script to work with 0.5.4 aws-k8s-tester
8291df3 
The names of environment variables accepted by aws-k8s-tester changed
when the managed node group functionality was introduced. This commit
updates the integration testing scripts to call aws-k8s-tester (v.0.5.4
which is the release needed with the fix for aws/aws-k8s-tester#70) with
these updated environment variables.

We decrease the number of parallel builds of the echo job from 100 to
3 and the number of completions for that job from 1000 to 30. This
decreases the setup time of the cluster by about 10 minutes.

Finally, I added in a short-circuit to prevent double-deprovisioning of
the cluster if, say, a stacktrace occurred when running the
aws-k8s-tester tool.

Issue #686
Issue #784
Issue #786
mogren pushed a commit to mogren/amazon-vpc-cni-k8s that referenced this issue Jan 31, 2020
@jaypipes
update script to work with 0.5.4 aws-k8s-tester
cee7bba 
The names of environment variables accepted by aws-k8s-tester changed
when the managed node group functionality was introduced. This commit
updates the integration testing scripts to call aws-k8s-tester (v.0.5.4
which is the release needed with the fix for aws/aws-k8s-tester#70) with
these updated environment variables.

We decrease the number of parallel builds of the echo job from 100 to
3 and the number of completions for that job from 1000 to 30. This
decreases the setup time of the cluster by about 10 minutes.

Finally, I added in a short-circuit to prevent double-deprovisioning of
the cluster if, say, a stacktrace occurred when running the
aws-k8s-tester tool.

Issue aws#686
Issue aws#784
Issue aws#786

(cherry picked from commit 8291df3)
jaypipes added a commit that referenced this issue Jan 31, 2020
@jaypipes
update script to work with 0.5.4 aws-k8s-tester
e65fef8 
The names of environment variables accepted by aws-k8s-tester changed
when the managed node group functionality was introduced. This commit
updates the integration testing scripts to call aws-k8s-tester (v.0.5.4
which is the release needed with the fix for aws/aws-k8s-tester#70) with
these updated environment variables.

We decrease the number of parallel builds of the echo job from 100 to
3 and the number of completions for that job from 1000 to 30. This
decreases the setup time of the cluster by about 10 minutes.

Finally, I added in a short-circuit to prevent double-deprovisioning of
the cluster if, say, a stacktrace occurred when running the
aws-k8s-tester tool.

Issue #686
Issue #784
Issue #786

(cherry picked from commit 8291df3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jaypipes jaypipes

Labels
bug testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jaypipes