This job view page is being replaced by Spyglass soon. Check out the new job view.
PRzouyee: Remove type and replace it with scheduler methods
ResultFAILURE
Tests 1 failed / 754 succeeded
Started2020-01-07 05:47
Elapsed43m16s
Revision36fa9957ffa91cd22810e9df323885c9dc7db29b
Refs 85442
job-versionv1.18.0-alpha.1.382+7e5c72a9260647
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
revisionv1.18.0-alpha.1.382+7e5c72a9260647

Test Failures


Test 21m7s

error during ./hack/ginkgo-e2e.sh --ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\] --minStartupPods=8 --report-dir=/logs/artifacts --disable-log-dump=true: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 754 Passed Tests

Show 4043 Skipped Tests

Error lines from build-log.txt

... skipping 139 lines ...
INFO: 4430 processes: 4354 remote cache hit, 27 processwrapper-sandbox, 49 remote.
INFO: Build completed successfully, 4495 total actions
INFO: Build completed successfully, 4495 total actions
make: Leaving directory '/home/prow/go/src/k8s.io/kubernetes'
2020/01/07 05:52:12 process.go:155: Step 'make -C /home/prow/go/src/k8s.io/kubernetes bazel-release' finished in 4m35.898769177s
2020/01/07 05:52:12 util.go:265: Flushing memory.
2020/01/07 05:52:13 util.go:275: flushMem error (page cache): exit status 1
2020/01/07 05:52:13 process.go:153: Running: /home/prow/go/src/k8s.io/release/push-build.sh --nomock --verbose --noupdatelatest --bucket=kubernetes-release-pull --ci --gcs-suffix=/pull-kubernetes-e2e-gce --allow-dup
push-build.sh: BEGIN main on e8f9f1c8-3110-11ea-89a1-364cd95ae453 Tue Jan  7 05:52:14 UTC 2020

$TEST_TMPDIR defined: output root default is '/bazel-scratch/.cache/bazel' and max_idle_secs default is '15'.
INFO: Invocation ID: 13f518cf-969f-410d-a106-64aca3776455
Loading: 
... skipping 822 lines ...
Trying to find master named 'e2e-fc1dcc3f95-abe28-master'
Looking for address 'e2e-fc1dcc3f95-abe28-master-ip'
Using master: e2e-fc1dcc3f95-abe28-master (external IP: 104.199.121.187; internal IP: (not set))
Waiting up to 300 seconds for cluster initialization.

  This will continually check to see if the API for kubernetes is reachable.
  This may time out if there was some uncaught error during start up.

.............Kubernetes cluster created.
Cluster "k8s-jkns-gce-reboot-1-4_e2e-fc1dcc3f95-abe28" set.
User "k8s-jkns-gce-reboot-1-4_e2e-fc1dcc3f95-abe28" set.
Context "k8s-jkns-gce-reboot-1-4_e2e-fc1dcc3f95-abe28" created.
Switched to context "k8s-jkns-gce-reboot-1-4_e2e-fc1dcc3f95-abe28".
... skipping 20 lines ...
NAME                                     STATUS                     ROLES    AGE   VERSION
e2e-fc1dcc3f95-abe28-master              Ready,SchedulingDisabled   <none>   35s   v1.18.0-alpha.1.382+7e5c72a9260647
e2e-fc1dcc3f95-abe28-minion-group-gb3c   Ready                      <none>   32s   v1.18.0-alpha.1.382+7e5c72a9260647
e2e-fc1dcc3f95-abe28-minion-group-j08n   Ready                      <none>   32s   v1.18.0-alpha.1.382+7e5c72a9260647
e2e-fc1dcc3f95-abe28-minion-group-mgp1   Ready                      <none>   31s   v1.18.0-alpha.1.382+7e5c72a9260647
Validate output:
NAME                 STATUS    MESSAGE             ERROR
scheduler            Healthy   ok                  
controller-manager   Healthy   ok                  
etcd-1               Healthy   {"health":"true"}   
etcd-0               Healthy   {"health":"true"}   
Cluster validation succeeded
Done, listing cluster services:
... skipping 87 lines ...

Jan  7 06:01:04.248: INFO: cluster-master-image: cos-77-12371-89-0
Jan  7 06:01:04.248: INFO: cluster-node-image: cos-77-12371-89-0
Jan  7 06:01:04.248: INFO: >>> kubeConfig: /workspace/.kube/config
Jan  7 06:01:04.251: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
Jan  7 06:01:04.405: INFO: Waiting up to 10m0s for all pods (need at least 8) in namespace 'kube-system' to be running and ready
Jan  7 06:01:04.603: INFO: The status of Pod kube-addon-manager-e2e-fc1dcc3f95-abe28-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan  7 06:01:04.603: INFO: 27 / 28 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Jan  7 06:01:04.603: INFO: expected 8 pod replicas in namespace 'kube-system', 8 are Running and Ready.
Jan  7 06:01:04.603: INFO: POD                                             NODE                         PHASE    GRACE  CONDITIONS
Jan  7 06:01:04.603: INFO: kube-addon-manager-e2e-fc1dcc3f95-abe28-master  e2e-fc1dcc3f95-abe28-master  Pending         []
Jan  7 06:01:04.603: INFO: 
Jan  7 06:01:06.739: INFO: The status of Pod fluentd-gcp-v3.2.0-t9l9t is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan  7 06:01:06.739: INFO: The status of Pod kube-addon-manager-e2e-fc1dcc3f95-abe28-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan  7 06:01:06.739: INFO: 26 / 28 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Jan  7 06:01:06.739: INFO: expected 8 pod replicas in namespace 'kube-system', 8 are Running and Ready.
Jan  7 06:01:06.739: INFO: POD                                             NODE                                    PHASE    GRACE  CONDITIONS
Jan  7 06:01:06.739: INFO: fluentd-gcp-v3.2.0-t9l9t                        e2e-fc1dcc3f95-abe28-minion-group-mgp1  Running  60s    [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-01-07 05:59:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-01-07 06:01:06 +0000 UTC ContainersNotReady containers with unready status: [fluentd-gcp prometheus-to-sd-exporter]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-01-07 06:01:06 +0000 UTC ContainersNotReady containers with unready status: [fluentd-gcp prometheus-to-sd-exporter]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-01-07 05:59:54 +0000 UTC  }]
Jan  7 06:01:06.739: INFO: kube-addon-manager-e2e-fc1dcc3f95-abe28-master  e2e-fc1dcc3f95-abe28-master             Pending         []
Jan  7 06:01:06.739: INFO: 
Jan  7 06:01:08.730: INFO: The status of Pod fluentd-gcp-v3.2.0-gkg78 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan  7 06:01:08.730: INFO: The status of Pod kube-addon-manager-e2e-fc1dcc3f95-abe28-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Jan  7 06:01:08.730: INFO: 26 / 28 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Jan  7 06:01:08.730: INFO: expected 8 pod replicas in namespace 'kube-system', 8 are Running and Ready.
Jan  7 06:01:08.730: INFO: POD                                             NODE                                    PHASE    GRACE  CONDITIONS
Jan  7 06:01:08.730: INFO: fluentd-gcp-v3.2.0-gkg78                        e2e-fc1dcc3f95-abe28-minion-group-mgp1  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2020-01-07 06:01:07 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2020-01-07 06:01:07 +0000 UTC ContainersNotReady containers with unready status: [fluentd-gcp prometheus-to-sd-exporter]} {ContainersReady False 0001-01-01 00:00:00 +0000 UTC 2020-01-07 06:01:07 +0000 UTC ContainersNotReady containers with unready status: [fluentd-gcp prometheus-to-sd-exporter]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2020-01-07 06:01:07 +0000 UTC  }]
Jan  7 06:01:08.730: INFO: kube-addon-manager-e2e-fc1dcc3f95-abe28-master  e2e-fc1dcc3f95-abe28-master             Pending         []
Jan  7 06:01:08.730: INFO: 
... skipping 1141 lines ...
  test/e2e/framework/framework.go:175
Jan  7 06:01:14.726: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "kubelet-test-9914" for this suite.

•
------------------------------
{"msg":"PASSED [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should be possible to delete [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":11,"failed":0}

S
------------------------------
[BeforeEach] [sig-storage] Pod Disks
  test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 2 lines ...
Jan  7 06:01:13.913: INFO: Found PodSecurityPolicies; assuming PodSecurityPolicy is enabled.
Jan  7 06:01:14.066: INFO: Found ClusterRoles; assuming RBAC is enabled.
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in pod-disks-7799
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [sig-storage] Pod Disks
  test/e2e/storage/pd.go:73
[It] should be able to delete a non-existent PD without error
  test/e2e/storage/pd.go:446
STEP: delete a PD
W0107 06:01:15.339723   13029 gce_disks.go:972] GCE persistent disk "non-exist" not found in managed zones (us-west1-b)
Jan  7 06:01:15.339: INFO: Successfully deleted PD "non-exist".
[AfterEach] [sig-storage] Pod Disks
  test/e2e/framework/framework.go:175
Jan  7 06:01:15.339: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "pod-disks-7799" for this suite.

•
------------------------------
{"msg":"PASSED [sig-storage] Pod Disks should be able to delete a non-existent PD without error","total":-1,"completed":1,"skipped":8,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
  test/e2e/storage/testsuites/base.go:94
[BeforeEach] [Testpattern: Pre-provisioned PV (block volmode)] volumeMode
... skipping 202 lines ...
• [SLOW TEST:8.542 seconds]
[sig-storage] Secrets
test/e2e/common/secrets_volume.go:34
  should be able to mount in a volume regardless of a different secret existing with same name in different namespace [NodeConformance] [Conformance]
  test/e2e/framework/framework.go:685
------------------------------
{"msg":"PASSED [sig-storage] Secrets should be able to mount in a volume regardless of a different secret existing with same name in different namespace [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":3,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] subPath
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:19.609: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 371 lines ...
  test/e2e/common/runtime.go:38
    on terminated container
    test/e2e/common/runtime.go:131
      should report termination message [LinuxOnly] from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]
      test/e2e/framework/framework.go:685
------------------------------
{"msg":"PASSED [k8s.io] Container Runtime blackbox test on terminated container should report termination message [LinuxOnly] from file when pod succeeds and TerminationMessagePolicy FallbackToLogsOnError is set [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":4,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/storage/testsuites/base.go:94
[BeforeEach] [Testpattern: Dynamic PV (delayed binding)] topology
  test/e2e/storage/testsuites/topology.go:86
Jan  7 06:01:23.963: INFO: Driver "csi-hostpath" does not support topology - skipping
[AfterEach] [Testpattern: Dynamic PV (delayed binding)] topology
... skipping 5 lines ...
[sig-storage] CSI Volumes
test/e2e/storage/utils/framework.go:23
  [Driver: csi-hostpath]
  test/e2e/storage/csi_volumes.go:55
    [Testpattern: Dynamic PV (delayed binding)] topology
    test/e2e/storage/testsuites/base.go:93
      should fail to schedule a pod which has topologies that conflict with AllowedTopologies [BeforeEach]
      test/e2e/storage/testsuites/topology.go:190

      Driver "csi-hostpath" does not support topology - skipping

      test/e2e/storage/testsuites/topology.go:95
------------------------------
... skipping 49 lines ...
test/e2e/framework/framework.go:680
  when scheduling a busybox command that always fails in a pod
  test/e2e/common/kubelet.go:78
    should have an terminated reason [NodeConformance] [Conformance]
    test/e2e/framework/framework.go:685
------------------------------
{"msg":"PASSED [k8s.io] Kubelet when scheduling a busybox command that always fails in a pod should have an terminated reason [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":1,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:24.302: INFO: Only supported for providers [openstack] (not gce)
[AfterEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/framework/framework.go:175
Jan  7 06:01:24.303: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 17 lines ...
  test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jan  7 06:01:23.970: INFO: >>> kubeConfig: /workspace/.kube/config
STEP: Building a namespace api object, basename configmap
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in configmap-7269
STEP: Waiting for a default service account to be provisioned in namespace
[It] should fail to create ConfigMap with empty key [Conformance]
  test/e2e/framework/framework.go:685
STEP: Creating configMap that has name configmap-test-emptyKey-9a35c758-5127-4fd3-8c5f-362531c050b7
[AfterEach] [sig-node] ConfigMap
  test/e2e/framework/framework.go:175
Jan  7 06:01:24.358: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "configmap-7269" for this suite.

•
------------------------------
{"msg":"PASSED [sig-node] ConfigMap should fail to create ConfigMap with empty key [Conformance]","total":-1,"completed":2,"skipped":8,"failed":0}
[BeforeEach] [sig-api-machinery] Servers with support for Table transformation
  test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
Jan  7 06:01:24.434: INFO: >>> kubeConfig: /workspace/.kube/config
STEP: Building a namespace api object, basename tables
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in tables-8425
... skipping 14 lines ...
  test/e2e/framework/framework.go:175
Jan  7 06:01:25.031: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "tables-8425" for this suite.

•
------------------------------
{"msg":"PASSED [sig-api-machinery] Servers with support for Table transformation should return generic metadata details across all namespaces for nodes","total":-1,"completed":3,"skipped":8,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:25.120: INFO: Driver local doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/framework/framework.go:175
Jan  7 06:01:25.120: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 98 lines ...
• [SLOW TEST:14.575 seconds]
[sig-storage] HostPath
test/e2e/common/host_path.go:34
  should support r/w [NodeConformance]
  test/e2e/common/host_path.go:65
------------------------------
{"msg":"PASSED [sig-storage] HostPath should support r/w [NodeConformance]","total":-1,"completed":1,"skipped":2,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] subPath
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:25.646: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 54 lines ...
• [SLOW TEST:18.628 seconds]
[k8s.io] [sig-node] Security Context
test/e2e/framework/framework.go:680
  should support pod.Spec.SecurityContext.RunAsUser And pod.Spec.SecurityContext.RunAsGroup [LinuxOnly]
  test/e2e/node/security_context.go:88
------------------------------
{"msg":"PASSED [k8s.io] [sig-node] Security Context should support pod.Spec.SecurityContext.RunAsUser And pod.Spec.SecurityContext.RunAsGroup [LinuxOnly]","total":-1,"completed":1,"skipped":5,"failed":0}

S
------------------------------
[BeforeEach] [sig-storage] ConfigMap
  test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 33 lines ...
• [SLOW TEST:20.337 seconds]
[sig-storage] ConfigMap
test/e2e/common/configmap_volume.go:33
  should be consumable from pods in volume as non-root with FSGroup [LinuxOnly] [NodeFeature:FSGroup]
  test/e2e/common/configmap_volume.go:72
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume as non-root with FSGroup [LinuxOnly] [NodeFeature:FSGroup]","total":-1,"completed":1,"skipped":0,"failed":0}

S
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:31.409: INFO: Driver hostPath doesn't support DynamicPV -- skipping
... skipping 216 lines ...
• [SLOW TEST:19.834 seconds]
[sig-storage] ConfigMap
test/e2e/common/configmap_volume.go:33
  should be consumable from pods in volume with mappings as non-root with FSGroup [LinuxOnly] [NodeFeature:FSGroup]
  test/e2e/common/configmap_volume.go:107
------------------------------
{"msg":"PASSED [sig-storage] ConfigMap should be consumable from pods in volume with mappings as non-root with FSGroup [LinuxOnly] [NodeFeature:FSGroup]","total":-1,"completed":1,"skipped":7,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volumes
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:31.775: INFO: Driver vsphere doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] volumes
  test/e2e/framework/framework.go:175
Jan  7 06:01:31.775: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 67 lines ...
• [SLOW TEST:6.889 seconds]
[sig-node] Downward API
test/e2e/common/downward_api.go:33
  should provide host IP and pod IP as an env var if pod uses host network [LinuxOnly]
  test/e2e/common/downward_api.go:108
------------------------------
{"msg":"PASSED [sig-node] Downward API should provide host IP and pod IP as an env var if pod uses host network [LinuxOnly]","total":-1,"completed":4,"skipped":15,"failed":0}

SSSSSS
------------------------------
[BeforeEach] [k8s.io] Security Context
  test/e2e/framework/framework.go:174
STEP: Creating a kubernetes client
... skipping 23 lines ...
test/e2e/framework/framework.go:680
  When creating a pod with privileged
  test/e2e/common/security_context.go:226
    should run the container as unprivileged when false [LinuxOnly] [NodeConformance] [Conformance]
    test/e2e/framework/framework.go:685
------------------------------
{"msg":"PASSED [k8s.io] Security Context When creating a pod with privileged should run the container as unprivileged when false [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":2,"skipped":8,"failed":0}

SS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
  test/e2e/storage/testsuites/base.go:94
[BeforeEach] [Testpattern: Dynamic PV (default fs)] volumes
... skipping 99 lines ...
• [SLOW TEST:21.549 seconds]
[sig-storage] EmptyDir volumes
test/e2e/common/empty_dir.go:40
  pod should support shared volumes between containers [Conformance]
  test/e2e/framework/framework.go:685
------------------------------
{"msg":"PASSED [sig-storage] EmptyDir volumes pod should support shared volumes between containers [Conformance]","total":-1,"completed":1,"skipped":5,"failed":0}
[BeforeEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:32.622: INFO: Driver local doesn't support ntfs -- skipping
[AfterEach] [Testpattern: Pre-provisioned PV (ntfs)][sig-windows] volumes
  test/e2e/framework/framework.go:175
Jan  7 06:01:32.623: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 37 lines ...
• [SLOW TEST:23.751 seconds]
[sig-storage] Projected downwardAPI
test/e2e/common/projected_downwardapi.go:34
  should update labels on modification [NodeConformance] [Conformance]
  test/e2e/framework/framework.go:685
------------------------------
{"msg":"PASSED [sig-storage] Projected downwardAPI should update labels on modification [NodeConformance] [Conformance]","total":-1,"completed":1,"skipped":4,"failed":0}
[BeforeEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:34.834: INFO: Driver supports dynamic provisioning, skipping InlineVolume pattern
[AfterEach] [Testpattern: Inline-volume (default fs)] subPath
  test/e2e/framework/framework.go:175
Jan  7 06:01:34.834: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 60 lines ...
• [SLOW TEST:10.794 seconds]
[sig-api-machinery] Garbage collector
test/e2e/apimachinery/framework.go:23
  should delete pods created by rc when not orphaning [Conformance]
  test/e2e/framework/framework.go:685
------------------------------
{"msg":"PASSED [sig-api-machinery] Garbage collector should delete pods created by rc when not orphaning [Conformance]","total":-1,"completed":2,"skipped":6,"failed":0}
[BeforeEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:40.509: INFO: Driver hostPathSymlink doesn't support DynamicPV -- skipping
[AfterEach] [Testpattern: Dynamic PV (default fs)(allowExpansion)] volume-expand
  test/e2e/framework/framework.go:175
Jan  7 06:01:40.510: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
... skipping 160 lines ...
test/e2e/framework/framework.go:680
  When creating a container with runAsUser
  test/e2e/common/security_context.go:44
    should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]
    test/e2e/framework/framework.go:685
------------------------------
{"msg":"PASSED [k8s.io] Security Context When creating a container with runAsUser should run the container with uid 65534 [LinuxOnly] [NodeConformance] [Conformance]","total":-1,"completed":3,"skipped":10,"failed":0}

SSS
------------------------------
[BeforeEach] [Testpattern: Dynamic PV (ntfs)][sig-windows] provisioning
  test/e2e/storage/testsuites/base.go:94
Jan  7 06:01:41.059: INFO: Driver local doesn't support DynamicPV -- skipping
... skipping 48 lines ...
Jan  7 06:01:32.625: INFO: >>> kubeConfig: /workspace/.kube/config
STEP: Building a namespace api object, basename init-container
STEP: Binding the e2e-test-privileged-psp PodSecurityPolicy to the default service account in init-container-4150
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] InitContainer [NodeConformance]
  test/e2e/common/init_container.go:153
[It] should not start app containers and fail the pod if init containers fail on a RestartNever pod [Conformance]
  test/e2e/f