Change:
<ins> /* Copyright 2014 Google Inc. All rights reserved. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. */ package master import ( "fmt" "log" "sync" "time" "github.com/GoogleCloudPlatform/kubernetes/pkg/client" "github.com/GoogleCloudPlatform/kubernetes/pkg/labels" "github.com/GoogleCloudPlatform/kubernetes/pkg/registry" "github.com/GoogleCloudPlatform/kubernetes/pkg/util" ) // PodCache contains both a cache of container information, as well as the mechanism for keeping // that cache up to date. type PodCache struct { containerInfo client.ContainerInfo pods          registry.PodRegistry podInfo       map[string]interface{} period        time.Duration podLock       sync.Mutex } func NewPodCache(info client.ContainerInfo, pods registry.PodRegistry, period time.Duration) *PodCache { return &PodCache{ containerInfo: info, pods:          pods, podInfo:       map[string]interface{}{}, period:        period, } } // Implements the ContainerInfo interface // The returned value should be treated as read-only func (p *PodCache) GetContainerInfo(host, id string) (interface{}, error) { p.podLock.Lock() defer p.podLock.Unlock() value, ok := p.podInfo[id] if !ok { return nil, fmt.Errorf("Couldn't find any information for %s", id) } else { return value, nil } } func (p *PodCache) updateContainerInfo(host, id string) error { info, err := p.containerInfo.GetContainerInfo(host, id) if err != nil { return err } p.podLock.Lock() defer p.podLock.Unlock() p.podInfo[id] = info return nil } // Update information about all containers.  Either called by Loop() below, or one-off. func (p *PodCache) UpdateAllContainers() { pods, err := p.pods.ListPods(labels.Everything()) if err != nil { log.Printf("Error synchronizing container: %#v", err) return } for _, pod := range pods { err := p.updateContainerInfo(pod.CurrentState.Host, pod.ID) if err != nil { log.Printf("Error synchronizing container: %#v", err) } } } func (p *PodCache) synchronizeContainers() { ticker := time.Tick(p.period) for _ = range ticker { p.UpdateAllContainers() } } // Loop runs forever, it is expected to be placed in a go routine. func (p *PodCache) Loop() { util.Forever(func() { p.synchronizeContainers() }, 0) } </ins>

Discussion:
Which jobs are failing: cip-postsubmit-push-to-staging (cip-postsubmit-push-to-staging) Since when has it been failing: This is a postsubmit of repository. Testgrid link: Reason for failure: Anything else we need to know: /cc /priority critical-urgent /milestone v1.18
So this is the "create a staging image of the promoter upon a merge to its master branch" job so that I don't have to do it manually myself. As for the failure, I am probably doing something wrong but from the logs it's hard to tell what I'm doing wrong. I don't think this is critical as it is not blocking the official promoter or anything.
I think the error could be that the service account for doesn't have creds to push to the buckets. I'll post another update later.
Thanks for the quick response. So, since this job is not critical, can we removed it from testgrid or is there a good reason to keep it there and just ignore the alerts?
I should be able to fix it this week; if that deadline passes then we can move it to another testgrid dashboard.
/sig release
/reopen Let's observe the job first before closing.
Reopened this issue. <detailsIn response to : /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
Do we have to rerun the job to make sure that it's fixed or wait for the next PR to be merge?
The behavior I have observed is that the job will re-run for each PR merge. I am now seeing that the latest build is failing due to a MemoryError when joining the heaviest Docker layer that contains gcloud: I am going to change the machine settings in another PR; stay tuned.
Looks like the last couple PRs did the trick. It's green now!
Thanks ! /close
Closing this issue. <detailsIn response to : Thanks ! Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details