Change:
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
The test failed because the busybox container was crash-looping, but I'm not sure why.
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
- Any ideas what changed in the past week that would cause the Kubelet usage/working set memory usage to suddenly increase? It may be a non-issue, but it's concerning that this seems to have recently changed. - This is only happening on GCI. Did we change the GCI image being tested recently?
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
Last image version update for testing was 11 days ago () though we are soon going to update it again ().
Since we increased the bound on (), we should also increase the bound on ( is usage - total inactive file). I think this may be the cause of this flake.
I agree that the bounds should match, but the cause of both flakes (why usage & workingset suddenly increased) is still unknown.
Usage workingset so it may not be necessary to bump both ;) I think this may be the caused by the gci mounter.
/cc
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
https://k8s- Failed: [] Summary API when querying /stats/summary should report resource usage through the stats api {E2eNode Suite}
I checked the log from the last failure, didn't see anything related to gci mounter. The test failed on trusty node which mounter should not be used at all.
Yes, the latest failures are just a flake introduced by The bounds need to be adjusted for the misc container. I'll send a PR soon.

Discussion:
var _ = framework.KubeDescribe("Summary API", func() { f := framework.NewDefaultFramework("summary-test") Context("when querying /stats/summary", func() { <ins> AfterEach(func() { if CurrentGinkgoTestDescription().Failed && framework.TestContext.DumpLogsOnFailure { framework.LogFailedContainers(f.ClientSet, f.Namespace.Name, framework.Logf) } }) </ins> It("should report resource usage through the stats api", func() { const pod0 = "stats-busybox-0" const pod1 = "stats-busybox-1"

{ Name:    "busybox-container", Image:   "gcr.io/google_containers/busybox:1.24", <del> Command: []string{"sh", "-c", "ping -c 1 google.com; while true; do echo 'hello world' | tee /test-empty-dir-mnt/file ; sleep 1; done"}, </del> <ins> Command: []string{"sh", "-c", "ping -c 1 google.com; while true; do echo 'hello world' >> /test-empty-dir-mnt/file ; sleep 1; done"}, </ins> Resources: api.ResourceRequirements{ Limits: api.ResourceList{ // Must set memory limit to get MemoryStats.AvailableBytes