Using Devfile proxy: 12659208-eu-de.lb.appdomain.cloud
go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=d155db6ed" ./cmd/odo/
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=32 tests/integration
Running Suite: Integration Suite - /go/odo_1/tests/integration
==============================================================
Random Seed: 1660061830 - will randomize all specs
Will run 282 of 282 specs
Running in parallel across 32 processes
••••••••••••••••••••••••••••••••••••••••••••••••••••••••
------------------------------
• [SLOW TEST] [129.911 seconds]
odo list with devfile when a component created in 'app' application show an odo deploy or dev in the list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:52
------------------------------
•
------------------------------
• [SLOW TEST] [132.929 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
------------------------------
••
------------------------------
• [SLOW TEST] [140.277 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "") when Starting a Pg service when running dev session should list the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:564
------------------------------
••••
------------------------------
• [SLOW TEST] [151.505 seconds]
odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying memoryLimit for container in Devfile should expose the endpoint on localhost
/go/odo_1/tests/integration/cmd_dev_test.go:434
------------------------------
••••••••••
------------------------------
• [SLOW TEST] [172.446 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-nlu") when Starting a Pg service when running dev session should describe the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:535
------------------------------
••
------------------------------
• [SLOW TEST] [125.922 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "") when Starting a Pg service when running dev session should describe the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:535
------------------------------
••
------------------------------
• [SLOW TEST] [132.861 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "") when Starting a Pg service when running dev session should list the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:564
------------------------------
••••••••••
------------------------------
• [SLOW TEST] [181.532 seconds]
odo dev command tests when a component is bootstrapped and pushed when odo dev is executed when deleting previous deployment and switching kubeconfig to another namespace should run odo dev on initial namespace
/go/odo_1/tests/integration/cmd_dev_test.go:239
------------------------------
••
------------------------------
• [SLOW TEST] [168.095 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "binding-uui") when Starting a Pg service when running dev session should list the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:564
------------------------------
• [SLOW TEST] [142.358 seconds]
odo list with devfile devfile has missing metadata when projectType and language is missing when the component is pushed should show 'nodejs' for 'Type' in odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:163
------------------------------
•
------------------------------
• [SLOW TEST] [165.969 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 when Update the devfile.yaml, and waiting synchronization should check cpuLimit, cpuRequests, memoryRequests after restart
/go/odo_1/tests/integration/cmd_dev_test.go:1813
------------------------------
•••••••••••••
------------------------------
• [SLOW TEST] [144.843 seconds]
odo list with devfile devfile has missing metadata when projectType is missing when the component is pushed in dev mode should show the language for 'Type' in odo list
/go/odo_1/tests/integration/cmd_devfile_list_test.go:137
------------------------------
• [SLOW TEST] [120.382 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "") when Starting a Pg service when running dev session should list the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:564
------------------------------
••••••••••••••
------------------------------
• [SLOW TEST] [174.598 seconds]
odo describe/list binding command tests when creating a component with a binding as files (service in namespace "binding-szv") when Starting a Pg service when running dev session should list the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:564
------------------------------
•••
------------------------------
• [SLOW TEST] [139.937 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
------------------------------
• [SLOW TEST] [129.642 seconds]
odo describe/list binding command tests when creating a component with a binding as environment variables (service in namespace "") when Starting a Pg service when running dev session should describe the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:535
------------------------------
••••
------------------------------
• [SLOW TEST] [121.046 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode when --follow flag is specified should successfully follow logs of running component
/go/odo_1/tests/integration/cmd_logs_test.go:216
------------------------------
• [SLOW TEST] [202.063 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml Should build the application successfully
/go/odo_1/tests/integration/cmd_dev_test.go:1702
------------------------------
••••
------------------------------
S [SKIPPED] [32.729 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:27
when Starting a PostgreSQL service [BeforeEach]
/go/odo_1/tests/integration/cmd_dev_test.go:762
when creating local files and dir and running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:777
should correctly propagate changes to the container
/go/odo_1/tests/integration/cmd_dev_test.go:802
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/120936752
Created dir: /tmp/2956737651
Setting KUBECONFIG=/tmp/2956737651/config
Creating a new project: cmd-dev-test802iqh
Running kubectl with args [kubectl create namespace cmd-dev-test802iqh]
[kubectl] namespace/cmd-dev-test802iqh created
Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test802iqh]
[kubectl] Context "odo-test-kubernetes-cluster/c8giauof0f337j4pe5u0/admin" modified.
Running kubectl with args [kubectl get namespaces]
[kubectl] NAME STATUS AGE
[kubectl] cbjruchjiht2pf0tc4t0 Active 8d
[kubectl] cmd-add-binding-test136xbt Active 40s
[kubectl] cmd-add-binding-test234lxp Active 47s
[kubectl] cmd-add-binding-test253yya Active 113s
[kubectl] cmd-add-binding-test264fhv Active 119s
[kubectl] cmd-add-binding-test278evt Active 12s
[kubectl] cmd-delete-test114mpm Active 30s
[kubectl] cmd-delete-test130gsc Active 82s
[kubectl] cmd-delete-test143drm Active 56s
[kubectl] cmd-delete-test266njs Active 53s
[kubectl] cmd-describe-component-test183sbo Terminating 100s
[kubectl] cmd-describe-list-binding-test535aai Active 39s
[kubectl] cmd-describe-list-binding-test535ljm Active 27s
[kubectl] cmd-describe-list-binding-test535qav Active 26s
[kubectl] cmd-describe-list-binding-test535ybf Terminating 2m22s
[kubectl] cmd-describe-list-binding-test564zdl Terminating 3m11s
[kubectl] cmd-dev-test1200jgz Active 29s
[kubectl] cmd-dev-test1329gdv Active 9s
[kubectl] cmd-dev-test1380xda Active 13s
[kubectl] cmd-dev-test1648kcr Active 69s
[kubectl] cmd-dev-test1702jxa Terminating 3m18s
[kubectl] cmd-dev-test1800giu Active 56s
[kubectl] cmd-dev-test1953uln Active 30s
[kubectl] cmd-dev-test666tcg Active 74s
[kubectl] cmd-dev-test752fqr Active 41s
[kubectl] cmd-dev-test802iqh Active 12s
[kubectl] cmd-dev-test963xdz Active 49s
[kubectl] cmd-devfile-build-images-test220fhs Active 17s
[kubectl] cmd-devfile-deploy-test91mbd Active 17s
[kubectl] cmd-logs-test114tvu Active 73s
[kubectl] cmd-logs-test216uth Terminating 119s
[kubectl] cmd-namespace-test75gly Active 16s
[kubectl] cmd-namespace-test90rsd Active 8s
[kubectl] default Active 158d
[kubectl] devfile-proxy Active 34d
[kubectl] generic-test61jef Active 4d1h
[kubectl] generic-test68evv Active 4d1h
[kubectl] generic-test68ygx Active 4d1h
[kubectl] ibm-cert-store Active 158d
[kubectl] ibm-operators Active 158d
[kubectl] ibm-system Active 158d
[kubectl] interactive-add-binding-test133ope Active 13s
[kubectl] interactive-add-binding-test311eyx Terminating 90s
[kubectl] interactive-add-binding-test378prx Terminating 89s
[kubectl] interactive-add-binding-test589bik Active 33s
[kubectl] kube-node-lease Active 158d
[kubectl] kube-public Active 158d
[kubectl] kube-system Active 158d
[kubectl] olm Active 48d
[kubectl] operators Active 48d
[kubectl] test Active 14d
Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test802iqh]
[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]
[odo] I0809 16:23:31.983538 22930 implem.go:106] The path for preference file is /tmp/2956737651/preference.yaml
[odo] Successfully removed registry
[odo] I0809 16:23:32.012767 22930 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
Running odo with args [odo preference add registry DefaultDevfileRegistry http://12659208-eu-de.lb.appdomain.cloud]
[odo] I0809 16:23:35.672349 23026 util.go:767] Cached response used.
[odo] I0809 16:23:35.671930 23026 implem.go:106] The path for preference file is /tmp/2956737651/preference.yaml
[odo] I0809 16:23:35.673532 23026 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
[odo] New registry successfully added
Setting current dir to: /tmp/120936752
Deleting project: cmd-dev-test802iqh
Running kubectl with args [kubectl delete namespaces cmd-dev-test802iqh --wait=false]
[kubectl] namespace "cmd-dev-test802iqh" deleted
Setting current dir to: /go/odo_1/tests/integration
Deleting dir: /tmp/120936752
Deleting dir: /tmp/2956737651
<< End Captured GinkgoWriter Output
Operators have not been setup on Kubernetes cluster yet. Remove this once the issue has been fixed.
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:764
------------------------------
•••••••••••
------------------------------
• [SLOW TEST] [167.782 seconds]
odo add binding command tests when the component is bootstrapped when adding a binding (current namespace) when odo dev is run when odo dev command is stopped should have successfully delete the binding
/go/odo_1/tests/integration/cmd_add_binding_test.go:264
------------------------------
••••
------------------------------
• [SLOW TEST] [174.778 seconds]
odo add binding command tests when the component is bootstrapped when adding a binding (current namespace) when odo dev is run should successfully bind component and service
/go/odo_1/tests/integration/cmd_add_binding_test.go:253
------------------------------
••••
------------------------------
• [SLOW TEST] [125.676 seconds]
odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 should check cpuLimit, cpuRequests, memoryRequests
/go/odo_1/tests/integration/cmd_dev_test.go:1800
------------------------------
•••••
------------------------------
• [SLOW TEST] [120.118 seconds]
odo dev command tests when creating local files and dir and running odo dev when deleting local files and dir and waiting for sync should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:752
------------------------------
• [SLOW TEST] [135.511 seconds]
odo delete command tests when a component is bootstrapped when component is deployed to the cluster in the namespace set in env.yaml which is not the same as the current active namespace when the component is deleted should have deleted the component
/go/odo_1/tests/integration/cmd_delete_test.go:266
------------------------------
••
------------------------------
• [SLOW TEST] [129.756 seconds]
odo add binding command tests when binding to a service in a different namespace should error out if service is not found in list of services of namespace selected
/go/odo_1/tests/integration/cmd_add_binding_test.go:136
------------------------------
••
------------------------------
S [SKIPPED] [36.510 seconds]
odo dev command tests
/go/odo_1/tests/integration/cmd_dev_test.go:27
when Starting a PostgreSQL service [BeforeEach]
/go/odo_1/tests/integration/cmd_dev_test.go:762
when creating local files and dir and running odo dev
/go/odo_1/tests/integration/cmd_dev_test.go:777
when deleting local files and dir and waiting for sync
/go/odo_1/tests/integration/cmd_dev_test.go:811
should not list deleted dir and file in container
/go/odo_1/tests/integration/cmd_dev_test.go:819
Begin Captured GinkgoWriter Output >>
Created dir: /tmp/880882255
Created dir: /tmp/3574395524
Setting KUBECONFIG=/tmp/3574395524/config
Creating a new project: cmd-dev-test819hpf
Running kubectl with args [kubectl create namespace cmd-dev-test819hpf]
[kubectl] namespace/cmd-dev-test819hpf created
Running kubectl with args [kubectl config set-context --current --namespace cmd-dev-test819hpf]
[kubectl] Context "odo-test-kubernetes-cluster/c8giauof0f337j4pe5u0/admin" modified.
Running kubectl with args [kubectl get namespaces]
[kubectl] NAME STATUS AGE
[kubectl] cbjruchjiht2pf0tc4t0 Active 8d
[kubectl] cmd-add-binding-test136jkv Active 51s
[kubectl] cmd-add-binding-test136szj Active 25s
[kubectl] cmd-add-binding-test136xbt Active 109s
[kubectl] cmd-add-binding-test253yya Terminating 3m2s
[kubectl] cmd-delete-test266njs Active 2m2s
[kubectl] cmd-delete-test266uze Active 39s
[kubectl] cmd-delete-test67amj Active 8s
[kubectl] cmd-describe-component-test29usu Active 28s
[kubectl] cmd-describe-list-binding-test535aai Active 108s
[kubectl] cmd-describe-list-binding-test535ljm Active 96s
[kubectl] cmd-describe-list-binding-test535qav Active 95s
[kubectl] cmd-dev-test1047gxd Active 9s
[kubectl] cmd-dev-test1200jgz Active 98s
[kubectl] cmd-dev-test1329gdv Active 78s
[kubectl] cmd-dev-test1443ugv Active 28s
[kubectl] cmd-dev-test1587gix Active 4s
[kubectl] cmd-dev-test1800giu Terminating 2m5s
[kubectl] cmd-dev-test1953uln Terminating 99s
[kubectl] cmd-dev-test2018rmh Active 52s
[kubectl] cmd-dev-test651thi Active 40s
[kubectl] cmd-dev-test752fqr Active 110s
[kubectl] cmd-dev-test819hpf Active 10s
[kubectl] cmd-dev-test874izo Active 66s
[kubectl] cmd-dev-test896pea Active 69s
[kubectl] cmd-devfile-build-images-test58kmn Active 15s
[kubectl] cmd-devfile-deploy-test126fey Active 49s
[kubectl] cmd-devfile-deploy-test126tdt Active 8s
[kubectl] cmd-devfile-deploy-test272kxh Terminating 37s
[kubectl] cmd-logs-test188wiy Active 26s
[kubectl] cmd-logs-test47jui Terminating 28s
[kubectl] default Active 158d
[kubectl] devfile-proxy Active 34d
[kubectl] generic-test61jef Active 4d1h
[kubectl] generic-test61ked Active 13s
[kubectl] generic-test68evv Active 4d1h
[kubectl] generic-test68ygx Active 4d1h
[kubectl] ibm-cert-store Active 158d
[kubectl] ibm-operators Active 158d
[kubectl] ibm-system Active 158d
[kubectl] interactive-add-binding-test133lor Active 4s
[kubectl] interactive-add-binding-test182emw Active 50s
[kubectl] interactive-add-binding-test378vox Active 46s
[kubectl] interactive-add-binding-test575hsl Active 20s
[kubectl] interactive-add-binding-test589bik Active 102s
[kubectl] interactive-add-binding-test589cya Active 15s
[kubectl] interactive-add-binding-test589efn Active 42s
[kubectl] interactive-add-binding-test75nfn Active 52s
[kubectl] kube-node-lease Active 158d
[kubectl] kube-public Active 158d
[kubectl] kube-system Active 158d
[kubectl] olm Active 48d
[kubectl] operators Active 48d
[kubectl] test Active 14d
Running kubectl with args [kubectl create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test819hpf]
[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]
[odo] I0809 16:24:44.258732 25575 implem.go:106] The path for preference file is /tmp/3574395524/preference.yaml
[odo] Successfully removed registry
[odo] I0809 16:24:44.273842 25575 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
Running odo with args [odo preference add registry DefaultDevfileRegistry http://12659208-eu-de.lb.appdomain.cloud]
[odo] I0809 16:24:47.029372 25728 implem.go:106] The path for preference file is /tmp/3574395524/preference.yaml
[odo] New registry successfully added
[odo] I0809 16:24:47.037916 25728 odo.go:75] Could not get the latest release information in time. Never mind, exiting gracefully :)
Setting current dir to: /tmp/880882255
Deleting project: cmd-dev-test819hpf
Running kubectl with args [kubectl delete namespaces cmd-dev-test819hpf --wait=false]
[kubectl] namespace "cmd-dev-test819hpf" deleted
Setting current dir to: /go/odo_1/tests/integration
Deleting dir: /tmp/880882255
Deleting dir: /tmp/3574395524
<< End Captured GinkgoWriter Output
Operators have not been setup on Kubernetes cluster yet. Remove this once the issue has been fixed.
In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:764
------------------------------
•••
------------------------------
• [SLOW TEST] [141.736 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "") when Starting a Pg service when running dev session should describe the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:535
------------------------------
•••
------------------------------
• [SLOW TEST] [135.134 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-wed") when Starting a Pg service when running dev session should describe the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:535
------------------------------
• [SLOW TEST] [135.714 seconds]
odo describe/list binding command tests when creating a component with a spec binding (service in namespace "binding-kin") when Starting a Pg service when running dev session should describe the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:535
------------------------------
•••••••••
------------------------------
• [SLOW TEST] [129.878 seconds]
odo dev command tests when running build and run commands as composite in different containers and a shared volume should run successfully
/go/odo_1/tests/integration/cmd_dev_test.go:1329
------------------------------
•
------------------------------
• [SLOW TEST] [162.710 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:589
------------------------------
••••••••••••
------------------------------
• [SLOW TEST] [120.399 seconds]
odo logs command tests when component is created and odo logs is executed when running in both Dev and Deploy mode should successfully show logs of the running component
/go/odo_1/tests/integration/cmd_logs_test.go:188
------------------------------
•••••••••••••••••••
------------------------------
• [SLOW TEST] [161.010 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:575
------------------------------
••••••
------------------------------
• [SLOW TEST] [129.861 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "binding-axb") when Starting a Pg service when running dev session should list the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:564
------------------------------
••
------------------------------
• [SLOW TEST] [128.059 seconds]
odo describe/list binding command tests when creating a component with a spec binding and envvars (service in namespace "") when Starting a Pg service when running dev session should describe the binding
/go/odo_1/tests/integration/cmd_describe_list_binding_test.go:535
------------------------------
•••••
------------------------------
• [SLOW TEST] [124.865 seconds]
odo add binding command tests when binding to a service in a different namespace should create a binding using the workload parameter
/go/odo_1/tests/integration/cmd_add_binding_test.go:145
------------------------------
••••••••••••••••••
------------------------------
• [SLOW TEST] [120.969 seconds]
odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume should run successfully
/go/odo_1/tests/integration/cmd_dev_debug_test.go:147
------------------------------
••••
------------------------------
• [SLOW TEST] [195.960 seconds]
odo add binding command tests when the component is bootstrapped when adding a binding (other namespace) when odo dev is run should successfully bind component and service
/go/odo_1/tests/integration/cmd_add_binding_test.go:253
------------------------------
•••
------------------------------
• [SLOW TEST] [187.230 seconds]
odo add binding command tests when the component is bootstrapped when adding a binding (other namespace) when odo dev is run when odo dev command is stopped should have successfully delete the binding
/go/odo_1/tests/integration/cmd_add_binding_test.go:264
------------------------------
•
------------------------------
• [SLOW TEST] [187.363 seconds]
odo dev command tests when java-springboot application is created and running odo dev when Update the devfile.yaml when compare the local and remote files localFiles and remoteFiles should match
/go/odo_1/tests/integration/cmd_dev_test.go:1753
------------------------------
Ran 280 of 282 Specs in 655.152 seconds
SUCCESS! -- 280 Passed | 0 Failed | 0 Pending | 2 Skipped
Ginkgo ran 1 suite in 11m56.719673671s
Test Suite Passed
go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --slow-spec-threshold=120s -timeout 14400s --no-color -nodes=32 tests/e2escenarios
Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios
===============================================================
Random Seed: 1660062553 - will randomize all specs
Will run 6 of 6 specs
Running in parallel across 32 processes
•••
------------------------------
• [SLOW TEST] [120.511 seconds]
odo devfile supported tests odo debug support for devfile components Verify output debug information for java-quarkus debug works
/go/odo_1/tests/e2escenarios/e2e_devfile_test.go:74
------------------------------
• [SLOW TEST] [138.759 seconds]
E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:161
------------------------------
• [SLOW TEST] [144.123 seconds]
E2E Test starting with empty Directory should verify developer workflow from empty Directory
/go/odo_1/tests/e2escenarios/e2e_test.go:46
------------------------------
Ran 6 of 6 Specs in 144.130 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 0 Skipped
Ginkgo ran 1 suite in 2m45.613359881s
Test Suite Passed