Giters

kubernetes-retired / multi-tenancy

A working place for multi-tenancy related proposals and prototypes.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[VC] Experimental Scheduler test failures

christopherhein opened this issue · comments

commented

It looks like currently on master the experimental scheduler features failing make test.

# sigs.k8s.io/multi-tenancy/incubator/virtualcluster/experiment/pkg/scheduler/cache [sigs.k8s.io/multi-tenancy/incubator/virtualcluster/experiment/pkg/scheduler/cache.test]
experiment/pkg/scheduler/cache/cache_test.go:189:52: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:190:110: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:192:52: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:193:110: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:293:15: cache.UpdateNamespace undefined (type Cache has no field or method UpdateNamespace)
experiment/pkg/scheduler/cache/cache_test.go:300:52: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:301:110: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:303:52: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:304:110: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:322:52: cache.clusters undefined (type Cache has no field or method clusters)
experiment/pkg/scheduler/cache/cache_test.go:322:52: too many errors
FAIL    sigs.k8s.io/multi-tenancy/incubator/virtualcluster/experiment/pkg/scheduler/cache [build failed]
commented

/kind bug

commented

This is fixed in #1390
/close

commented

@Fei-Guo: Closing this issue.

In response to this:

This is fixed in #1390
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.