Error from server (NotFound): namespaces "devfile-proxy" not found Using Devfile proxy: go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=8c510d9a8" ./cmd/odo/ go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=16 --junit-report="test-integration.xml" --label-filter="!unauth && !nocluster && !podman" tests/integration Running Suite: Integration Suite - /go/odo_1/tests/integration ============================================================== Random Seed: 1683023359 - will randomize all specs Will run 483 of 860 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSS•S••S•• ------------------------------ • [21.652 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "none") /go/odo_1/tests/integration/interactive_add_binding_test.go:378 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3549610349 << Captured StdOut/StdErr Output ------------------------------ S••SSS•SS ------------------------------ • [FAILED] [18.442 seconds] odo devfile deploy command tests deploying devfile with exec when using devfile where the exec command is bound to fail [It] should print the last 100 lines of the log to the output /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:616 Timeline >> Created dir: /tmp/2798433139 Created dir: /tmp/3293352902 Setting KUBECONFIG=/tmp/3293352902/config Creating a new project: cmd-devfile-deploy-test616vzz Running kubectl with args [kubectl create namespace cmd-devfile-deploy-test616vzz] and odo env: [] [kubectl] namespace/cmd-devfile-deploy-test616vzz created Running kubectl with args [kubectl config set-context --current --namespace cmd-devfile-deploy-test616vzz] and odo env: [] [kubectl] Context "odo-test-kubernetes-cluster/c8giauof0f337j4pe5u0/admin" modified. Running kubectl with args [kubectl get namespaces] and odo env: [] [kubectl] NAME STATUS AGE [kubectl] backstage Active 10d [kubectl] ci-devfile-registry Active 31d [kubectl] cmd-add-binding-test292joy Terminating 24s [kubectl] cmd-delete-test329mdx Active 4s [kubectl] cmd-delete-test438vsh Active 5s [kubectl] cmd-delete-test513epr Terminating 11s [kubectl] cmd-delete-test625kve Active 23s [kubectl] cmd-delete-test670wdn Active 24s [kubectl] cmd-describe-component-test294ubc Active 3s [kubectl] cmd-describe-component-test294ymh Active 25s [kubectl] cmd-dev-test102nxi Active 24s [kubectl] cmd-dev-test1183rhz Active 24s [kubectl] cmd-dev-test1275plg Active 24s [kubectl] cmd-dev-test1508iks Active 23s [kubectl] cmd-dev-test1777bux Active 23s [kubectl] cmd-dev-test1789dpm Active 11s [kubectl] cmd-dev-test3325dcu Active 24s [kubectl] cmd-dev-test3475uil Active 24s [kubectl] cmd-dev-test3752scl Terminating 23s [kubectl] cmd-dev-test3864ffw Terminating 4s [kubectl] cmd-devfile-build-images-test314xgz Terminating 9s [kubectl] cmd-devfile-deploy-test616vzz Active 1s [kubectl] default Active 424d [kubectl] ibm-cert-store Active 424d [kubectl] ibm-operators Active 424d [kubectl] ibm-system Active 424d [kubectl] interactive-add-binding-test378wuy Terminating 24s [kubectl] interactive-dev-test40vjq Active 24s [kubectl] ipzh-project Active 33d [kubectl] kube-node-lease Active 424d [kubectl] kube-public Active 424d [kubectl] kube-system Active 424d [kubectl] olm Active 313d [kubectl] operators Active 313d [kubectl] osag-namespace Active 174d [kubectl] phmartin Active 5d22h Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-devfile-deploy-test616vzz] and odo env: [] [kubectl] configmap/config-map-for-cleanup created Current working dir: /go/odo_1/tests/integration Running odo with args [odo preference remove registry DefaultDevfileRegistry -f] and odo env: [] [odo] I0502 10:30:45.805215 13400 implem.go:110] The path for preference file is /tmp/3293352902/preference.yaml [odo] Successfully removed registry Running odo with args [odo preference add registry DefaultDevfileRegistry https://devfile-registry-ci-devfile-registry.odo-test-kubernetes-clust-49529fc6e6a4a9fe7ebba9a3db5b55c4-0000.eu-de.containers.appdomain.cloud/] and odo env: [] [odo] I0502 10:30:46.039530 13412 implem.go:110] The path for preference file is /tmp/3293352902/preference.yaml [odo] New registry successfully added Setting current dir to: /tmp/2798433139 Replacing "commandLine: echo Hello world" with "commandLine: for i in {1..100}; do echo counter $i counter; done; run-non-existent-binary" in /tmp/2798433139/devfile.yaml Running odo with args [odo deploy] and odo env: [] [odo] I0502 10:30:46.251561 13421 version.go:28] executing [podman version --format json] [odo] I0502 10:30:46.251967 13421 implem.go:110] The path for preference file is /tmp/3293352902/preference.yaml [odo] I0502 10:30:46.258937 13421 context.go:159] absolute devfile path: '/tmp/2798433139/devfile.yaml' [odo] I0502 10:30:46.258956 13421 context.go:110] absolute devfile path: '/tmp/2798433139/devfile.yaml' [odo] I0502 10:30:46.259731 13421 content.go:48] converted devfile YAML to JSON [odo] I0502 10:30:46.259833 13421 apiVersion.go:60] devfile schemaVersion: '2.2.0' [odo] I0502 10:30:46.259858 13421 helper.go:56] devfile apiVersion '2.2.0' is supported [odo] I0502 10:30:46.263101 13421 schema.go:61] validated devfile schema [odo] I0502 10:30:46.264993 13421 validate.go:45] Successfully validated devfile sections [odo] I0502 10:30:46.265008 13421 validate.go:45] Successfully validated devfile sections [odo] I0502 10:30:46.265055 13421 component.go:87] name of component is "sggkea", and sanitized name is "sggkea" [odo] I0502 10:30:46.265076 13421 kclient.go:224] Checking if "projects" resource is supported [odo] I0502 10:30:46.289163 13421 oc_server.go:26] Trying to connect to server c110.eu-de.containers.cloud.ibm.com:31454 [odo] I0502 10:30:46.292930 13421 oc_server.go:33] Server https://c110.eu-de.containers.cloud.ibm.com:31454 is up [odo] I0502 10:30:46.300837 13421 oc_server.go:66] Unable to get OpenShift Version: the server could not find the requested resource [odo] __ [odo] / \__ Running the application in Deploy mode using sggkea Devfile [odo] \__/ \ Namespace: cmd-devfile-deploy-test616vzz [odo] / \__/ odo version: v3.9.0 [odo] \__/ [odo] [odo] ↪ Executing command: [odo] • Executing command in container (command: deploy-exec) ... [odo] I0502 10:30:46.426244 13421 jobs.go:44] Waiting for Job sggkea-app-deploy-exec to complete successfully [odo] I0502 10:31:02.101896 13421 jobs.go:67] Failed to execute the job, reason: &JobCondition{Type:Failed,Status:True,LastProbeTime:2023-05-02 10:31:02 +0000 UTC,LastTransitionTime:2023-05-02 10:31:02 +0000 UTC,Reason:BackoffLimitExceeded,Message:Job has reached the specified backoff limit,} [odo] ✗ Executing command in container (command: deploy-exec) [16s] [odo] Execution output: [odo] counter 1 counter [odo] counter 2 counter [odo] counter 3 counter [odo] counter 4 counter [odo] counter 5 counter [odo] counter 6 counter [odo] counter 7 counter [odo] counter 8 counter [odo] counter 9 counter [odo] counter 10 counter [odo] counter 11 counter [odo] counter 12 counter [odo] counter 13 counter [odo] counter 14 counter [odo] counter 15 counter [odo] counter 16 counter [odo] counter 17 counter [odo] counter 18 counter [odo] counter 19 counter [odo] counter 20 counter [odo] counter 21 counter [odo] counter 22 counter [odo] counter 23 counter [odo] counter 24 counter [odo] counter 25 counter [odo] counter 26 counter [odo] counter 27 counter [odo] counter 28 counter [odo] counter 29 counter [odo] counter 30 counter [odo] counter 31 counter [odo] counter 32 counter [odo] counter 33 counter [odo] counter 34 counter [odo] counter 35 counter [odo] counter 36 counter [odo] counter 37 counter [odo] counter 38 counter [odo] counter 39 counter [odo] counter 40 counter [odo] counter 41 counter [odo] counter 42 counter [odo] counter 43 counter [odo] counter 44 counter [odo] counter 45 counter [odo] counter 46 counter [odo] counter 47 counter [odo] counter 48 counter [odo] counter 49 counter [odo] counter 50 counter [odo] counter 51 counter [odo] counter 52 counter [odo] counter 53 counter [odo] counter 54 counter [odo] counter 55 counter [odo] counter 56 counter [odo] counter 57 counter [odo] counter 58 counter [odo] counter 59 counter [odo] counter 60 counter [odo] counter 61 counter [odo] counter 62 counter [odo] counter 63 counter [odo] counter 64 counter [odo] counter 65 counter [odo] counter 66 counter [odo] counter 67 counter [odo] counter 68 counter [odo] counter 69 counter [odo] counter 70 counter [odo] counter 71 counter [odo] counter 72 counter [odo] counter 73 counter [odo] counter 74 counter [odo] counter 75 counter [odo] counter 76 counter [odo] counter 77 counter [odo] counter 78 counter [odo] counter 79 counter [odo] counter 80 counter [odo] counter 81 counter [odo] counter 82 counter [odo] counter 83 counter [odo] counter 84 counter [odo] counter 85 counter [odo] counter 86 counter [odo] counter 87 counter [odo] counter 88 counter [odo] counter 89 counter [odo] counter 90 counter [odo] counter 91 counter [odo] counter 92 counter [odo] counter 93 counter [odo] counter 94 counter [odo] counter 95 counter [odo] counter 96 counter [odo] counter 97 counter [odo] counter 98 counter [odo] counter 99 counter [odo] counter 100 counter [odo] ✗ failed to execute (command: deploy-exec) [FAILED] in [It] - /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:620 @ 05/02/23 10:31:02.257 Deleting project: cmd-devfile-deploy-test616vzz Running kubectl with args [kubectl delete namespaces cmd-devfile-deploy-test616vzz --wait=false] and odo env: [] [kubectl] namespace "cmd-devfile-deploy-test616vzz" deleted Setting current dir to: /go/odo_1/tests/integration Deleting dir: /tmp/2798433139 Deleting dir: /tmp/3293352902 << Timeline [FAILED] Expected : I0502 10:30:46.251561 13421 version.go:28] executing [podman version --format json] I0502 10:30:46.251967 13421 implem.go:110] The path for preference file is /tmp/3293352902/preference.yaml I0502 10:30:46.258937 13421 context.go:159] absolute devfile path: '/tmp/2798433139/devfile.yaml' I0502 10:30:46.258956 13421 context.go:110] absolute devfile path: '/tmp/2798433139/devfile.yaml' I0502 10:30:46.259731 13421 content.go:48] converted devfile YAML to JSON I0502 10:30:46.259833 13421 apiVersion.go:60] devfile schemaVersion: '2.2.0' I0502 10:30:46.259858 13421 helper.go:56] devfile apiVersion '2.2.0' is supported I0502 10:30:46.263101 13421 schema.go:61] validated devfile schema I0502 10:30:46.264993 13421 validate.go:45] Successfully validated devfile sections I0502 10:30:46.265008 13421 validate.go:45] Successfully validated devfile sections I0502 10:30:46.265055 13421 component.go:87] name of component is "sggkea", and sanitized name is "sggkea" I0502 10:30:46.265076 13421 kclient.go:224] Checking if "projects" resource is supported I0502 10:30:46.289163 13421 oc_server.go:26] Trying to connect to server c110.eu-de.containers.cloud.ibm.com:31454 I0502 10:30:46.292930 13421 oc_server.go:33] Server https://c110.eu-de.containers.cloud.ibm.com:31454 is up I0502 10:30:46.300837 13421 oc_server.go:66] Unable to get OpenShift Version: the server could not find the requested resource I0502 10:30:46.426244 13421 jobs.go:44] Waiting for Job sggkea-app-deploy-exec to complete successfully I0502 10:31:02.101896 13421 jobs.go:67] Failed to execute the job, reason: &JobCondition{Type:Failed,Status:True,LastProbeTime:2023-05-02 10:31:02 +0000 UTC,LastTransitionTime:2023-05-02 10:31:02 +0000 UTC,Reason:BackoffLimitExceeded,Message:Job has reached the specified backoff limit,} counter 1 counter counter 2 counter counter 3 counter counter 4 counter counter 5 counter counter 6 counter counter 7 counter counter 8 counter counter 9 counter counter 10 counter counter 11 counter counter 12 counter counter 13 counter counter 14 counter counter 15 counter counter 16 counter counter 17 counter counter 18 counter counter 19 counter counter 20 counter counter 21 counter counter 22 counter counter 23 counter counter 24 counter counter 25 counter counter 26 counter counter 27 counter counter 28 counter counter 29 counter counter 30 counter counter 31 counter counter 32 counter counter 33 counter counter 34 counter counter 35 counter counter 36 counter counter 37 counter counter 38 counter counter 39 counter counter 40 counter counter 41 counter counter 42 counter counter 43 counter counter 44 counter counter 45 counter counter 46 counter counter 47 counter counter 48 counter counter 49 counter counter 50 counter counter 51 counter counter 52 counter counter 53 counter counter 54 counter counter 55 counter counter 56 counter counter 57 counter counter 58 counter counter 59 counter counter 60 counter counter 61 counter counter 62 counter counter 63 counter counter 64 counter counter 65 counter counter 66 counter counter 67 counter counter 68 counter counter 69 counter counter 70 counter counter 71 counter counter 72 counter counter 73 counter counter 74 counter counter 75 counter counter 76 counter counter 77 counter counter 78 counter counter 79 counter counter 80 counter counter 81 counter counter 82 counter counter 83 counter counter 84 counter counter 85 counter counter 86 counter counter 87 counter counter 88 counter counter 89 counter counter 90 counter counter 91 counter counter 92 counter ... Gomega truncated this representation as it exceeds 'format.MaxLength'. Consider having the object provide a custom 'GomegaStringer' representation or adjust the parameters in Gomega's 'format' package. Learn more here: https://onsi.github.io/gomega/#adjusting-output not to contain substring : counter 1 counter In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:620 @ 05/02/23 10:31:02.257 ------------------------------ SSSSS•S••S ------------------------------ • [63.730 seconds] odo dev command tests when a component with multiple endpoints is run should create state files containing information, including forwarded ports /go/odo_1/tests/integration/cmd_dev_test.go:3325 Captured StdOut/StdErr Output >> PID: 12535 << Captured StdOut/StdErr Output ------------------------------ ••SSSS•SSS•• ------------------------------ • [8.492 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("lowercase" as naming strategy) /go/odo_1/tests/integration/interactive_add_binding_test.go:131 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/946316 << Captured StdOut/StdErr Output ------------------------------ S•S•S• ------------------------------ • [95.746 seconds] odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag /go/odo_1/tests/integration/interactive_dev_test.go:40 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/1432255150 << Captured StdOut/StdErr Output ------------------------------ •••••SS•••S•••S•SS•••SS•••S•SSS•S•S••S••SSSSSS••S•••S•SSSS••••S•••S ------------------------------ • [9.258 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (Bind as Environment Variables) /go/odo_1/tests/integration/interactive_add_binding_test.go:73 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3849776992 << Captured StdOut/StdErr Output ------------------------------ ••••S•••SS•S•••••••S•• ------------------------------ • [4.130 seconds] odo init interactive command tests when DevfileRegistriesList CRD is installed on cluster when CR for devfileregistrieslists is installed in namespace should download correct devfile from the first in-cluster registry /go/odo_1/tests/integration/interactive_init_test.go:635 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo init' from /tmp/4017540974 << Captured StdOut/StdErr Output ------------------------------ ••S•SS•SS•••S•• ------------------------------ • [17.195 seconds] odo add binding interactive command tests when running a deployment when binding to a service in a different namespace should successfully add binding without devfile /go/odo_1/tests/integration/interactive_add_binding_test.go:591 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/4221245103 << Captured StdOut/StdErr Output ------------------------------ S•••SS•SS•••S••SS•••SS•SS•• ------------------------------ • [18.141 seconds] odo dev interactive command tests when a component is bootstrapped should sync files when p is pressed /go/odo_1/tests/integration/interactive_dev_test.go:206 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/2788586901 << Captured StdOut/StdErr Output ------------------------------ •S••••••S•S•••S••S•SSS•S•S••SSSS•••SS ------------------------------ • [78.221 seconds] odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile /go/odo_1/tests/integration/interactive_dev_test.go:76 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/3859140886 << Captured StdOut/StdErr Output ------------------------------ SSSSS•• ------------------------------ • [10.905 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("none" as naming strategy) /go/odo_1/tests/integration/interactive_add_binding_test.go:131 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1207490757 << Captured StdOut/StdErr Output ------------------------------ •SS•SSS•SS••SSS•S•S•S•S ------------------------------ • [8.898 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "uppercase") /go/odo_1/tests/integration/interactive_add_binding_test.go:378 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/403859684 << Captured StdOut/StdErr Output ------------------------------ SS••S•••S•S•SS••S•••SS••••S••••S••SS•S••••S•SSS ------------------------------ • [9.263 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "any string") /go/odo_1/tests/integration/interactive_add_binding_test.go:463 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/548114332 << Captured StdOut/StdErr Output ------------------------------ ••SSSS•• ------------------------------ • [9.618 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "") /go/odo_1/tests/integration/interactive_add_binding_test.go:463 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3363554824 << Captured StdOut/StdErr Output ------------------------------ S•S•••SSSSS••• ------------------------------ • [10.913 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (custom naming strategy: "{ .name | upper }") /go/odo_1/tests/integration/interactive_add_binding_test.go:463 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3696469695 << Captured StdOut/StdErr Output ------------------------------ S•S•S•SS•S ------------------------------ • [7.821 seconds] odo dev interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode /go/odo_1/tests/integration/interactive_dev_test.go:164 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/2573527748 << Captured StdOut/StdErr Output ------------------------------ •SS••S•SS•SSS•SSSSS•S•SS•••••S ------------------------------ • [16.613 seconds] odo add binding interactive command tests when the component is bootstrapped when binding to a service in a different namespace should error out if service is not found in the namespace selected /go/odo_1/tests/integration/interactive_add_binding_test.go:242 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2982987913 << Captured StdOut/StdErr Output ------------------------------ •••S•••SSSSSS••••SS•S•SS•••S•SSSSSS••SS•••SSS••S•• ------------------------------ • [3.967 seconds] odo deploy interactive command tests directory is not empty when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode /go/odo_1/tests/integration/interactive_deploy_test.go:159 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/1736578709 << Captured StdOut/StdErr Output ------------------------------ •••••SS••S• ------------------------------ • [9.426 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (naming strategy: "lowercase") /go/odo_1/tests/integration/interactive_add_binding_test.go:378 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3673241608 << Captured StdOut/StdErr Output ------------------------------ SSS•SSSSS••••SS•S•••SS••••SS•••••S•••••SSSSSSS•••S•S•SSS•S•SS•SS••SSSS•S••S•SSS ------------------------------ • [19.833 seconds] odo add binding interactive command tests when the component is bootstrapped when binding to a service in a different namespace should successfully add binding to the devfile /go/odo_1/tests/integration/interactive_add_binding_test.go:257 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3895729203 << Captured StdOut/StdErr Output ------------------------------ ••••••••••S••••SS•S••S••••SS••••S•S••S•••••SSSSS••••SSS••SSSS••S••••SSSSS•••SS•SSSS•S•••S•••S•SS•••S•••••S•S•SS••S•• ------------------------------ • [2.981 seconds] odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile /go/odo_1/tests/integration/interactive_deploy_test.go:75 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/1528831825 << Captured StdOut/StdErr Output ------------------------------ •S•••S•S•••SSSS••S•S••••S•••SS••S• ------------------------------ • [10.362 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "{ .name | upper }") /go/odo_1/tests/integration/interactive_add_binding_test.go:180 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1847847855 << Captured StdOut/StdErr Output ------------------------------ S• ------------------------------ • [18.412 seconds] odo add binding interactive command tests when running a deployment when binding to a service in a different namespace should error out if service is not found in the namespace selected /go/odo_1/tests/integration/interactive_add_binding_test.go:577 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1158255434 << Captured StdOut/StdErr Output ------------------------------ S••••••S••S ------------------------------ • [12.003 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile ("uppercase" as naming strategy) /go/odo_1/tests/integration/interactive_add_binding_test.go:131 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2334813290 << Captured StdOut/StdErr Output ------------------------------ ••••S•SSS•SS•SS ------------------------------ • [10.434 seconds] odo add binding interactive command tests when running a deployment should successfully add binding without devfile (default naming strategy) /go/odo_1/tests/integration/interactive_add_binding_test.go:311 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/3114493360 << Captured StdOut/StdErr Output ------------------------------ S•••••••••••S••••S••S•••SS•S•S•••SS•SSSSS•SS•••••SSSSSSSSS•S•SSSS••S••S•SS•S ------------------------------ • [9.299 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "") /go/odo_1/tests/integration/interactive_add_binding_test.go:180 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/2333948234 << Captured StdOut/StdErr Output ------------------------------ S•SS•S••• ------------------------------ • [11.007 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (custom naming strategy: "any string") /go/odo_1/tests/integration/interactive_add_binding_test.go:180 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/1963705839 << Captured StdOut/StdErr Output ------------------------------ S•SSS•••• ------------------------------ • [6.716 seconds] odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile successfully even with -v flag /go/odo_1/tests/integration/interactive_deploy_test.go:40 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy -v 4' from /tmp/1239515795 << Captured StdOut/StdErr Output ------------------------------ S•S•S•S ------------------------------ • [8.390 seconds] odo add binding interactive command tests when the component is bootstrapped should successfully add binding to the devfile (Bind as Files) /go/odo_1/tests/integration/interactive_add_binding_test.go:101 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo add binding' from /tmp/4233984199 << Captured StdOut/StdErr Output ------------------------------ ••••••S••SSS ------------------------------ • [2.633 seconds] odo deploy interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first /go/odo_1/tests/integration/interactive_deploy_test.go:109 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo deploy' from /tmp/2831776010 << Captured StdOut/StdErr Output ------------------------------ SS••SS••••SSS••S••••••••••• ------------------------------ • [78.018 seconds] odo dev interactive command tests directory is not empty when there is a match from Alizer should display welcoming messages first /go/odo_1/tests/integration/interactive_dev_test.go:112 Captured StdOut/StdErr Output >> Spawning '/go/bin/odo dev --random-ports' from /tmp/938455730 << Captured StdOut/StdErr Output ------------------------------ ••• Summarizing 1 Failure: [FAIL] odo devfile deploy command tests deploying devfile with exec when using devfile where the exec command is bound to fail [It] should print the last 100 lines of the log to the output /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:620 Ran 478 of 860 Specs in 1520.872 seconds FAIL! -- 477 Passed | 1 Failed | 0 Pending | 382 Skipped Ginkgo ran 1 suite in 26m24.101458141s Test Suite Failed You're using deprecated Ginkgo functionality: ============================================= --slow-spec-threshold is deprecated --slow-spec-threshold has been deprecated and will be removed in a future version of Ginkgo. This feature has proved to be more noisy than useful. You can use --poll-progress-after, instead, to get more actionable feedback about potentially slow specs and understand where they might be getting stuck. To silence deprecations that can be silenced set the following environment variable: ACK_GINKGO_DEPRECATIONS=2.6.0 exit status 1 make: *** [Makefile:207: test-integration-cluster] Error 1