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.

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

Revert "allow ignoreMetrics in new manager" #1163

Closed
wants to merge 1 commit into from

Conversation

vishh
Copy link
Contributor

@vishh vishh commented Mar 15, 2016

Build is broken after #1159 was merged. Opening this PR to fix CI.

Build failure logs here.

@vishh
Copy link
Contributor Author

vishh commented Mar 15, 2016

cc @timstclair

@timstclair
Copy link
Contributor

cc @sjenning @ncdc @derekwaynecarr

@ncdc
Copy link
Collaborator

ncdc commented Mar 15, 2016

What CI failed - I'm guessing you have something besides the Jenkins GCE e2e?

@vishh
Copy link
Contributor Author

vishh commented Mar 15, 2016

We run CI on HEAD. I believe the PR was merged before the CI was happy with
the most recent commit.

On Mon, Mar 14, 2016 at 5:47 PM, Andy Goldstein notifications@github.com
wrote:

What CI failed - I'm guessing you have something besides the Jenkins GCE
e2e?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#1163 (comment)

@timstclair
Copy link
Contributor

https://storage.googleapis.com/kubernetes-jenkins/logs/cadvisor-gce-e2e-ci/41/build-log.txt

I'm not sure that this caused the issue, but we're having trouble debugging, so decided to try the rollback.

@timstclair
Copy link
Contributor

Oops, updated to external link.

@k8s-bot
Copy link
Collaborator

k8s-bot commented Mar 15, 2016

Jenkins GCE e2e

Build/test failed for commit 1ae7db7.

@vishh
Copy link
Contributor Author

vishh commented Mar 15, 2016

@k8s-bot test again

@k8s-bot
Copy link
Collaborator

k8s-bot commented Mar 15, 2016

Jenkins GCE e2e

Build/test failed for commit 1ae7db7.

@ncdc
Copy link
Collaborator

ncdc commented Mar 15, 2016

It appears there's an issue with the way that CI is running the integration tests. It's invoking like this:

"godep" ["go" "test" "--timeout" "15m0s" "" "github.com/google/cadvisor/integration/tests/..." "--host" "e2e-cadvisor-container-vm-v20160127" "--port" "8080" "--ssh-options" "-i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no"]

Notice the empty string argument in between 15m0s and github.com/google/cadvisor/integration/tests/... . Because of that empty string, CI is basically just running godep go test --host ....

The reason that CI is failing is because --host is not a valid flag for the new cadvisor_test.go that was added in Seth's PR in the project root.

@vishh
Copy link
Contributor Author

vishh commented Mar 15, 2016

That flag is part of the integration test framework. Why would the PR
affect the test framework?

On Tue, Mar 15, 2016, 6:41 AM Andy Goldstein notifications@github.com
wrote:

It appears there's an issue with the way that CI is running the
integration tests. It's invoking like this:

"godep" ["go" "test" "--timeout" "15m0s" "" "github.com/google/cadvisor/integration/tests/..." "--host" "e2e-cadvisor-container-vm-v20160127" "--port" "8080" "--ssh-options" "-i /home/jenkins/.ssh/google_compute_engine -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o CheckHostIP=no -o StrictHostKeyChecking=no"]

Notice the empty string argument in between 15m0s and
github.com/google/cadvisor/integration/tests/... . Because of that empty
string, CI is basically just running godep go test ... --host ....

The reason that CI is failing is because --host is not a valid flag for
the new cadvisor_test.go that was added in Seth's PR in the project root.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:

#1163 (comment)

@ncdc
Copy link
Collaborator

ncdc commented Mar 15, 2016

@vishh it doesn't affect the test framework, per se. What happened is the PR added a new test at the root of the project directory, where one didn't exist before. And because there is no --host flag at the root (it only exists in the integration test code), things fail. Can you all fix how Jenkins invokes godep go test to get rid of that empty string argument?

@vishh vishh closed this Mar 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants