cp ododevapispec.yaml pkg/apiserver-impl/swagger-ui/swagger.yaml go install -mod=vendor -ldflags="-X github.com/redhat-developer/odo/pkg/version.GITCOMMIT=3048a4c75" ./cmd/odo/ go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --poll-progress-after=120s --poll-progress-interval=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: 1701426004 - will randomize all specs Will run 504 of 962 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ S [17.968 seconds] odo dev command tests when a component is bootstrapped [It] should not set securitycontext for podsecurity admission /go/odo_1/tests/integration/cmd_dev_test.go:392 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44947" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: /go/odo_1/tests/integration/cmd_dev_test.go:394 @ 12/01/23 10:21:26.251 ------------------------------ S [16.930 seconds] odo devfile deploy command tests deploying devfile with long-running exec when pod security is enforced as restricted [It] should set securitycontext for podsecurity admission on job's pod template /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:676 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43711" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:678 @ 12/01/23 10:21:25.673 ------------------------------ S ------------------------------ • [19.360 seconds] odo dev command tests when Devfile contains metadata.projectType invalid as a label value when odo deploy is executed should set the correct value in labels of deployed resources /go/odo_1/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34975" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [21.282 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in= should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39705" << Captured StdOut/StdErr Output ------------------------------ • [8.005 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with default variable values (push=false) /go/odo_1/tests/integration/cmd_devfile_build_images_test.go:431 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41375" << Captured StdOut/StdErr Output ------------------------------ • [10.436 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42279" << Captured StdOut/StdErr Output ------------------------------ • [34.337 seconds] odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should error out on an invalid command /go/odo_1/tests/integration/cmd_dev_test.go:3150 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34945" << Captured StdOut/StdErr Output ------------------------------ • [7.507 seconds] odo devfile deploy command tests when a component is bootstrapped when using a default namespace should display warning when running the deploy command /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:67 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43597" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [37.956 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46315" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [61.295 seconds] odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=true /go/odo_1/tests/integration/cmd_dev_test.go:4921 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38211" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [69.798 seconds] odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should execute the custom non-default build command successfully /go/odo_1/tests/integration/cmd_dev_test.go:3112 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43407" << Captured StdOut/StdErr Output ------------------------------ • [72.876 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34409" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [80.285 seconds] odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) Default output when describing the component in dev mode should describe the component /go/odo_1/tests/integration/cmd_describe_component_test.go:373 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40351" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [11.020 seconds] odo logs command tests when component is created and odo logs is executed when running in Deploy mode should successfully show logs of the running component /go/odo_1/tests/integration/cmd_logs_test.go:267 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33159" << Captured StdOut/StdErr Output ------------------------------ • [9.760 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:241 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45329" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [61.948 seconds] odo dev command tests when devfile project field is present and running odo dev - without metadata.name should sync to the correct dir in container /go/odo_1/tests/integration/cmd_dev_test.go:2097 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44733" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [57.484 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should start the Dev server when --api-server flag is passed /go/odo_1/tests/integration/cmd_dev_api_server_test.go:98 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34699" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [7.261 seconds] odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when an env.yaml file contains a non-current Project when running odo deploy should succeed /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:201 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43915" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [7.098 seconds] odo dev command tests when Devfile contains metadata.language invalid as a label value when odo deploy is executed should set the correct value in labels of deployed resources /go/odo_1/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34511" << Captured StdOut/StdErr Output ------------------------------ • [5.868 seconds] odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not build images /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:502 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38117" << Captured StdOut/StdErr Output ------------------------------ • [6.455 seconds] odo devfile deploy command tests when using a devfile.yaml containing two deploy commands should run odo deploy /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:244 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34883" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.768 seconds] odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var-file flag should check if the env variable has a correct value /go/odo_1/tests/integration/cmd_dev_test.go:1639 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38539" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [6.422 seconds] odo devfile deploy command tests when using a devfile.yaml containing an Image component with a build context should build image via Podman if build context references PROJECT_SOURCE env var /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:326 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32815" << Captured StdOut/StdErr Output ------------------------------ • [6.281 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args should succeed /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38379" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [95.444 seconds] odo dev debug command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components not referenced in the Devfile should create the appropriate resources /go/odo_1/tests/integration/cmd_dev_debug_test.go:501 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33283" << Captured StdOut/StdErr Output ------------------------------ • [10.383 seconds] odo logs command tests when odo logs is executed for a component that's not running in any modes should print that no containers are running /go/odo_1/tests/integration/cmd_logs_test.go:99 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43513" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [6.185 seconds] odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - with metadata.name should correctly propagate changes to the container [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815 [It] /go/odo_1/tests/integration/cmd_dev_test.go:1865 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41851" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 10:22:50.828 ------------------------------ • [6.574 seconds] odo dev command tests when Devfile contains metadata.language when odo deploy is executed should set the correct value in labels of deployed resources /go/odo_1/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40531" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [7.723 seconds] odo describe component command tests when creating a component should not describe the component from another directory, with cluster /go/odo_1/tests/integration/cmd_describe_component_test.go:314 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44537" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [108.693 seconds] odo dev command tests when a component is bootstrapped when a delay is necessary for the component to start and running odo dev should first fail then succeed querying endpoint /go/odo_1/tests/integration/cmd_dev_test.go:789 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41175" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [110.408 seconds] odo dev command with api server tests when the component is bootstrapped when odo is executed with --no-watch and --api-server flags when a file in component directory is modified when /component/command endpoint is POSTed should trigger a push /go/odo_1/tests/integration/cmd_dev_api_server_test.go:282 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34193" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [110.740 seconds] odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands=false when a file in component directory is modified when p is pressed should trigger a push /go/odo_1/tests/integration/cmd_dev_test.go:754 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46181" << Captured StdOut/StdErr Output ------------------------------ • [25.307 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should error out on an invalid command /go/odo_1/tests/integration/cmd_dev_test.go:3080 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45623" << Captured StdOut/StdErr Output ------------------------------ • [5.395 seconds] odo devfile init command tests setting application ports when running odo init --run-port with a Devfile with no commands should overwrite the ports into the container component referenced by the default run command /go/odo_1/tests/integration/cmd_devfile_init_test.go:648 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41877" << Captured StdOut/StdErr Output ------------------------------ • [10.958 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42525" << Captured StdOut/StdErr Output ------------------------------ • [80.826 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=false, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39253" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [67.971 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/foobar.txt file should not synchronize it /go/odo_1/tests/integration/cmd_dev_test.go:1987 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34651" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [49.596 seconds] odo dev debug command tests when a component without debug command is bootstrapped should log error about missing debug command when running odo dev --debug /go/odo_1/tests/integration/cmd_dev_debug_test.go:444 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43951" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ Progress Report for Ginkgo Process #9 Automatically polling progress: odo dev command tests when doing odo dev and there is a env variable with spaces - without metadata.name should be able to exec command (Spec Runtime: 2m12.283s) /go/odo_1/tests/integration/cmd_dev_test.go:1743 In [It] (Node Runtime: 2m0s) /go/odo_1/tests/integration/cmd_dev_test.go:1743 Begin Captured GinkgoWriter Output >> ... [odo] read: read /dev/stdin: input/output error [odo] I1201 10:22:56.497297 12986 watch.go:333] Dev mode interrupted by user [odo] I1201 10:22:56.503422 12986 implem.go:114] The path for preference file is /tmp/1241649588/preference.yaml [odo] Cleaning resources, please wait [odo] I1201 10:22:56.505174 12986 segment.go:268] Checking telemetry enable status [odo] I1201 10:22:56.505186 12986 segment.go:286] Sending telemetry disabled by env variable [odo] I1201 10:22:56.625750 12986 all.go:46] starting to concurrently query 201 APIs [odo] I1201 10:22:56.625899 12986 all.go:62] fired up all goroutines to query APIs [odo] I1201 10:22:57.944480 12986 all.go:67] all goroutines have returned in 1.318150828s [odo] I1201 10:22:57.944584 12986 all.go:76] query result: objects=627 << End Captured GinkgoWriter Output Spec Goroutine goroutine 70 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00015f7a0, {0x314bfb8?, 0xc00088d848}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00015f7a0, {0x314bfb8, 0xc00088d848}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc000dcfd70?, {0xc0007e0820?, 0xc000dcfc38?, 0x2?}) /go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) /go/odo_1/tests/helper/helper_dev.go:263 github.com/redhat-developer/odo/tests/helper.RunDevMode.func1() /go/odo_1/tests/helper/helper_dev.go:334 github.com/redhat-developer/odo/tests/helper.RunDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...}, ...) /go/odo_1/tests/helper/helper_dev.go:337 > github.com/redhat-developer/odo/tests/integration.glob..func7.13.2() /go/odo_1/tests/integration/cmd_dev_test.go:1744 | | It("should be able to exec command", func() { > err := helper.RunDevMode(helper.DevSessionOpts{ | RunOnPodman: podman, | }, func(session *gexec.Session, out, err string, ports map[string]string) { github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ • [4.229 seconds] odo dev command tests when running applications listening on the container loopback interface should error out if using --ignore-localhost on any platform other than Podman /go/odo_1/tests/integration/cmd_dev_test.go:4211 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42355" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [3.915 seconds] odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with no Deploy command should fail to run odo deploy /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:880 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35765" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [139.182 seconds] odo dev command tests when doing odo dev and there is a env variable with spaces - without metadata.name should be able to exec command /go/odo_1/tests/integration/cmd_dev_test.go:1743 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41201" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [121.819 seconds] odo dev command tests Devfile with no metadata.name when running odo dev against a component with no source code should use the directory as component name /go/odo_1/tests/integration/cmd_dev_test.go:3873 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33813" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [28.189 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40655" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [141.711 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:348 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37083" << Captured StdOut/StdErr Output ------------------------------ • [4.592 seconds] odo devfile build-images command tests when starting with Devfile with autoBuild or deployByDefault components when building images should build all Image components regardless of autoBuild /go/odo_1/tests/integration/cmd_devfile_build_images_test.go:364 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35179" << Captured StdOut/StdErr Output ------------------------------ • [7.521 seconds] odo create/delete/list/set namespace/project tests when namespace is created with -w should list the new namespace when listing namespace /go/odo_1/tests/integration/cmd_namespace_test.go:41 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35679" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [119.695 seconds] odo dev command tests when running odo dev with devfile contain volume - with metadata.name check the volume name and mount paths for the containers /go/odo_1/tests/integration/cmd_dev_test.go:2230 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42363" << Captured StdOut/StdErr Output ------------------------------ • [61.262 seconds] odo dev command tests when a container component defines a Command or Args - without metadata.name should run odo dev successfully (#5620) /go/odo_1/tests/integration/cmd_dev_test.go:3538 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39827" << Captured StdOut/StdErr Output ------------------------------ • [58.692 seconds] odo dev command tests when creating local files and dir and running odo dev - without metadata.name should correctly propagate changes to the container /go/odo_1/tests/integration/cmd_dev_test.go:1788 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32989" << Captured StdOut/StdErr Output ------------------------------ • [61.086 seconds] odo dev command tests when a component is bootstrapped should sync .git directory and subfiles with --sync-git-dir /go/odo_1/tests/integration/cmd_dev_test.go:182 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45337" << Captured StdOut/StdErr Output ------------------------------ • [52.989 seconds] odo dev command tests when a component is bootstrapped when running with --no-commands (debug=false) should start the dev session /go/odo_1/tests/integration/cmd_dev_test.go:268 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43599" << Captured StdOut/StdErr Output ------------------------------ • [6.343 seconds] odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces in JSON format /go/odo_1/tests/integration/cmd_namespace_test.go:228 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46385" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.639 seconds] odo dev command tests when a component is bootstrapped when run command takes really long to start should cancel run command and return if odo dev is stopped /go/odo_1/tests/integration/cmd_dev_test.go:1002 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41973" << Captured StdOut/StdErr Output ------------------------------ • [59.153 seconds] odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should execute the default run command successfully if specified explicitly /go/odo_1/tests/integration/cmd_dev_test.go:3195 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43039" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [9.777 seconds] odo generic When deleting two project one after the other should be able to delete them in any order /go/odo_1/tests/integration/generic_test.go:107 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40205" << Captured StdOut/StdErr Output ------------------------------ • [65.301 seconds] odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=a-command-not-found-for-podman-should-make-odo-fallback-to-docker DOCKER_CMD=echo] remote server returns a valid file when odo dev is run should build and push image when odo dev is run /go/odo_1/tests/integration/cmd_dev_test.go:2526 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45495" << Captured StdOut/StdErr Output ------------------------------ • [57.127 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should start the Dev server when --api-server flag is passed /go/odo_1/tests/integration/cmd_dev_api_server_test.go:98 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46631" << Captured StdOut/StdErr Output ------------------------------ • [31.410 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33357" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [59.631 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=false, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40459" << Captured StdOut/StdErr Output ------------------------------ • [6.630 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:241 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36861" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.602 seconds] odo dev command tests when Devfile contains metadata.projectType when odo deploy is executed should set the correct value in labels of deployed resources /go/odo_1/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36671" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [112.304 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=false, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43567" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ • [59.160 seconds] odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) JSON output when describing the component in dev mode should describe the component /go/odo_1/tests/integration/cmd_describe_component_test.go:441 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37713" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [7.078 seconds] odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when an env.yaml file contains a non-current Project when running odo deploy when the env.yaml file still contains a non-current Project should delete the component in the current namespace /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:226 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37411" << Captured StdOut/StdErr Output ------------------------------ • [62.002 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42119" << Captured StdOut/StdErr Output ------------------------------ • [52.634 seconds] odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=false /go/odo_1/tests/integration/cmd_dev_test.go:4921 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38705" << Captured StdOut/StdErr Output ------------------------------ • [18.333 seconds] odo create/delete/list/set namespace/project tests delete namespace when force-deleting a valid namespace should successfully delete the namespace asynchronously /go/odo_1/tests/integration/cmd_namespace_test.go:107 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33429" << Captured StdOut/StdErr Output ------------------------------ • [69.351 seconds] odo dev command tests when a component is bootstrapped should show validation errors if the devfile is incorrect /go/odo_1/tests/integration/cmd_dev_test.go:156 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41049" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [5.188 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should succeed /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35059" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [56.540 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag should serve endpoints /go/odo_1/tests/integration/cmd_dev_api_server_test.go:171 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46151" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [7.118 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=deploy should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42999" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [109.313 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=true, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41391" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [75.184 seconds] odo dev command tests cleanup of resources is not successful when using a Devfile with a Pod failing to delete before the cleanup timeout when odo dev is executed when odo dev is stopped should report that the component could not be deleted /go/odo_1/tests/integration/cmd_dev_test.go:5007 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39603" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [132.872 seconds] odo dev command tests multiple dev sessions with different project are running on same platform (podman=false), same port when odo dev session is run for nodejs component when odo dev session is run for go project on the same port but different address when go and nodejs files are modified should be possible to access both the projects on same address and port /go/odo_1/tests/integration/cmd_dev_test.go:1237 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33803" << Captured StdOut/StdErr Output ------------------------------ • [120.847 seconds] odo dev command tests when running odo dev and multiple env variables are set - without metadata.name should be able to exec command /go/odo_1/tests/integration/cmd_dev_test.go:1717 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45455" << Captured StdOut/StdErr Output ------------------------------ • [7.862 seconds] odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with Deploy commands when running odo deploy with some components not referenced in the Devfile should create the appropriate resources /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:725 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33027" << Captured StdOut/StdErr Output ------------------------------ • [9.845 seconds] odo create/delete/list/set namespace/project tests create project should fail to create project /go/odo_1/tests/integration/cmd_namespace_test.go:63 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46725" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [8.590 seconds] odo create/delete/list/set namespace/project tests list project should successfully list all the projects in JSON format /go/odo_1/tests/integration/cmd_namespace_test.go:228 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44461" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.060 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39809" << Captured StdOut/StdErr Output ------------------------------ • [44.364 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32949" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [12.805 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 >> Using Devfile Registry URL at: "http://127.0.0.1:38157" Spawning '/go/bin/odo dev --random-ports' from /tmp/2992770357 << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [110.422 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=false, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41389" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [6.997 seconds] odo devfile deploy command tests when deploying a Devfile OpenShift component with multiple K8s resources defined should have created all the resources defined in the Devfile OpenShift component /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:372 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34709" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [59.325 seconds] odo dev command tests when devfile has sourcemappings and running odo dev - without metadata.name should sync files to the correct location /go/odo_1/tests/integration/cmd_dev_test.go:2016 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45999" << Captured StdOut/StdErr Output ------------------------------ • [70.652 seconds] odo dev command tests when Create and dev java-springboot component should execute default build and run commands correctly /go/odo_1/tests/integration/cmd_dev_test.go:2931 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36493" << Captured StdOut/StdErr Output ------------------------------ • [119.127 seconds] odo dev command tests when a hotReload capable Run command is used with odo dev when a source file is modified should not re-execute the run command /go/odo_1/tests/integration/cmd_dev_test.go:3787 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40105" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [8.313 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=deploy should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42489" << Captured StdOut/StdErr Output ------------------------------ • [5.813 seconds] odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not build images /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:502 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41637" << Captured StdOut/StdErr Output ------------------------------ S [6.507 seconds] odo devfile deploy command tests deploying devfile with exec [It] should not set securitycontext for podsecurity admission on job's pod template /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:601 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33387" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:603 @ 12/01/23 10:26:02.056 ------------------------------ • [113.383 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=true, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37425" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [5.674 seconds] odo devfile build-images command tests when starting with Devfile with autoBuild or deployByDefault components when building and pushing images should build and push all Image components regardless of autoBuild /go/odo_1/tests/integration/cmd_devfile_build_images_test.go:385 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36577" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [9.662 seconds] odo create/delete/list/set namespace/project tests set namespace when running inside a component directory should set the namespace /go/odo_1/tests/integration/cmd_namespace_test.go:190 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40237" << Captured StdOut/StdErr Output ------------------------------ • [74.693 seconds] odo devfile deploy command tests deploying devfile with exec when using devfile with a long running command in exec should print the tip to run odo logs after 1 minute of execution /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:636 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44457" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [6.774 seconds] odo dev command tests when running odo dev and prestart events are defined should not correctly execute PreStart commands /go/odo_1/tests/integration/cmd_dev_test.go:2823 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45617" << Captured StdOut/StdErr Output ------------------------------ • [8.902 seconds] odo generic When deleting two project one after the other should be able to delete sequentially /go/odo_1/tests/integration/generic_test.go:100 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39673" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [49.068 seconds] odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=echo] remote server returns an error when odo dev is run should not build images when odo dev is run /go/odo_1/tests/integration/cmd_dev_test.go:2549 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45527" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.939 seconds] odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag should connect to relevant ports forwarded /go/odo_1/tests/integration/cmd_dev_debug_test.go:112 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40433" << Captured StdOut/StdErr Output ------------------------------ • [7.165 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=dev should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38907" << Captured StdOut/StdErr Output ------------------------------ • [120.018 seconds] odo dev command tests when running odo dev with devfile contain volume - without metadata.name check the volume name and mount paths for the containers /go/odo_1/tests/integration/cmd_dev_test.go:2230 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42387" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.245 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag when /instance endpoint is DELETEd should terminate the dev session /go/odo_1/tests/integration/cmd_dev_api_server_test.go:239 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42135" <<< Session terminated >>> << Captured StdOut/StdErr Output ------------------------------ • [6.519 seconds] odo describe component command tests should fail, with cluster /go/odo_1/tests/integration/cmd_describe_component_test.go:89 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37133" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [133.253 seconds] odo describe component command tests checking for remote source code location when using devfile with containers that has mountSource set to false and starting an odo dev session should show remote source code location in odo describe component output /go/odo_1/tests/integration/cmd_describe_component_test.go:667 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41571" << Captured StdOut/StdErr Output ------------------------------ • [6.952 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 >> Using Devfile Registry URL at: "http://127.0.0.1:43231" Spawning '/go/bin/odo deploy -v 4' from /tmp/1320751571 << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [79.209 seconds] odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag and custom port mapping for port forwarding should connect to relevant custom ports forwarded /go/odo_1/tests/integration/cmd_dev_debug_test.go:76 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42665" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [88.709 seconds] odo dev command tests 1. devfile contains composite apply command when odo dev is running with container backend global extra args should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43195" << Captured StdOut/StdErr Output ------------------------------ • [130.163 seconds] odo dev command tests when running odo dev and composite command is used as a run command - without metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_test.go:2709 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42575" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.996 seconds] odo dev command tests when running odo dev and composite command are nested - with metadata.name should execute all commands in composite commmand /go/odo_1/tests/integration/cmd_dev_test.go:2674 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42435" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [79.959 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/baz.txt file should synchronize it only /go/odo_1/tests/integration/cmd_dev_test.go:1965 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43103" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [59.412 seconds] odo dev command tests when a component is bootstrapped when recording telemetry data should record the telemetry data correctly /go/odo_1/tests/integration/cmd_dev_test.go:458 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39227" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [61.329 seconds] odo dev command tests when a component is bootstrapped should use the index information from previous push operation /go/odo_1/tests/integration/cmd_dev_test.go:200 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35513" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [115.223 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:320 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38441" << Captured StdOut/StdErr Output ------------------------------ • [7.329 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33075" << Captured StdOut/StdErr Output ------------------------------ • [121.617 seconds] odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args when running and stopping odo dev should not delete the resources created with odo deploy /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45061" << Captured StdOut/StdErr Output ------------------------------ • [112.874 seconds] odo dev command tests multiple dev sessions with different project are running on same platform (podman=false), same port when odo dev session is run for nodejs component when odo dev session is run for go project on the same port but different address should be able to run both the sessions /go/odo_1/tests/integration/cmd_dev_test.go:1213 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38289" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [59.213 seconds] odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands=false when a file in component directory is modified should not trigger a push /go/odo_1/tests/integration/cmd_dev_test.go:736 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46575" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [59.975 seconds] odo dev command tests when odo dev is executed to run a devfile containing a k8s resource should have created the necessary k8s resources /go/odo_1/tests/integration/cmd_dev_test.go:1127 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36445" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [57.439 seconds] odo dev command tests when running odo dev and devfile with composite command - without metadata.name should execute all commands in composite command /go/odo_1/tests/integration/cmd_dev_test.go:2610 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43251" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [68.021 seconds] odo dev command tests when a component with multiple endpoints is run should fail running a second session on the same platform /go/odo_1/tests/integration/cmd_dev_test.go:3615 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39447" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [26.634 seconds] odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=false should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:517 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45075" << Captured StdOut/StdErr Output ------------------------------ • [10.388 seconds] odo devfile deploy command tests deploying devfile with exec when using devfile that works; with component name of at max(63) characters length should complete the command execution successfully /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:576 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37239" << Captured StdOut/StdErr Output ------------------------------ • [59.663 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=true, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37233" << Captured StdOut/StdErr Output ------------------------------ • [118.257 seconds] odo dev command tests when running odo dev and multiple env variables are set - with metadata.name should be able to exec command /go/odo_1/tests/integration/cmd_dev_test.go:1717 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41873" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [48.028 seconds] odo dev command tests when running odo dev and build command throws an error should error out with some log /go/odo_1/tests/integration/cmd_dev_test.go:2898 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39049" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [3.447 seconds] odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - without metadata.name should correctly propagate changes to the container [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815 [It] /go/odo_1/tests/integration/cmd_dev_test.go:1865 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36523" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 10:28:12.588 ------------------------------ • [120.551 seconds] odo describe component command tests checking for remote source code location when using devfile with no sourceMapping, defaults to /projects and starting an odo dev session should show remote source code location in odo describe component output /go/odo_1/tests/integration/cmd_describe_component_test.go:667 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40123" << Captured StdOut/StdErr Output ------------------------------ SS•SS ------------------------------ • [5.930 seconds] odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces /go/odo_1/tests/integration/cmd_namespace_test.go:221 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40655" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [28.930 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40629" << Captured StdOut/StdErr Output ------------------------------ • [28.407 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45313" << Captured StdOut/StdErr Output ------------------------------ • [86.652 seconds] odo dev command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components referenced in the Devfile should create the appropriate resources /go/odo_1/tests/integration/cmd_dev_test.go:4579 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37881" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [7.333 seconds] odo dev command with api server tests when the component is bootstrapped should fail if --random-ports and --api-server-port are used together /go/odo_1/tests/integration/cmd_dev_api_server_test.go:63 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43021" << Captured StdOut/StdErr Output ------------------------------ • [7.426 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=dev should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38993" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [9.642 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=deploy should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42559" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [71.244 seconds] odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume - with metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35065" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [50.817 seconds] odo dev command tests when a component is bootstrapped when using a default namespace should print warning about default namespace when running odo dev /go/odo_1/tests/integration/cmd_dev_test.go:130 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40843" << Captured StdOut/StdErr Output ------------------------------ • [8.548 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33163" << Captured StdOut/StdErr Output ------------------------------ • [79.670 seconds] odo dev command tests when creating local files and dir and running odo dev - without metadata.name 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:1805 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46065" << Captured StdOut/StdErr Output ------------------------------ • [85.742 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args should run odo dev successfully /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42357" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [6.399 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 >> Using Devfile Registry URL at: "http://127.0.0.1:33769" Spawning '/go/bin/odo deploy' from /tmp/2642764619 << Captured StdOut/StdErr Output ------------------------------ • [9.689 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37905" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [6.092 seconds] odo list with devfile listing non-odo managed components when a non-odo managed component without the managed-by label is deployed should list the component with odo list /go/odo_1/tests/integration/cmd_devfile_list_test.go:67 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39863" << Captured StdOut/StdErr Output ------------------------------ • [5.942 seconds] odo dev command tests when running applications listening on the container loopback interface should error out if using --forward-localhost on any platform other than Podman /go/odo_1/tests/integration/cmd_dev_test.go:4220 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38921" << Captured StdOut/StdErr Output ------------------------------ • [24.191 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:211 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39027" Spawning '/go/bin/odo dev --random-ports --no-watch' from /tmp/1991441315 << Captured StdOut/StdErr Output ------------------------------ • [60.174 seconds] odo dev command tests when Devfile contains metadata.language when running odo dev should set the correct value in labels of resources /go/odo_1/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42867" << Captured StdOut/StdErr Output ------------------------------ • [124.714 seconds] odo dev command tests when running odo dev with devfile contain volume - without metadata.name should create pvc and reuse if it shares the same devfile volume name /go/odo_1/tests/integration/cmd_dev_test.go:2197 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38195" << Captured StdOut/StdErr Output ------------------------------ • [40.318 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38701" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ S [6.833 seconds] odo init interactive command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should download correct devfile from the first in-cluster registry [BeforeEach] /go/odo_1/tests/integration/interactive_init_test.go:708 [It] /go/odo_1/tests/integration/interactive_init_test.go:737 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44587" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/interactive_init_test.go:710 @ 12/01/23 10:29:06.675 ------------------------------ SS ------------------------------ • [119.423 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=false, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35369" << Captured StdOut/StdErr Output ------------------------------ • [85.796 seconds] odo dev command tests 1. devfile contains composite apply command when odo dev is running with container run extra args should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45823" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [130.326 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:3269 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32911" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [60.819 seconds] odo dev command tests when a component is bootstrapped should not sync .git directory /go/odo_1/tests/integration/cmd_dev_test.go:166 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41569" << Captured StdOut/StdErr Output ------------------------------ S [5.537 seconds] odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - without metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815 [It] /go/odo_1/tests/integration/cmd_dev_test.go:1882 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46333" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 10:29:18.843 ------------------------------ • [86.902 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 >> Using Devfile Registry URL at: "http://127.0.0.1:42275" Spawning '/go/bin/odo dev --random-ports' from /tmp/1755312196 << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ S [5.856 seconds] odo devfile registry command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should list detailed information regarding nodejs when using an in-cluster registry [BeforeEach] /go/odo_1/tests/integration/cmd_devfile_registry_test.go:212 [It] /go/odo_1/tests/integration/cmd_devfile_registry_test.go:240 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38003" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_registry_test.go:214 @ 12/01/23 10:29:24.364 ------------------------------ • [69.031 seconds] odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var-file flag and setting value in env should check if the env variable has a correct value /go/odo_1/tests/integration/cmd_dev_test.go:1668 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38473" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [71.930 seconds] odo dev command tests when Devfile contains metadata.language invalid as a label value when running odo dev should set the correct value in labels of resources /go/odo_1/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42863" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [35.204 seconds] odo dev command tests when a component is bootstrapped should start on cluster even if Podman client takes long to initialize /go/odo_1/tests/integration/cmd_dev_test.go:91 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39329" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [29.768 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37411" << Captured StdOut/StdErr Output ------------------------------ • [58.769 seconds] odo dev command tests when running applications listening on the container loopback interface when running on default cluster platform should port-forward successfully /go/odo_1/tests/integration/cmd_dev_test.go:4244 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41965" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.188 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should describe the API Server port (JSON) /go/odo_1/tests/integration/cmd_dev_api_server_test.go:123 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40425" << Captured StdOut/StdErr Output ------------------------------ • [48.799 seconds] odo dev command tests when running odo dev --no-watch and build command throws an error should error out with some log /go/odo_1/tests/integration/cmd_dev_test.go:2898 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46229" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [62.231 seconds] odo dev command tests when running odo dev and composite command is marked as parallel:true - with metadata.name should execute all commands in composite command /go/odo_1/tests/integration/cmd_dev_test.go:2642 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40699" << Captured StdOut/StdErr Output ------------------------------ • [26.831 seconds] odo devfile deploy command tests deploying devfile with exec when using devfile where the exec command is bound to fail should print the last 100 lines of the log to the output /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:648 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46429" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [63.088 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39269" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.766 seconds] odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy should succeed /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43275" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [63.466 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34373" << Captured StdOut/StdErr Output ------------------------------ • [51.072 seconds] odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands when a file in component directory is modified should not trigger a push /go/odo_1/tests/integration/cmd_dev_test.go:736 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38875" << Captured StdOut/StdErr Output ------------------------------ • [73.870 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:363 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44719" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [7.442 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 >> Using Devfile Registry URL at: "http://127.0.0.1:35117" Spawning '/go/bin/odo deploy' from /tmp/664183648 << Captured StdOut/StdErr Output ------------------------------ • [5.543 seconds] odo dev command tests when running applications listening on the container loopback interface should error out if using --ignore-localhost on any platform other than Podman /go/odo_1/tests/integration/cmd_dev_test.go:4211 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43141" << Captured StdOut/StdErr Output ------------------------------ • [88.424 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=false, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38121" << Captured StdOut/StdErr Output ------------------------------ • [6.678 seconds] odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together /go/odo_1/tests/integration/cmd_dev_test.go:233 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42239" << Captured StdOut/StdErr Output ------------------------------ • [119.679 seconds] odo dev command tests when running odo dev with devfile contain volume - with metadata.name should create pvc and reuse if it shares the same devfile volume name /go/odo_1/tests/integration/cmd_dev_test.go:2197 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44717" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.665 seconds] odo create/delete/list/set namespace/project tests create namespace should successfully create the namespace /go/odo_1/tests/integration/cmd_namespace_test.go:54 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34169" << Captured StdOut/StdErr Output ------------------------------ • [9.904 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32953" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [79.469 seconds] odo dev debug command tests when running build and debug commands as composite in different containers and a shared volume - without metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34917" << Captured StdOut/StdErr Output ------------------------------ • [5.746 seconds] odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together /go/odo_1/tests/integration/cmd_dev_test.go:233 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33701" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [58.079 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should describe the API Server port /go/odo_1/tests/integration/cmd_dev_api_server_test.go:108 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42075" << Captured StdOut/StdErr Output ------------------------------ • [5.316 seconds] odo create/delete/list/set namespace/project tests set namespace should not succeed to set the namespace /go/odo_1/tests/integration/cmd_namespace_test.go:162 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43407" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [85.222 seconds] odo dev command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components not referenced in the Devfile should create the appropriate resources /go/odo_1/tests/integration/cmd_dev_test.go:4466 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33807" << Captured StdOut/StdErr Output ------------------------------ • [120.577 seconds] odo dev debug command tests when creating nodejs component, doing odo dev and run command has dev.odo.push.path attribute should sync only the mentioned files at the appropriate remote destination /go/odo_1/tests/integration/cmd_dev_debug_test.go:163 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40815" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [80.923 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=true, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39745" << Captured StdOut/StdErr Output ------------------------------ • [62.311 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=false, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35463" << Captured StdOut/StdErr Output ------------------------------ • [80.487 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=true, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44013" << Captured StdOut/StdErr Output ------------------------------ • [122.008 seconds] odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy when running and stopping odo dev should not delete the resources created with odo deploy /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43291" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [7.690 seconds] odo create/delete/list/set namespace/project tests delete project should not succeed to delete a non-existent project /go/odo_1/tests/integration/cmd_namespace_test.go:122 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34959" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [9.288 seconds] odo create/delete/list/set namespace/project tests set project should not succeed to set the project /go/odo_1/tests/integration/cmd_namespace_test.go:162 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33203" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [25.757 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should error out on an invalid command /go/odo_1/tests/integration/cmd_dev_test.go:3150 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37019" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [11.676 seconds] odo list with devfile listing non-odo managed components when a non-odo managed component is deployed should list the component with odo list /go/odo_1/tests/integration/cmd_devfile_list_test.go:43 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40525" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [32.348 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35843" << Captured StdOut/StdErr Output ------------------------------ • [12.455 seconds] odo list with devfile listing non-odo managed components when a non-odo managed component without the managed-by label is deployed should list the component in JSON /go/odo_1/tests/integration/cmd_devfile_list_test.go:71 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36345" << Captured StdOut/StdErr Output ------------------------------ • [7.763 seconds] odo dev command with api server tests when the component is bootstrapped should fail if --api-server is false but --api-server-port is true /go/odo_1/tests/integration/cmd_dev_api_server_test.go:46 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33819" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [7.296 seconds] odo logs command tests when directory is empty should error /go/odo_1/tests/integration/cmd_logs_test.go:86 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43963" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [10.075 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38157" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [79.477 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=false, customPortForwarding=false, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37095" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [57.759 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should execute the default build command successfully if specified explicitly /go/odo_1/tests/integration/cmd_dev_test.go:3126 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41205" << Captured StdOut/StdErr Output ------------------------------ • [6.636 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=false) /go/odo_1/tests/integration/cmd_devfile_build_images_test.go:437 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37621" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [58.655 seconds] odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev with --var flag should check if the env variable has a correct value /go/odo_1/tests/integration/cmd_dev_test.go:1612 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40193" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.541 seconds] odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) Default output when switching to another directory when describing the component from another directory should describe the named component /go/odo_1/tests/integration/cmd_describe_component_test.go:414 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40711" << Captured StdOut/StdErr Output ------------------------------ • [99.415 seconds] odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when stopping odo dev normally should have deleted all resources before returning /go/odo_1/tests/integration/cmd_dev_test.go:629 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41571" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [26.572 seconds] odo dev command tests when a component is bootstrapped when an env.yaml file contains a non-current Project when odo dev is executed should not have modified env.yaml, and use current namespace /go/odo_1/tests/integration/cmd_dev_test.go:547 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42033" << Captured StdOut/StdErr Output ------------------------------ • [64.148 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name should execute the custom non-default build and run commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:3207 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45779" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.679 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=true, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41557" << Captured StdOut/StdErr Output ------------------------------ S [4.286 seconds] odo devfile init command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should be able to download devfile from the in-cluster registry [BeforeEach] /go/odo_1/tests/integration/cmd_devfile_init_test.go:580 [It] /go/odo_1/tests/integration/cmd_devfile_init_test.go:607 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37963" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_init_test.go:582 @ 12/01/23 10:31:52.596 ------------------------------ • [7.667 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45741" << Captured StdOut/StdErr Output ------------------------------ • [8.765 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:237 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36511" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [7.272 seconds] odo describe component command tests when creating a component should not describe the component from another directory, with default cluster mode /go/odo_1/tests/integration/cmd_describe_component_test.go:289 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36921" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS ------------------------------ • [59.999 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=true, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39681" << Captured StdOut/StdErr Output ------------------------------ • [9.105 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=dev should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41723" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [6.425 seconds] odo preference and config command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace should fail to delete the in-cluster registry [BeforeEach] /go/odo_1/tests/integration/cmd_pref_config_test.go:377 [It] /go/odo_1/tests/integration/cmd_pref_config_test.go:444 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33217" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:379 @ 12/01/23 10:32:05.905 ------------------------------ • [29.153 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44101" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.817 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should execute the default run command successfully if specified explicitly /go/odo_1/tests/integration/cmd_dev_test.go:3195 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42951" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [59.936 seconds] odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) JSON output when describing the component in dev mode should describe the component /go/odo_1/tests/integration/cmd_describe_component_test.go:441 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42795" << Captured StdOut/StdErr Output ------------------------------ • [7.705 seconds] odo devfile deploy command tests Devfile with autoBuild or deployByDefault components when starting with Devfile with Deploy commands when running odo deploy with some components referenced in the Devfile should create the appropriate resources /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:802 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33953" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [46.967 seconds] odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=a-command-not-found-for-podman-should-make-odo-fallback-to-docker DOCKER_CMD=echo] remote server returns an error when odo dev is run should not build images when odo dev is run /go/odo_1/tests/integration/cmd_dev_test.go:2549 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46733" << Captured StdOut/StdErr Output ------------------------------ • [119.115 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy when running and stopping odo dev should not delete the resources created with odo deploy /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43453" << Captured StdOut/StdErr Output ------------------------------ • [61.118 seconds] odo dev command tests when project and clonePath is present in devfile and running odo dev - without metadata.name should sync to the correct dir in container /go/odo_1/tests/integration/cmd_dev_test.go:2058 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46719" << Captured StdOut/StdErr Output ------------------------------ • [82.959 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 >> Using Devfile Registry URL at: "http://127.0.0.1:36815" Spawning '/go/bin/odo dev --random-ports' from /tmp/2722634886 << Captured StdOut/StdErr Output ------------------------------ • [59.688 seconds] odo dev command tests when setting git config and running odo dev should create vcs-uri annotation for the deployment when running odo dev /go/odo_1/tests/integration/cmd_dev_test.go:2966 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40277" << Captured StdOut/StdErr Output ------------------------------ • [9.977 seconds] odo delete command tests when running odo deploy for an exec command bound to fail should print the job in the list of resources to be deleted with named delete command /go/odo_1/tests/integration/cmd_delete_test.go:546 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43701" << Captured StdOut/StdErr Output ------------------------------ • [118.553 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy with image build extra args when running and stopping odo dev should not delete the resources created with odo deploy /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35637" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [51.265 seconds] odo devfile deploy command tests deploying devfile with exec when the deploy command terminates abruptly; component name of a normal character length when odo deploy command is run again should run successfully /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:595 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46181" << Captured StdOut/StdErr Output ------------------------------ • [6.871 seconds] odo dev command tests when a component is bootstrapped when a state file is not writable should fail running odo dev /go/odo_1/tests/integration/cmd_dev_test.go:435 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44431" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [59.850 seconds] odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) Default output when describing the component in dev mode should describe the component /go/odo_1/tests/integration/cmd_describe_component_test.go:373 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36953" << Captured StdOut/StdErr Output ------------------------------ • [4.722 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when an env.yaml file contains a non-current Project when running odo deploy should succeed /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:201 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39299" << Captured StdOut/StdErr Output ------------------------------ • [111.075 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=false, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43913" << Captured StdOut/StdErr Output ------------------------------ • [120.819 seconds] odo list with devfile when a component created in 'app' application when dev is running on cluster verifying the managedBy Version in the odo list output should show managedBy Version /go/odo_1/tests/integration/cmd_devfile_list_test.go:181 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33135" << Captured StdOut/StdErr Output ------------------------------ • [47.547 seconds] odo dev command tests when a component is bootstrapped when build command takes really long to start should cancel build command and return if odo dev is stopped /go/odo_1/tests/integration/cmd_dev_test.go:981 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32941" << Captured StdOut/StdErr Output ------------------------------ • [80.521 seconds] odo dev command tests when devfile has sourcemappings and running odo dev - with metadata.name should sync files to the correct location /go/odo_1/tests/integration/cmd_dev_test.go:2016 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45775" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.994 seconds] odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag should not add a DEBUG_PORT variable to the container /go/odo_1/tests/integration/cmd_dev_debug_test.go:124 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44973" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [130.632 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:3324 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43953" << Captured StdOut/StdErr Output ------------------------------ • [6.187 seconds] odo generic executing odo version command when executing the complete command with server info should show the version of odo major components including server login URL /go/odo_1/tests/integration/generic_test.go:132 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46723" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [82.215 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 >> Using Devfile Registry URL at: "http://127.0.0.1:34735" Spawning '/go/bin/odo dev --random-ports -v 4' from /tmp/4045646524 << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [88.514 seconds] odo dev command tests when a component with endpoints is bootstrapped and pushed should not create Ingress or Route resources in the cluster /go/odo_1/tests/integration/cmd_dev_test.go:3463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39269" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [85.491 seconds] odo dev command tests 1. devfile contains composite apply command when odo dev is running with image build extra args should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41523" << Captured StdOut/StdErr Output ------------------------------ • [6.053 seconds] odo generic executing odo version command should only print client info when using --client flag /go/odo_1/tests/integration/generic_test.go:201 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41413" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [89.760 seconds] odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when killing odo dev and running odo delete component --wait should have deleted all resources before returning /go/odo_1/tests/integration/cmd_dev_test.go:577 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39073" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [78.470 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=true, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43123" << Captured StdOut/StdErr Output ------------------------------ • [64.198 seconds] odo run command tests when a component is bootstrapped when odo dev is executed with --no-commands=false and ready should execute commands /go/odo_1/tests/integration/cmd_run_test.go:100 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40707" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.924 seconds] odo dev command tests when project and clonePath is present in devfile and running odo dev - with metadata.name should sync to the correct dir in container /go/odo_1/tests/integration/cmd_dev_test.go:2058 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43359" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ S [4.171 seconds] odo dev command tests when a component is bootstrapped when pod security is enforced as restricted [It] should set securitycontext for podsecurity admission /go/odo_1/tests/integration/cmd_dev_test.go:414 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38489" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: /go/odo_1/tests/integration/cmd_dev_test.go:416 @ 12/01/23 10:34:03.532 ------------------------------ SS ------------------------------ • [5.153 seconds] odo create/delete/list/set namespace/project tests set project when running inside a component directory should set the project /go/odo_1/tests/integration/cmd_namespace_test.go:190 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45929" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [120.412 seconds] odo dev command tests when running odo dev and single env var is set - without metadata.name should be able to exec command /go/odo_1/tests/integration/cmd_dev_test.go:1691 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40455" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.599 seconds] odo dev command tests when a component is bootstrapped should add annotation to use ImageStreams /go/odo_1/tests/integration/cmd_dev_test.go:147 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32773" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [58.680 seconds] odo dev command tests when a component with multiple endpoints is run when odo dev is stopped should remove forwarded ports from state file /go/odo_1/tests/integration/cmd_dev_test.go:3583 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33435" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [139.552 seconds] odo dev command tests when running odo dev with devfile containing volume-component - without metadata.name should successfully use the volume components in container components /go/odo_1/tests/integration/cmd_dev_test.go:2278 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35507" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.194 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a run command should execute the custom non-default run command successfully /go/odo_1/tests/integration/cmd_dev_test.go:3181 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45807" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.821 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34441" << Captured StdOut/StdErr Output ------------------------------ • [6.061 seconds] odo devfile init command tests setting application ports when running odo init --run-port with a Devfile with no commands should ignore the run ports /go/odo_1/tests/integration/cmd_devfile_init_test.go:622 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38995" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.447 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in=deploy should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39069" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.415 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42737" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [27.763 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34285" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSS ------------------------------ • [8.108 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in= should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42579" << Captured StdOut/StdErr Output ------------------------------ • [59.351 seconds] odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should execute the default build command successfully if specified explicitly /go/odo_1/tests/integration/cmd_dev_test.go:3126 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38647" << Captured StdOut/StdErr Output ------------------------------ • [5.908 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=true) /go/odo_1/tests/integration/cmd_devfile_build_images_test.go:445 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36411" << Captured StdOut/StdErr Output ------------------------------ • [7.609 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44637" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [63.132 seconds] odo dev command tests when no project is present - without metadata.name should sync to the correct dir in container /go/odo_1/tests/integration/cmd_dev_test.go:2164 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32957" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ • [61.644 seconds] odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and with --no-commands when a file in component directory is modified when p is pressed should trigger a push /go/odo_1/tests/integration/cmd_dev_test.go:754 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36591" << Captured StdOut/StdErr Output ------------------------------ • [7.392 seconds] odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together /go/odo_1/tests/integration/cmd_dev_test.go:233 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35941" << Captured StdOut/StdErr Output ------------------------------ • [28.825 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46721" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [88.989 seconds] odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false when killing odo dev and another process replaces it should restart a new session successfully /go/odo_1/tests/integration/cmd_dev_test.go:609 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38997" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [68.431 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag when /component/command endpoint is POSTed should trigger a push /go/odo_1/tests/integration/cmd_dev_api_server_test.go:221 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37591" << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #6 Automatically polling progress: odo dev command tests Devfile contains pod-overrides and container-overrides attributes should override the content in the pod it creates for the component on the cluster (Spec Runtime: 2m4.392s) /go/odo_1/tests/integration/cmd_dev_test.go:4146 In [It] (Node Runtime: 2m0s) /go/odo_1/tests/integration/cmd_dev_test.go:4146 Begin Captured GinkgoWriter Output >> ... [odo] ✗ Finished executing the application (command: run) [1m] [odo] I1201 10:34:39.120181 37173 execute_run.go:36] error while running background command: unable to exec command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_run.pid && cd ${PROJECT_SOURCE} && (npm start) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_run.pid]: error while streaming command: context canceled [odo] I1201 10:34:39.134863 37173 implem.go:114] The path for preference file is /tmp/4240247907/preference.yaml [odo] I1201 10:34:39.135726 37173 segment.go:268] Checking telemetry enable status [odo] I1201 10:34:39.135749 37173 segment.go:286] Sending telemetry disabled by env variable [odo] Cleaning resources, please wait [odo] I1201 10:34:39.195897 37173 all.go:46] starting to concurrently query 201 APIs [odo] I1201 10:34:39.196050 37173 all.go:62] fired up all goroutines to query APIs [odo] I1201 10:34:39.990543 37173 all.go:67] all goroutines have returned in 794.649535ms [odo] I1201 10:34:39.990578 37173 all.go:76] query result: objects=632 << End Captured GinkgoWriter Output Spec Goroutine goroutine 705 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0003ca8c0, {0x314bfb8?, 0xc000693638}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0003ca8c0, {0x314bfb8, 0xc000693638}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc000c61d50?, {0xc00171d520?, 0x2d3fd5a?, 0x9?}) /go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) /go/odo_1/tests/helper/helper_dev.go:263 github.com/redhat-developer/odo/tests/helper.RunDevMode.func1() /go/odo_1/tests/helper/helper_dev.go:334 github.com/redhat-developer/odo/tests/helper.RunDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...}, ...) /go/odo_1/tests/helper/helper_dev.go:337 > github.com/redhat-developer/odo/tests/integration.glob..func7.64.2() /go/odo_1/tests/integration/cmd_dev_test.go:4147 | }) | It("should override the content in the pod it creates for the component on the cluster", func() { > err := helper.RunDevMode(helper.DevSessionOpts{ | RunOnPodman: ctx.podman, | }, func(session *gexec.Session, outContents, _ string, _ map[string]string) { github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x10a6e7e, 0xc0010c4ba0}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ • [6.723 seconds] odo describe component command tests should fail, with default cluster mode /go/odo_1/tests/integration/cmd_describe_component_test.go:70 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35523" << Captured StdOut/StdErr Output ------------------------------ • [130.348 seconds] odo dev command tests Devfile contains pod-overrides and container-overrides attributes should override the content in the pod it creates for the component on the cluster /go/odo_1/tests/integration/cmd_dev_test.go:4146 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33339" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [31.905 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40745" << Captured StdOut/StdErr Output ------------------------------ • [132.418 seconds] odo dev command tests when running build and run commands as composite in different containers and a shared volume - with metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_test.go:2772 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38791" << Captured StdOut/StdErr Output ------------------------------ • [59.759 seconds] odo dev command tests when creating local files and dir and running odo dev - with metadata.name should correctly propagate changes to the container /go/odo_1/tests/integration/cmd_dev_test.go:1788 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37175" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [93.302 seconds] odo logs command tests when component is created and odo logs is executed when logs --follow is started when running in Dev mode should successfully follow logs of running component /go/odo_1/tests/integration/cmd_logs_test.go:219 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44837" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [120.349 seconds] odo dev command tests when node-js application is created and deployed with devfile schema 2.2.0 should check memory Request and Limit /go/odo_1/tests/integration/cmd_dev_test.go:3375 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38577" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [7.811 seconds] odo dev command tests when directory is empty should error /go/odo_1/tests/integration/cmd_dev_test.go:64 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39483" << Captured StdOut/StdErr Output ------------------------------ • [80.771 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/baz.txt file should synchronize it only /go/odo_1/tests/integration/cmd_dev_test.go:1965 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33489" << Captured StdOut/StdErr Output ------------------------------ • [60.719 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=false, customPortForwarding=true, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44515" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.733 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36727" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [68.925 seconds] odo devfile deploy command tests deploying devfile with long-running exec when Automount volumes are present in the namespace should mount the volumes /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:695 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40599" << Captured StdOut/StdErr Output ------------------------------ • [9.650 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43633" << Captured StdOut/StdErr Output ------------------------------ • [61.525 seconds] odo dev command tests when running odo dev and devfile with composite command - with metadata.name should execute all commands in composite command /go/odo_1/tests/integration/cmd_dev_test.go:2610 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34623" << Captured StdOut/StdErr Output ------------------------------ • [5.272 seconds] odo devfile deploy command tests when using a devfile.yaml containing an Image component with a build context should build image via Docker if build context references PROJECT_SOURCE env var /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:326 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33105" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [47.118 seconds] odo logs command tests when component is created and odo logs is executed when running in Deploy mode when --follow flag is specified should successfully follow logs of running component /go/odo_1/tests/integration/cmd_logs_test.go:291 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41401" << Captured StdOut/StdErr Output ------------------------------ • [60.611 seconds] odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var-file flag and setting value in env should check if the env variable has a correct value /go/odo_1/tests/integration/cmd_dev_test.go:1668 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36519" << Captured StdOut/StdErr Output ------------------------------ SSS• ------------------------------ • [81.038 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=true, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46499" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [127.450 seconds] odo list with devfile when a component created in 'app' application when dev is running on cluster should display platform /go/odo_1/tests/integration/cmd_devfile_list_test.go:150 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36681" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.496 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:3622 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39191" PID: 42326 << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [8.750 seconds] odo devfile deploy command tests when recording telemetry data should record the telemetry data correctly /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39081" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [31.619 seconds] odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=true should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:517 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34731" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ S [6.161 seconds] odo preference and config command tests when DevfileRegistriesList CRD is installed on cluster [BeforeEach] when CR for devfileregistrieslists is installed in namespace registry list should return registry listed in CR [BeforeEach] /go/odo_1/tests/integration/cmd_pref_config_test.go:377 [It] /go/odo_1/tests/integration/cmd_pref_config_test.go:414 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46473" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: /go/odo_1/tests/integration/cmd_pref_config_test.go:379 @ 12/01/23 10:36:35.633 ------------------------------ SSSSS ------------------------------ • [11.993 seconds] odo describe component command tests when creating a component when running odo deploy to create ingress/routes should show the ingress with defaultBackend in odo describe component output /go/odo_1/tests/integration/cmd_describe_component_test.go:577 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43319" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [61.864 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44245" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [29.447 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45975" << Captured StdOut/StdErr Output ------------------------------ • [170.170 seconds] odo dev command tests when a component is bootstrapped when Automount volumes are present in the namespace when odo dev is executed should mount the volumes /go/odo_1/tests/integration/cmd_dev_test.go:833 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43341" << Captured StdOut/StdErr Output ------------------------------ • [131.142 seconds] odo dev command tests when running odo dev and composite command is used as a run command - with metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_test.go:2709 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46835" << Captured StdOut/StdErr Output ------------------------------ • [63.540 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34367" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [30.389 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37469" << Captured StdOut/StdErr Output ------------------------------ • [74.461 seconds] odo dev debug command tests when a composite command is used as debug command - with metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:225 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36759" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [118.833 seconds] odo dev command tests when a devfile with a local parent is used for odo dev and the parent is not synced when updating the parent should update the component /go/odo_1/tests/integration/cmd_dev_test.go:3697 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37375" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [4.147 seconds] odo devfile deploy command tests when deploying a ServiceBinding k8s resource [BeforeEach] when odo deploy is run should successfully deploy the ServiceBinding resource [BeforeEach] /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:387 [It] /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:412 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36301" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:390 @ 12/01/23 10:37:12.418 ------------------------------ S ------------------------------ • [53.505 seconds] odo devfile deploy command tests deploying devfile with exec when the deploy command terminates abruptly; component name of at max(63) characters length when odo deploy command is run again should run successfully /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:595 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45139" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [149.381 seconds] odo dev command tests when running odo dev with devfile containing volume-component - with metadata.name should successfully use the volume components in container components /go/odo_1/tests/integration/cmd_dev_test.go:2278 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37315" << Captured StdOut/StdErr Output ------------------------------ • [26.813 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34361" << Captured StdOut/StdErr Output ------------------------------ • [60.491 seconds] odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) JSON output when switching to another directory when describing the component from another directory should describe the named component /go/odo_1/tests/integration/cmd_describe_component_test.go:502 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35225" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [70.008 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /testdir/foobar.txt file should not synchronize it /go/odo_1/tests/integration/cmd_dev_test.go:1987 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44953" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [13.846 seconds] odo devfile deploy command tests deploying devfile with exec when using devfile that works; with component name of a normal character length should complete the command execution successfully /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:576 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33297" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [8.123 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:241 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38665" << Captured StdOut/StdErr Output ------------------------------ • [92.385 seconds] odo logs command tests when component is created and odo logs is executed when running in Dev mode should successfully show logs of the running component /go/odo_1/tests/integration/cmd_logs_test.go:140 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35083" << Captured StdOut/StdErr Output ------------------------------ • [5.288 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with default variable values (push=true) /go/odo_1/tests/integration/cmd_devfile_build_images_test.go:431 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38429" << Captured StdOut/StdErr Output ------------------------------ • [60.815 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34835" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [84.258 seconds] odo dev command tests 1. devfile contains composite apply command when odo dev is running with both image build and container run extra args should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39767" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [61.156 seconds] odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a run command should execute the custom non-default run command successfully /go/odo_1/tests/integration/cmd_dev_test.go:3181 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35221" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [4.895 seconds] odo create/delete/list/set namespace/project tests delete namespace should not succeed to delete a non-existent namespace /go/odo_1/tests/integration/cmd_namespace_test.go:122 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36849" << Captured StdOut/StdErr Output ------------------------------ • [61.011 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43333" << Captured StdOut/StdErr Output ------------------------------ • [77.989 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=false, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44443" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.222 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=true) should describe the API Server port /go/odo_1/tests/integration/cmd_dev_api_server_test.go:108 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36585" << Captured StdOut/StdErr Output ------------------------------ • [6.669 seconds] odo devfile deploy command tests when deploying a Devfile K8s component with multiple K8s resources defined should have created all the resources defined in the Devfile K8s component /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:372 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41651" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [142.098 seconds] odo dev command tests when running build and run commands as composite in different containers and a shared volume - without metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_test.go:2772 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37919" << Captured StdOut/StdErr Output ------------------------------ • [10.213 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in=dev should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40145" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [5.013 seconds] odo devfile deploy command tests when directory is empty should error /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:47 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35569" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [6.174 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when an env.yaml file contains a non-current Project when running odo deploy when the env.yaml file still contains a non-current Project should delete the component in the current namespace /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:226 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44919" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [58.105 seconds] odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev 3. should check if the env variable has a correct value /go/odo_1/tests/integration/cmd_dev_test.go:1589 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35125" << Captured StdOut/StdErr Output ------------------------------ • [9.978 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:241 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38053" << Captured StdOut/StdErr Output ------------------------------ • [58.712 seconds] odo dev command tests when Devfile contains metadata.projectType invalid as a label value when running odo dev should set the correct value in labels of resources /go/odo_1/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33783" << Captured StdOut/StdErr Output ------------------------------ • [79.645 seconds] odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and without --no-commands when a file in component directory is modified when p is pressed should trigger a push /go/odo_1/tests/integration/cmd_dev_test.go:754 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37037" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ • [17.166 seconds] odo create/delete/list/set namespace/project tests delete project when force-deleting a valid project should successfully delete the project synchronously with --wait /go/odo_1/tests/integration/cmd_namespace_test.go:115 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:32779" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [9.827 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46363" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [71.794 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /foobar.txt file should not synchronize it /go/odo_1/tests/integration/cmd_dev_test.go:1977 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43401" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [58.436 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=false, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38307" << Captured StdOut/StdErr Output ------------------------------ • [10.652 seconds] odo list with devfile listing non-odo managed components when a non-odo managed component is deployed should list the component in JSON /go/odo_1/tests/integration/cmd_devfile_list_test.go:47 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38389" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [63.082 seconds] odo dev command tests when no project is present - with metadata.name should sync to the correct dir in container /go/odo_1/tests/integration/cmd_dev_test.go:2164 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42701" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [9.717 seconds] odo devfile deploy command tests deploying devfile with exec when using a devfile name with length more than 63 should fail with invalid component name error /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:622 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40359" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS ------------------------------ • [113.004 seconds] odo logs command tests when component is created and odo logs is executed when running in Dev mode when --follow flag is specified should successfully follow logs of running component /go/odo_1/tests/integration/cmd_logs_test.go:172 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33933" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.399 seconds] odo dev command tests when running applications listening on the container loopback interface should error out if using --forward-localhost on any platform other than Podman /go/odo_1/tests/integration/cmd_dev_test.go:4220 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43281" << Captured StdOut/StdErr Output ------------------------------ • [10.512 seconds] odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should run odo deploy /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:538 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33671" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [5.695 seconds] odo run command tests when a component is bootstrapped should fail if odo dev is not running /go/odo_1/tests/integration/cmd_run_test.go:72 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42793" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.245 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=true --running-in= should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38791" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [58.041 seconds] odo dev command with api server tests when the component is bootstrapped when odo dev is run with --api-server flag (custom api server port=false) should describe the API Server port (JSON) /go/odo_1/tests/integration/cmd_dev_api_server_test.go:123 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44501" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [7.669 seconds] odo list with devfile listing non-odo managed components when an operator managed deployment(without instance and managed-by label) is deployed should not be listed in the odo list output /go/odo_1/tests/integration/cmd_devfile_list_test.go:88 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39277" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [60.267 seconds] odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var flag should check if the env variable has a correct value /go/odo_1/tests/integration/cmd_dev_test.go:1612 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40077" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [63.175 seconds] odo dev command tests when Devfile contains neither metadata.language nor metadata.projectType when running odo dev should set the correct value in labels of resources /go/odo_1/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43027" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [4.671 seconds] odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args should succeed /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:143 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36831" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [62.359 seconds] odo describe component command tests when creating a component when running odo dev (podman=false,debug=false) JSON output when switching to another directory when describing the component from another directory should describe the named component /go/odo_1/tests/integration/cmd_describe_component_test.go:502 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41481" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ S [5.223 seconds] odo dev command tests when Starting a PostgreSQL service [BeforeEach] when creating local files and dir and running odo dev - with metadata.name when deleting local files and dir and waiting for sync should not list deleted dir and file in container [BeforeEach] /go/odo_1/tests/integration/cmd_dev_test.go:1815 [It] /go/odo_1/tests/integration/cmd_dev_test.go:1882 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43311" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: /go/odo_1/tests/integration/cmd_dev_test.go:1818 @ 12/01/23 10:39:17.512 ------------------------------ • [57.179 seconds] odo dev command tests when a component is bootstrapped when running with --no-commands (debug=true) should start the dev session /go/odo_1/tests/integration/cmd_dev_test.go:268 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45859" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.038 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted while having access to the devfile.yaml should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41701" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [61.406 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:124 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36489" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [63.774 seconds] odo dev command tests when multiple projects are present - without metadata.name should sync to the correct dir in container /go/odo_1/tests/integration/cmd_dev_test.go:2130 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46207" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [61.764 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should execute the custom non-default build command successfully /go/odo_1/tests/integration/cmd_dev_test.go:3112 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46733" << Captured StdOut/StdErr Output ------------------------------ • [15.672 seconds] odo create/delete/list/set namespace/project tests delete namespace when force-deleting a valid namespace should successfully delete the namespace synchronously with --wait /go/odo_1/tests/integration/cmd_namespace_test.go:115 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45937" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ Progress Report for Ginkgo Process #1 Automatically polling progress: odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully (Spec Runtime: 3m33.003s) /go/odo_1/tests/integration/cmd_dev_debug_test.go:288 In [It] (Node Runtime: 2m0s) /go/odo_1/tests/integration/cmd_dev_debug_test.go:288 At [By Step] cleaning up the resources on ending the session (Step Runtime: 26.762s) /go/odo_1/tests/integration/cmd_dev_debug_test.go:326 Begin Captured GinkgoWriter Output >> ... [odo] stderr: [] [odo] I1201 10:39:20.016523 43883 execute_run.go:36] error while running background command: unable to exec command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_start-debug.pid && cd /projects && (npm run debug) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_start-debug.pid]: error while streaming command: context canceled [odo] I1201 10:39:20.016785 43883 implem.go:114] The path for preference file is /tmp/2949761456/preference.yaml [odo] I1201 10:39:20.017933 43883 segment.go:268] Checking telemetry enable status [odo] I1201 10:39:20.017965 43883 segment.go:286] Sending telemetry disabled by env variable [odo] Cleaning resources, please wait [odo] I1201 10:39:20.093587 43883 all.go:46] starting to concurrently query 201 APIs [odo] I1201 10:39:20.093871 43883 all.go:62] fired up all goroutines to query APIs [odo] I1201 10:39:20.913931 43883 all.go:67] all goroutines have returned in 820.343037ms [odo] I1201 10:39:20.914006 43883 all.go:76] query result: objects=669 << End Captured GinkgoWriter Output Spec Goroutine goroutine 1172 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000244000, {0x314bfb8?, 0xc0004ba288}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000244000, {0x314bfb8, 0xc0004ba288}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc0003e4900?, {0xc00173c060?, 0x0?, 0x0?}) /go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) /go/odo_1/tests/helper/helper_dev.go:263 > github.com/redhat-developer/odo/tests/integration.glob..func6.7.2.8() /go/odo_1/tests/integration/cmd_dev_debug_test.go:328 | By("cleaning up the resources on ending the session", func() { | devSession.Stop() > devSession.WaitEnd() | out := commonVar.CliRunner.Run("get", "deployments").Out.Contents() | helper.DontMatchAllInOutput(string(out), deploymentNames) github.com/onsi/ginkgo/v2/internal.(*Suite).By(0xc0001b0000, {0x2d9e5c8, 0x2f}, {0xc0009b1e70, 0x1, 0x0?}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:309 github.com/onsi/ginkgo/v2.By({0x2d9e5c8?, 0x0?}, {0xc0009b1e70?, 0x0?, 0x0?}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/core_dsl.go:547 > github.com/redhat-developer/odo/tests/integration.glob..func6.7.2() /go/odo_1/tests/integration/cmd_dev_debug_test.go:326 | }) | > By("cleaning up the resources on ending the session", func() { | devSession.Stop() | devSession.WaitEnd() github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x10a6e7e, 0xc0016415c0}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ • [5.991 seconds] odo create/delete/list/set namespace/project tests list project should successfully list all the projects /go/odo_1/tests/integration/cmd_namespace_test.go:221 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36403" << Captured StdOut/StdErr Output ------------------------------ • [118.894 seconds] odo describe component command tests checking for remote source code location when using devfile with sourceMapping and starting an odo dev session should show remote source code location in odo describe component output /go/odo_1/tests/integration/cmd_describe_component_test.go:667 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36535" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [225.696 seconds] odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:288 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46507" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [67.432 seconds] odo dev command tests when Devfile 2.1.0 is used - with metadata.name when doing odo dev with --var-file flag should check if the env variable has a correct value /go/odo_1/tests/integration/cmd_dev_test.go:1639 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38385" << Captured StdOut/StdErr Output ------------------------------ • [16.360 seconds] odo create/delete/list/set namespace/project tests delete project when force-deleting a valid project should successfully delete the project asynchronously /go/odo_1/tests/integration/cmd_namespace_test.go:107 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44955" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [4.853 seconds] odo devfile deploy command tests when using a devfile.yaml containing an Image component with no build context should build image via Docker by defaulting build context to devfile path /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:450 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35069" << Captured StdOut/StdErr Output ------------------------------ • [59.983 seconds] odo describe component command tests when creating a component when running odo dev (podman=false,debug=true) Default output when switching to another directory when describing the component from another directory should describe the named component /go/odo_1/tests/integration/cmd_describe_component_test.go:414 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35537" << Captured StdOut/StdErr Output ------------------------------ • [67.818 seconds] odo dev command tests when Devfile 2.1.0 is used - without metadata.name when doing odo dev 3. should check if the env variable has a correct value /go/odo_1/tests/integration/cmd_dev_test.go:1589 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40851" << Captured StdOut/StdErr Output ------------------------------ • [4.814 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=false) /go/odo_1/tests/integration/cmd_devfile_build_images_test.go:445 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40341" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [58.793 seconds] odo dev command tests when running odo dev and composite command is marked as parallel:true - without metadata.name should execute all commands in composite command /go/odo_1/tests/integration/cmd_dev_test.go:2642 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36293" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [5.612 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=true) /go/odo_1/tests/integration/cmd_devfile_build_images_test.go:437 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40219" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [5.861 seconds] odo devfile deploy command tests when using a devfile.yaml containing an Image component with no build context should build image via Podman by defaulting build context to devfile path /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:450 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37189" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [110.835 seconds] odo dev command tests when hotReload capable Build and Run commands are used with odo dev when a source file is modified should not re-execute the run command /go/odo_1/tests/integration/cmd_dev_test.go:3834 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34129" << Captured StdOut/StdErr Output ------------------------------ S [5.405 seconds] odo devfile deploy command tests deploying devfile with exec [It] should not set securitycontext for podsecurity admission on job's pod template /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:601 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34449" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:603 @ 12/01/23 10:40:31.212 ------------------------------ • [62.250 seconds] odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container /go/odo_1/tests/integration/cmd_dev_test.go:1955 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34139" << Captured StdOut/StdErr Output ------------------------------ • [120.413 seconds] odo dev command tests when a hotReload capable Run command is used with odo dev should execute the build and run commands /go/odo_1/tests/integration/cmd_dev_test.go:3771 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39233" << Captured StdOut/StdErr Output ------------------------------ • [120.024 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=true, customPortForwarding=true, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46079" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [88.773 seconds] odo dev command tests 1. devfile contains composite apply command when odo dev is running should execute the composite apply commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36559" << Captured StdOut/StdErr Output ------------------------------ • [120.800 seconds] odo dev command tests when doing odo dev and there is a env variable with spaces - with metadata.name should be able to exec command /go/odo_1/tests/integration/cmd_dev_test.go:1743 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34103" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [85.811 seconds] odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy should run odo dev successfully /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37361" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [7.378 seconds] odo create/delete/list/set namespace/project tests create namespace should fail to create namespace /go/odo_1/tests/integration/cmd_namespace_test.go:63 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36343" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [7.208 seconds] odo describe component command tests when creating a component when running odo deploy to create ingress/routes should show the ingress/routes in odo describe component output /go/odo_1/tests/integration/cmd_describe_component_test.go:577 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33801" << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #14 Automatically polling progress: odo dev command tests when a component is bootstrapped ensure that index information is updated (Spec Runtime: 2m4.489s) /go/odo_1/tests/integration/cmd_dev_test.go:305 In [It] (Node Runtime: 2m0.001s) /go/odo_1/tests/integration/cmd_dev_test.go:305 Begin Captured GinkgoWriter Output >> ... [odo] I1201 10:40:56.127056 49514 watch.go:271] deployment watcher Event: Type: MODIFIED, name: zpzgma-app, rv: 119131376, generation: 1, pods: 1 [odo] I1201 10:40:56.127146 49514 watch.go:333] Dev mode interrupted by user [odo] I1201 10:40:56.135123 49514 implem.go:114] The path for preference file is /tmp/4023122489/preference.yaml [odo] I1201 10:40:56.136610 49514 segment.go:268] Checking telemetry enable status [odo] I1201 10:40:56.136622 49514 segment.go:286] Sending telemetry disabled by env variable [odo] Cleaning resources, please wait [odo] I1201 10:40:56.308918 49514 all.go:46] starting to concurrently query 201 APIs [odo] I1201 10:40:56.309120 49514 all.go:62] fired up all goroutines to query APIs [odo] I1201 10:40:57.242834 49514 all.go:67] all goroutines have returned in 934.195065ms [odo] I1201 10:40:57.242953 49514 all.go:76] query result: objects=627 << End Captured GinkgoWriter Output Spec Goroutine goroutine 32609 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0014ce000, {0x314bfb8?, 0xc0007522b8}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0014ce000, {0x314bfb8, 0xc0007522b8}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc00091bdf8?, {0xc000788030?, 0xc0005e8920?, 0xc000470070?}) /go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) /go/odo_1/tests/helper/helper_dev.go:263 github.com/redhat-developer/odo/tests/helper.RunDevMode.func1() /go/odo_1/tests/helper/helper_dev.go:334 github.com/redhat-developer/odo/tests/helper.RunDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...}, ...) /go/odo_1/tests/helper/helper_dev.go:337 > github.com/redhat-developer/odo/tests/integration.glob..func7.4.14() /go/odo_1/tests/integration/cmd_dev_test.go:306 | | It("ensure that index information is updated", func() { > err := helper.RunDevMode(helper.DevSessionOpts{}, func(session *gexec.Session, outContents, errContents string, ports map[string]string) { | indexAfterPush, err := util.ReadFileIndex(filepath.Join(commonVar.Context, ".odo", "odo-file-index.json")) | Expect(err).ToNot(HaveOccurred()) github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x26c1b33, 0xc00006d980}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ • [61.635 seconds] odo dev command tests when a container component defines a Command or Args - with metadata.name should run odo dev successfully (#5620) /go/odo_1/tests/integration/cmd_dev_test.go:3538 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46347" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [5.805 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when a resource is changed in the devfile and the component is deleted while having access to the devfile.yaml with --files=false --running-in= should delete the component /go/odo_1/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42881" << Captured StdOut/StdErr Output ------------------------------ • [85.705 seconds] odo devfile deploy command tests when using a devfile.yaml containing an outer-loop Kubernetes component referenced via an URI when running odo deploy with image build extra args should run odo dev successfully /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46707" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [28.771 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="") should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36589" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [78.485 seconds] odo dev command tests when creating local files and dir and running odo dev - with metadata.name 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:1805 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41081" << Captured StdOut/StdErr Output ------------------------------ • [7.011 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEPLOY mode when the component is deleted using its name and namespace from another directory should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:237 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39041" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [110.640 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=true, customAddress=false) /go/odo_1/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34381" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [25.402 seconds] odo dev command tests when running odo dev with alternative commands - with metadata.name when running odo dev with a build command should error out on an invalid command /go/odo_1/tests/integration/cmd_dev_test.go:3080 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42371" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [151.442 seconds] odo dev command tests when a component is bootstrapped ensure that index information is updated /go/odo_1/tests/integration/cmd_dev_test.go:305 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37195" << Captured StdOut/StdErr Output ------------------------------ • [6.039 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 >> Using Devfile Registry URL at: "http://127.0.0.1:44543" Spawning '/go/bin/odo deploy' from /tmp/2175734550 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [67.608 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /foobar.txt file should not synchronize it /go/odo_1/tests/integration/cmd_dev_test.go:1977 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38015" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [91.419 seconds] odo logs command tests when component is created and odo logs is executed when running in Dev mode with --logs 1. should successfully show logs of the running component /go/odo_1/tests/integration/cmd_logs_test.go:249 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38891" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.277 seconds] odo create/delete/list/set namespace/project tests create project should successfully create the project /go/odo_1/tests/integration/cmd_namespace_test.go:54 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36447" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [88.476 seconds] odo dev command tests when hotReload capable Build and Run commands are used with odo dev should execute the build and run commands /go/odo_1/tests/integration/cmd_dev_test.go:3818 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45721" << Captured StdOut/StdErr Output ------------------------------ • [27.841 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="dev") when odo delete command is run again with nothing deployed on the cluster should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36179" << Captured StdOut/StdErr Output ------------------------------ • [4.878 seconds] odo dev command tests when a component is bootstrapped should fail when using --random-ports and --port-forward together /go/odo_1/tests/integration/cmd_dev_test.go:218 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46119" << Captured StdOut/StdErr Output ------------------------------ • [62.825 seconds] odo dev command tests 1. devfile contains composite apply command the devfile contains an image component that uses a remote Dockerfile when [PODMAN_CMD=echo] remote server returns a valid file when odo dev is run should build and push image when odo dev is run /go/odo_1/tests/integration/cmd_dev_test.go:2526 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43893" << Captured StdOut/StdErr Output ------------------------------ • [85.995 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should run odo dev successfully /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:161 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:33931" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [57.438 seconds] odo dev command tests when a component is bootstrapped when odo dev is executed when odo dev is stopped should delete the component from the platform /go/odo_1/tests/integration/cmd_dev_test.go:507 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37395" << Captured StdOut/StdErr Output ------------------------------ • [86.645 seconds] odo dev debug command tests when starting with Devfile with autoBuild or deployByDefault components when running odo dev with some components referenced in the Devfile should create the appropriate resources /go/odo_1/tests/integration/cmd_dev_debug_test.go:631 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:44553" << Captured StdOut/StdErr Output ------------------------------ • [5.440 seconds] odo devfile deploy command tests using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should run odo deploy /go/odo_1/tests/integration/cmd_devfile_deploy_test.go:538 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:39277" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS ------------------------------ Progress Report for Ginkgo Process #13 Automatically polling progress: odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource with apply command should have deleted the old resource and created the new resource (Spec Runtime: 2m4.891s) /go/odo_1/tests/integration/cmd_dev_test.go:1077 In [BeforeEach] (Node Runtime: 2m0.001s) /go/odo_1/tests/integration/cmd_dev_test.go:1050 Begin Captured GinkgoWriter Output >> ... [odo] I1201 10:42:03.864256 51554 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1201 10:42:03.868435 51554 port.go:319] port 8080 not listening in container "runtime" [odo] I1201 10:42:11.673751 51554 exec.go:37] Executing command [/bin/sh -c cat /proc/net/tcp /proc/net/udp /proc/net/tcp6 /proc/net/udp6 || true] for pod: wsklgj-app-57dc4b56d6-trj9t in container: runtime [odo] I1201 10:42:11.960134 51554 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1201 10:42:11.960170 51554 exec.go:96] 0: 8D2B11AC:B47E 23001068:01BB 06 00000000:00000000 03:00000BD9 00000000 0 0 0 3 0000000000000000 [odo] I1201 10:42:11.960177 51554 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1201 10:42:11.960190 51554 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1201 10:42:11.960195 51554 exec.go:96] 0: 00000000000000000000000000000000:0BB8 00000000000000000000000000000000:0000 0A 00000000:00000000 00:00000000 00000000 1031090000 0 209785762 1 0000000000000000 100 0 0 10 0 [odo] I1201 10:42:11.961232 51554 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1201 10:42:11.964022 51554 port.go:319] port 8080 not listening in container "runtime" << End Captured GinkgoWriter Output Spec Goroutine goroutine 1188 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00041c150, {0x314c1f8?, 0xc000984000}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00041c150, {0x314c1f8, 0xc000984000}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2d3df75, 0x8}, 0xc0004a4400?, 0xc0004a43e0?, 0xc000985b60) /go/odo_1/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc00049a960) /go/odo_1/tests/helper/helper_dev.go:279 > github.com/redhat-developer/odo/tests/integration.glob..func7.5.1.1() /go/odo_1/tests/integration/cmd_dev_test.go:1069 | helper.ReplaceStrings(filepath.Join(commonVar.Context, "devfile.yaml"), devfile.deploymentName, devfile.newDeploymentName) | > err := devSession.WaitSync() | Expect(err).To(BeNil()) | }) github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x10a6e7e, 0x26cab5d}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ • [60.538 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is deployed in DEV mode and dev mode stopped when the component is deleted using its name (and namespace) from another directory (running-in="deploy") should output that there are no resources to be deleted /go/odo_1/tests/integration/cmd_delete_test.go:124 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38037" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [8.472 seconds] odo describe component command tests when a non-odo application is present on the cluster should describe the component /go/odo_1/tests/integration/cmd_describe_component_test.go:719 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42831" << Captured StdOut/StdErr Output ------------------------------ • [61.796 seconds] odo dev command tests when running odo dev with alternative commands - with metadata.name should execute the custom non-default build and run commands successfully /go/odo_1/tests/integration/cmd_dev_test.go:3207 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40709" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [6.306 seconds] odo dev command tests when Devfile contains neither metadata.language nor metadata.projectType when odo deploy is executed should set the correct value in labels of deployed resources /go/odo_1/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46285" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ • [57.233 seconds] odo dev command tests port-forwarding for the component when devfile has no endpoint when running odo dev should have no endpoint forwarded (podman=false, manual=false) /go/odo_1/tests/integration/cmd_dev_test.go:1282 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42091" << Captured StdOut/StdErr Output ------------------------------ • [58.830 seconds] odo dev command tests when multiple projects are present - with metadata.name should sync to the correct dir in container /go/odo_1/tests/integration/cmd_dev_test.go:2130 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41687" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [60.057 seconds] odo delete command tests when a component is bootstrapped when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted using its name and namespace from another directory should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37119" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [124.546 seconds] odo list with devfile when a component created in 'app' application when dev is running on cluster show an odo deploy or dev in the list /go/odo_1/tests/integration/cmd_devfile_list_test.go:193 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40967" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [61.619 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38295" << Captured StdOut/StdErr Output ------------------------------ • [60.789 seconds] odo dev command tests port-forwarding for the component when devfile has no endpoint when running odo dev should have no endpoint forwarded (podman=false, manual=true) /go/odo_1/tests/integration/cmd_dev_test.go:1282 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41049" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ • [10.089 seconds] odo create/delete/list/set namespace/project tests set project should successfully set the project /go/odo_1/tests/integration/cmd_namespace_test.go:147 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:42565" << Captured StdOut/StdErr Output ------------------------------ • [62.047 seconds] odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container /go/odo_1/tests/integration/cmd_dev_test.go:1955 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34557" << Captured StdOut/StdErr Output ------------------------------ • [80.428 seconds] odo dev debug command tests when a composite command is used as debug command - without metadata.name should run successfully /go/odo_1/tests/integration/cmd_dev_debug_test.go:225 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43679" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ • [52.390 seconds] odo run command tests when a component is bootstrapped when odo dev is executed with --no-commands=true and ready should execute commands /go/odo_1/tests/integration/cmd_run_test.go:100 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40597" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [7.394 seconds] odo create/delete/list/set namespace/project tests set namespace should successfully set the namespace /go/odo_1/tests/integration/cmd_namespace_test.go:147 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:36975" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ • [63.544 seconds] odo dev command tests when creating nodejs component, doing odo dev and run command has dev.odo.push.path attribute should sync only the mentioned files at the appropriate remote destination /go/odo_1/tests/integration/cmd_dev_test.go:3428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37203" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [62.747 seconds] odo dev command tests when a component is bootstrapped when odo is executed with --no-watch flag and without --no-commands when a file in component directory is modified should not trigger a push /go/odo_1/tests/integration/cmd_dev_test.go:736 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:46201" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ • [58.384 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources /go/odo_1/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:45811" << Captured StdOut/StdErr Output ------------------------------ • [90.511 seconds] odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource without apply command should have deleted the old resource and created the new resource /go/odo_1/tests/integration/cmd_dev_test.go:1077 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40471" << Captured StdOut/StdErr Output ------------------------------ • [74.731 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:334 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41077" << Captured StdOut/StdErr Output ------------------------------ • [60.560 seconds] odo dev command tests when devfile project field is present and running odo dev - with metadata.name should sync to the correct dir in container /go/odo_1/tests/integration/cmd_dev_test.go:2097 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35797" << Captured StdOut/StdErr Output ------------------------------ • [36.285 seconds] odo dev command tests image names as selectors when starting with a Devfile with relative and absolute image names and Kubernetes resources when adding a local registry for images when running odo dev should treat relative image names as selectors /go/odo_1/tests/integration/cmd_dev_test.go:4756 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:35347" << Captured StdOut/StdErr Output ------------------------------ • [119.647 seconds] odo dev command tests when running odo dev and single env var is set - with metadata.name should be able to exec command /go/odo_1/tests/integration/cmd_dev_test.go:1691 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38495" << Captured StdOut/StdErr Output ------------------------------ • [210.289 seconds] odo dev command tests checking if odo dev matches local Devfile K8s resources and remote resources when odo dev is executed to run a devfile containing a k8s resource with apply command should have deleted the old resource and created the new resource /go/odo_1/tests/integration/cmd_dev_test.go:1077 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34323" << Captured StdOut/StdErr Output ------------------------------ • [57.928 seconds] odo dev command tests when a component is bootstrapped when odo dev is executed and Ephemeral is set to false should have created resources /go/odo_1/tests/integration/cmd_dev_test.go:668 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:43425" << Captured StdOut/StdErr Output ------------------------------ • [61.507 seconds] odo dev command tests when running odo dev and composite command are nested - without metadata.name should execute all commands in composite commmand /go/odo_1/tests/integration/cmd_dev_test.go:2674 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38653" << Captured StdOut/StdErr Output ------------------------------ • [57.936 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev should expose the endpoint on localhost (podman=false, manual=true, customPortForwarding=false, customAddress=true) /go/odo_1/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41401" << Captured StdOut/StdErr Output ------------------------------ • [59.299 seconds] odo dev command tests when Devfile contains metadata.projectType when running odo dev should set the correct value in labels of resources /go/odo_1/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:41421" << Captured StdOut/StdErr Output ------------------------------ • [116.527 seconds] odo dev command tests when running odo dev and run command throws an error should error out with some log /go/odo_1/tests/integration/cmd_dev_test.go:2858 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:38423" << Captured StdOut/StdErr Output ------------------------------ • [59.939 seconds] odo delete command tests when a component is bootstrapped when the component is deployed in DEV mode and dev mode stopped the component is deleted while having access to the devfile.yaml when the component is deleted with --files should have deleted the component /go/odo_1/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37817" << Captured StdOut/StdErr Output ------------------------------ • [59.812 seconds] odo dev command tests when odo dev is executed to run a devfile containing multiple k8s resource defined under a single Devfile component should have created the necessary k8s resources /go/odo_1/tests/integration/cmd_dev_test.go:1127 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40445" << Captured StdOut/StdErr Output ------------------------------ • [229.909 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:3391 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37537" << Captured StdOut/StdErr Output ------------------------------ Ran 406 of 962 Specs in 1404.684 seconds SUCCESS! -- 406 Passed | 0 Failed | 0 Pending | 556 Skipped Ginkgo ran 1 suite in 24m34.608798678s Test Suite Passed go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --poll-progress-after=120s --poll-progress-interval=120s -timeout 14400s --no-color -nodes=16 --junit-report="test-e2e.xml" tests/e2escenarios Running Suite: odo e2e scenarios - /go/odo_1/tests/e2escenarios =============================================================== Random Seed: 1701427488 - will randomize all specs Will run 4 of 4 specs Running in parallel across 16 processes ------------------------------ • [108.409 seconds] E2E Test starting with non-empty Directory test debugging should verify developer workflow from non-empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:40887" Spawning '/go/bin/odo init' from /tmp/2229469992 << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #8 Automatically polling progress: E2E Test starting with empty Directory should verify developer workflow from empty Directory (Spec Runtime: 2m3.672s) /go/odo_1/tests/e2escenarios/e2e_test.go:50 In [It] (Node Runtime: 2m0.001s) /go/odo_1/tests/e2escenarios/e2e_test.go:50 Begin Captured GinkgoWriter Output >> ... [odo] [odo] Keyboard Commands: [odo] [Ctrl+c] - Exit and delete resources from the cluster [odo] [p] - Manually apply local changes to the application on the cluster [odo] I1201 10:47:06.415763 59102 watch.go:348] filesystem watch event: REMOVE "/tmp/104028280/.odo/odo-file-index.json" [odo] I1201 10:47:06.415992 59102 watch.go:383] error removing watch for /tmp/104028280/.odo/odo-file-index.json: can't remove non-existent watcher: /tmp/104028280/.odo/odo-file-index.json [odo] I1201 10:47:06.416036 59102 watch.go:348] filesystem watch event: CREATE "/tmp/104028280/.odo/odo-file-index.json" [odo] I1201 10:47:06.419600 59102 watch.go:348] filesystem watch event: WRITE "/tmp/104028280/.odo/odo-file-index.json" [odo] I1201 10:47:06.425585 59102 watch.go:348] filesystem watch event: WRITE "/tmp/104028280/.odo/devstate.json" [odo] I1201 10:47:06.430095 59102 watch.go:348] filesystem watch event: WRITE "/tmp/104028280/.odo/devstate.59102.json" << End Captured GinkgoWriter Output Spec Goroutine goroutine 68 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0002621c0, {0x2f8fa40?, 0xc000dde3f0}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0002621c0, {0x2f8fa40, 0xc000dde3f0}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2bbd239, 0xf}, 0x0?, 0x3?, 0xc000dde360) /go/odo_1/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.StartDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...}) /go/odo_1/tests/helper/helper_dev.go:192 > github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.5.1() /go/odo_1/tests/e2escenarios/e2e_test.go:142 | | // start dev mode again > devSession, err = helper.StartDevMode(helper.DevSessionOpts{}) | Expect(err).ToNot(HaveOccurred()) | github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2658533, 0xc0003d1980}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ Progress Report for Ginkgo Process #3 Automatically polling progress: E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory (Spec Runtime: 2m3.653s) /go/odo_1/tests/e2escenarios/e2e_test.go:186 In [It] (Node Runtime: 2m0s) /go/odo_1/tests/e2escenarios/e2e_test.go:186 Begin Captured GinkgoWriter Output >> ... [odo] ✗ Finished executing the application (command: run) [27s] [odo] I1201 10:47:05.587918 58617 execute_run.go:36] error while running background command: unable to exec command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_run.pid && cd ${PROJECT_SOURCE} && (mvn -Dmaven.repo.local=/home/user/.m2/repository spring-boot:run) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_run.pid]: error while streaming command: context canceled [odo] I1201 10:47:05.606851 58617 implem.go:114] The path for preference file is /tmp/3603659902/preference.yaml [odo] Cleaning resources, please wait [odo] I1201 10:47:05.608127 58617 segment.go:268] Checking telemetry enable status [odo] I1201 10:47:05.608148 58617 segment.go:286] Sending telemetry disabled by env variable [odo] I1201 10:47:05.764292 58617 all.go:46] starting to concurrently query 201 APIs [odo] I1201 10:47:05.766758 58617 all.go:62] fired up all goroutines to query APIs [odo] I1201 10:47:06.469399 58617 all.go:67] all goroutines have returned in 705.11182ms [odo] I1201 10:47:06.469448 58617 all.go:76] query result: objects=640 << End Captured GinkgoWriter Output Spec Goroutine goroutine 61 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0002882a0, {0x2f8f920?, 0xc00050c870}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0002882a0, {0x2f8f920, 0xc00050c870}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc0006b9d28?, {0xc0007cc630?, 0xc0006b9c18?, 0x3?}) /go/odo_1/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) /go/odo_1/tests/helper/helper_dev.go:263 > github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.6.2() /go/odo_1/tests/e2escenarios/e2e_test.go:245 | // "exit dev mode and run odo deploy" | devSession.Stop() > devSession.WaitEnd() | | // all resources should be deleted from the namespace github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ Progress Report for Ginkgo Process #7 Automatically polling progress: E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop (Spec Runtime: 2m8.523s) /go/odo_1/tests/e2escenarios/e2e_test.go:448 In [It] (Node Runtime: 2m0.001s) /go/odo_1/tests/e2escenarios/e2e_test.go:448 Begin Captured GinkgoWriter Output >> ... [odo] ✓ Building your application in container (command: build) [3s] [odo] I1201 10:47:09.113517 58737 kubeexec.go:54] StartProcessForCommand for "run" [odo] • Executing the application (command: run) ... [odo] I1201 10:47:09.113582 58737 retry.go:48] waiting for 5 second(s) before trying task "process for command \"run\"" [odo] I1201 10:47:09.113616 58737 exec.go:37] Executing command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_run.pid && cd ${PROJECT_SOURCE} && (./main) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_run.pid] for pod: eobeev-app-7486668bfd-wzf8d in container: runtime [odo] I1201 10:47:14.113660 58737 execute_run.go:90] checking if process for command "run" is running [odo] I1201 10:47:14.113723 58737 kubeexec.go:40] GetProcessInfoForCommand for "run" [odo] I1201 10:47:14.113758 58737 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: eobeev-app-7486668bfd-wzf8d in container: runtime [odo] I1201 10:47:14.341594 58737 exec.go:96] 160 [odo] I1201 10:47:14.344715 58737 exec.go:37] Executing command [/bin/sh -c kill -0 160; echo $?] for pod: eobeev-app-7486668bfd-wzf8d in container: runtime << End Captured GinkgoWriter Output Spec Goroutine goroutine 82 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0000cdf80, {0x2f8fa40?, 0xc0006f3f80}, 0x1, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0000cdf80, {0x2f8fa40, 0xc0006f3f80}, {0x0, 0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2baf14b, 0x8}, 0x0?, 0x48?, 0xc00041d0b0) /go/odo_1/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc000a7be28) /go/odo_1/tests/helper/helper_dev.go:279 > github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.8.4() /go/odo_1/tests/e2escenarios/e2e_test.go:513 | helper.Cmd("odo", "remove", "binding", "--name", bindingName).ShouldPass() | > err = devSession.WaitSync() | Expect(err).To(BeNil()) | Eventually(func() string { return helper.Cmd("odo", "describe", "binding").ShouldRun().Out() }). github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0, 0x0}) /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode /go/odo_1/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ • [151.965 seconds] E2E Test starting with empty Directory should verify developer workflow from empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:50 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:34379" Spawning '/go/bin/odo init' from /tmp/104028280 Spawning '/go/bin/odo delete component' from /tmp/104028280 << Captured StdOut/StdErr Output ------------------------------ • [168.637 seconds] E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop /go/odo_1/tests/e2escenarios/e2e_test.go:448 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37233" Spawning '/go/bin/odo init' from /tmp/3425454539 << Captured StdOut/StdErr Output ------------------------------ • [241.715 seconds] E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory /go/odo_1/tests/e2escenarios/e2e_test.go:186 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "http://127.0.0.1:37829" Spawning '/go/bin/odo init' from /tmp/3956366621 Spawning '/go/bin/odo delete component' from /tmp/3956366621 << Captured StdOut/StdErr Output ------------------------------ Ran 4 of 4 Specs in 241.775 seconds SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 4m19.473780903s Test Suite Passed