go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --poll-progress-after=120s --poll-progress-interval=120s -timeout 14400s --no-color -p --junit-report="test-integration-nc.xml" --label-filter=nocluster tests/integration Running Suite: Integration Suite - C:\Users\Administrator.ANSIBLE-TEST-VS\4661\tests\integration ================================================================================================ Random Seed: 1698657685 - will randomize all specs Will run 135 of 956 specs Running in parallel across 7 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [0.842 seconds] odo devfile registry command tests label nocluster when adding a registry should list newly added registry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:171 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [1.179 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile-path flag with a local devfile should copy the devfile.yaml file [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:232 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [1.364 seconds] odo preference and config command tests label nocluster When no ConsentTelemetry preference value is set should not prompt when user calls for help [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ + [1.464 seconds] odo preference and config command tests label nocluster When ConsentTelemetry preference value is set should not prompt the user [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:203 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [1.461 seconds] odo preference and config command tests label nocluster when telemetry is enabled when unsetting value for preference Timeout should track parameter that is unset without any value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:247 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSS ------------------------------ + [1.723 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference Timeout should track parameter that is set along with its plain value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS ------------------------------ + [1.182 seconds] odo devfile registry command tests label nocluster when adding a registry should fail, when adding same registry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:181 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ + [1.936 seconds] odo create/delete/list/set namespace/project tests list project should fail, without cluster [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:212 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSS ------------------------------ + [1.950 seconds] odo preference and config command tests label nocluster when telemetry is enabled when unsetting value for preference ConsentTelemetry should track parameter that is unset without any value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:247 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.299 seconds] odo preference and config command tests label nocluster when telemetry is enabled when unsetting value for preference UpdateNotification should track parameter that is unset without any value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:247 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [0.443 seconds] odo create/delete/list/set namespace/project tests list namespace should fail, without cluster [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:212 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSS ------------------------------ + [2.848 seconds] odo devfile init command tests label nocluster telemetry when recording telemetry data with valid caller env var: jboss should record the telemetry data correctly [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:563 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [0.847 seconds] odo devfile build-images command tests label nocluster using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should run 'odo build-images --push' [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:335 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.570 seconds] odo describe component command tests describe commands in Devfile when initializing a component with different types of commands should describe the Devfile commands in human-readable form [unauth, nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:725 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ + [0.644 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile-path flag with a URL should copy the devfile.yaml file [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:243 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [1.442 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference ImageRegistry should track parameter that is set along with its hashed value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [0.385 seconds] odo devfile registry command tests label nocluster Should fail to delete the registry, when registry is not present [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:162 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [2.873 seconds] odo devfile registry command tests label nocluster Should list detailed information regarding nodejs [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:51 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [1.350 seconds] odo devfile init command tests label nocluster when a dangling env file exists in the working directory should successfully create a devfile component and remove the dangling env file [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:261 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSS ------------------------------ + [6.153 seconds] odo devfile init command tests label nocluster should fail [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:46 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [0.522 seconds] odo devfile build-images command tests label nocluster using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not build images [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:284 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [0.380 seconds] odo devfile init command tests label nocluster telemetry should error out if ODO_DISABLE_TELEMETRY=true and ODO_TRACKING_CONSENT=yes [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:452 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [1.189 seconds] odo preference and config command tests label nocluster When viewing global config should get the default global config keys [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:74 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [2.768 seconds] odo preference and config command tests label nocluster when telemetry is enabled when unsetting value for preference Ephemeral should track parameter that is unset without any value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:247 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS ------------------------------ + [0.752 seconds] odo describe component command tests when creating a component should describe the component in the current directory [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:210 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [1.548 seconds] odo devfile registry command tests label nocluster Should list java-openliberty specifically [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:112 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [1.449 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile-version flag to download a specific version should download the devfile with the requested version [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:198 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [7.273 seconds] odo init interactive command tests label nocluster should start downloading starter project only after all interactive questions have been asked [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:586 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\175079141 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [0.268 seconds] odo init interactive command tests label nocluster displaying welcoming messages when directory is not empty [It] should display appropriate welcoming messages [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:460 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Unix specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:463 @ 10/30/23 04:22:14.076 ------------------------------ SS ------------------------------ + [2.244 seconds] odo init interactive command tests label nocluster displaying welcoming messages when alizer detection of javascript name should display node-echo name [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:513 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3350811373 << Captured StdOut/StdErr Output ------------------------------ + [0.381 seconds] odo devfile registry command tests label nocluster Should list all default registries [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:41 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [0.390 seconds] odo run command tests when directory is empty should error [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_run_test.go:36 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [2.603 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference ImageRegistry should anonymize values set such that same strings have same hash [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:287 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [0.953 seconds] odo devfile init command tests label nocluster when running odo init with a devfile that has a subDir starter project should successfully extract the project in the specified subDir path [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:271 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [0.670 seconds] odo devfile build-images command tests label nocluster when using a devfile.yaml containing an Image component with Dockerfile args should be able pass extra flags to Podman/Docker build command [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [2.602 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference ImageRegistry should anonymize values set such that different strings will not have same hash [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:304 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS ------------------------------ + [0.620 seconds] odo devfile registry command tests label nocluster when adding a registry should list registry with recently added registry on top [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:195 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [3.583 seconds] odo init interactive command tests label nocluster should download correct devfile [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:229 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2177532214 << Captured StdOut/StdErr Output ------------------------------ + [0.477 seconds] odo generic label nocluster returns error when using an invalid command [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:57 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.819 seconds] odo describe component command tests when creating a component when renaming to hide devfile.yaml file should describe the component in the current directory using the hidden devfile [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:239 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [0.997 seconds] odo devfile init command tests label nocluster should successfully run odo init for devfile with starter project from the specified branch [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:303 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.351 seconds] odo devfile init command tests label nocluster telemetry when recording telemetry data with empty caller env var should record the telemetry data correctly [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:563 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [0.573 seconds] odo devfile build-images command tests label nocluster when using a devfile.yaml containing an Image component should pass extra args to Podman [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:102 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS ------------------------------ + [1.205 seconds] odo devfile init command tests label nocluster should successfully run odo init for devfile with starter project from the specified tag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:309 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.465 seconds] odo generic label nocluster when running odo without subcommand and flags a short vesion of help contents is returned, an error is not expected [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:52 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [0.564 seconds] odo devfile build-images command tests label nocluster 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 [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:235 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.590 seconds] odo devfile build-images command tests label nocluster 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 [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:191 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [1.385 seconds] odo devfile init command tests label nocluster when running odo init from a directory with sources should work without --starter flag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:327 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.660 seconds] odo devfile build-images command tests label nocluster when using a devfile.yaml with no Image component should not be able to run odo build-images [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [1.338 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile flag and JSON output should return correct values in output [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:152 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [0.766 seconds] odo preference and config command tests label nocluster When no ConsentTelemetry preference value is set should not prompt when preference command is run [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:181 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [1.495 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference PushTimeout should track parameter that is set along with its plain value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.611 seconds] odo preference and config command tests label nocluster when when preference.yaml contains an int value for Timeout should show warning about incompatible Timeout value when viewing preferences [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:158 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSS ------------------------------ + [0.401 seconds] odo generic label nocluster when running odo --help returns full help contents including usage, examples, commands, utility commands, component shortcuts, and flags sections [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:38 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.388 seconds] odo devfile init command tests label nocluster telemetry when recording telemetry data with invalid caller env var should record the telemetry data correctly [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:563 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [0.453 seconds] odo devfile init command tests label nocluster checking odo init final output message when the devfile used by `odo init` contains a deploy command should show information about both `odo dev`, and `odo deploy` [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:373 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [0.402 seconds] odo devfile build-images command tests label nocluster using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not run 'odo build-images --push' [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:292 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [0.550 seconds] odo logs command tests when in a devfile directory when not connected to any cluster or podman odo logs should fail with an error message [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:61 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS ------------------------------ + [1.127 seconds] odo init interactive command tests label nocluster when Alizer cannot determine a Devfile based on the current source code should not fail but fallback to the interactive mode [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:694 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3883820337 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSS ------------------------------ + [2.397 seconds] odo devfile init command tests label nocluster telemetry when recording telemetry data with valid caller env var: intellij should record the telemetry data correctly [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:563 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [0.406 seconds] odo generic Experimental Mode when experimental mode is enabled should display warning message [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:233 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [0.372 seconds] odo devfile init command tests label nocluster checking odo init final output message when the devfile used by `odo init` does not contain a deploy command should only show information about `odo dev`, and not `odo deploy` [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:355 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [2.526 seconds] odo preference and config command tests label nocluster when telemetry is enabled when unsetting value for preference PushTimeout should track parameter that is unset without any value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:247 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [1.387 seconds] odo preference and config command tests label nocluster when telemetry is enabled when telemetry is enabled in preferences when setting ConsentTelemetry to false should record the odo-preference-set command in telemetry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:336 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS ------------------------------ + [0.796 seconds] odo generic label nocluster returns JSON error [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:62 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSS ------------------------------ + [0.606 seconds] odo devfile build-images command tests label nocluster when using a devfile.yaml containing an Image component should run odo build-images without push [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:102 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [0.524 seconds] odo devfile build-images command tests label nocluster using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should build images [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:328 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [0.498 seconds] odo devfile build-images command tests label nocluster 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 [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:235 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [2.349 seconds] odo init interactive command tests label nocluster Automatic port detection via Alizer when starting with an existing project should display ports detected [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:651 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1465980843 << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [0.619 seconds] odo logs command tests when in a devfile directory when not connected to any cluster or podman odo logs --platform podman should fail with an error message [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:67 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [1.505 seconds] odo devfile registry command tests label nocluster when adding a registry should pass, when doing odo init with --devfile-registry flag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [1.377 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference ConsentTelemetry should track parameter that is set along with its plain value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [2.560 seconds] odo preference and config command tests label nocluster when telemetry is enabled when unsetting value for preference RegistryCacheTime should track parameter that is unset without any value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:247 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [2.227 seconds] odo init interactive command tests label nocluster displaying welcoming messages when alizer detection of javascript name should ask to re-enter the component name if invalid value is passed by the user [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:548 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2969539326 << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [0.544 seconds] odo dev command tests when a component is bootstrapped should fail to run odo dev when not connected to any cluster [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:82 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [3.587 seconds] odo init interactive command tests label nocluster should ask to re-enter the component name when an invalid value is passed [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:142 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2188916282 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSS ------------------------------ + [1.007 seconds] odo list with devfile devfile has missing metadata when projectType and language is missing should show 'Not available' for 'Type' in odo list [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:346 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [1.421 seconds] odo preference and config command tests label nocluster when telemetry is enabled when Telemetry is disabled in preferences when setting ConsentTelemetry to true should record the odo-preference-set command in telemetry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:361 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS ------------------------------ + [3.297 seconds] odo init interactive command tests label nocluster should not fail when using -v flag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:49 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init -v 4' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3313633964 << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [2.415 seconds] odo devfile init command tests label nocluster telemetry when recording telemetry data with valid caller env var: vscode should record the telemetry data correctly [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:563 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.694 seconds] odo preference and config command tests label nocluster check that help works should display help info [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:46 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [1.418 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile flag should download a devfile.yaml file and correctly set the component name in it [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:133 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ S [0.289 seconds] odo init interactive command tests label nocluster [It] should print automation command with proper values [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:180 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Unix specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:184 @ 10/30/23 04:22:23.538 ------------------------------ SSSSSSSSS ------------------------------ + [0.473 seconds] odo devfile build-images command tests label nocluster using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should build images [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:328 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSS ------------------------------ + [0.399 seconds] odo generic label nocluster returns error when using an invalid command with --help [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:92 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [0.447 seconds] odo preference and config command tests label nocluster should fail to set an incompatible format for a preference that accepts duration [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:165 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.470 seconds] odo devfile build-images command tests label nocluster using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not run 'odo build-images --push' [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:292 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [0.255 seconds] odo init interactive command tests label nocluster displaying welcoming messages when directory is empty [It] should display appropriate welcoming messages [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:409 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Unix specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:412 @ 10/30/23 04:22:24.233 ------------------------------ SSSSSS ------------------------------ + [0.535 seconds] odo devfile build-images command tests label nocluster when using a devfile.yaml containing an Image component with Dockerfile args should use args to build image when running odo build-images [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:145 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [1.437 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference UpdateNotification should track parameter that is set along with its plain value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [0.490 seconds] odo devfile registry command tests label nocluster when adding a registry should successfully delete registry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:185 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [0.392 seconds] odo generic label nocluster when running odo --help does not support the --kubeconfig flag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:42 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [0.421 seconds] odo devfile init command tests label nocluster when running odo init from a directory with sources should not accept --starter flag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:330 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [5.140 seconds] odo preference and config command tests label nocluster When configuring global config values should successfully updated [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:114 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [0.439 seconds] odo describe component command tests describe commands in Devfile when initializing a component with different types of commands should describe the Devfile commands in JSON output [unauth, nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:761 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [2.398 seconds] odo devfile init command tests label nocluster telemetry when recording telemetry data with ODO_TRACKING_CONSENT=yes env var should take precedence over ConsentTelemetry preference should record the telemetry data correctly [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:563 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [3.820 seconds] odo init interactive command tests label nocluster should ask to download the starter project when the devfile stack has extra files [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1418205047 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSS ------------------------------ + [0.407 seconds] odo preference and config command tests label nocluster when running help for preference command should display the help [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:56 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSS ------------------------------ + [0.614 seconds] odo run command tests when a component is bootstrapped should fail if command is not found in devfile [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_run_test.go:49 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [0.420 seconds] odo generic executing odo version command when executing the complete command with server info should show the version of odo major components [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:184 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [2.517 seconds] odo preference and config command tests label nocluster when telemetry is enabled when unsetting value for preference ImageRegistry should track parameter that is unset without any value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:247 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.564 seconds] odo devfile registry command tests label nocluster Should fail with an error with no registries [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:156 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.539 seconds] odo devfile build-images command tests label nocluster using a Devfile with an image component using a remote Dockerfile when remote server returns a valid file should run 'odo build-images --push' [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:335 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.650 seconds] odo devfile build-images command tests label nocluster 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 [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:191 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.565 seconds] odo devfile build-images command tests label nocluster using a Devfile with an image component using a remote Dockerfile when remote server returns an error should not build images [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:284 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.889 seconds] odo devfile registry command tests label nocluster Should list at least one nodejs component from the default registry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:46 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.631 seconds] odo devfile build-images command tests label nocluster when using a devfile.yaml containing an Image component should run odo build-images --push [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:102 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSS ------------------------------ + [0.454 seconds] odo devfile init command tests label nocluster checking odo init final output message when the devfile used by `odo init` contains a deploy command should not show the interactive mode notice message [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:378 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.918 seconds] odo run command tests when a component is bootstrapped should fail if platform is not available [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_run_test.go:55 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [0.879 seconds] odo describe component command tests should fail, without cluster [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:36 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSS ------------------------------ + [0.578 seconds] odo list with devfile when a component created in 'app' application should list the local component when no authenticated [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:115 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.596 seconds] odo devfile build-images command tests label nocluster when using a devfile.yaml containing an Image component should pass extra args to Docker [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:102 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ + [0.490 seconds] odo devfile init command tests label nocluster when devfile contains parent URI should not replace the original devfile [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:400 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [0.355 seconds] odo devfile registry command tests label nocluster should fail when adding a git based registry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:208 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSSS ------------------------------ + [4.865 seconds] odo init interactive command tests label nocluster personalizing configuration should allow to add and delete a port [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:89 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1888864421 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSSS ------------------------------ + [0.581 seconds] odo devfile deploy command tests when a component is bootstrapped should fail to run odo deploy when not connected to any cluster [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:76 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [1.430 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference RegistryCacheTime should track parameter that is set along with its plain value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [0.675 seconds] odo devfile registry command tests label nocluster when adding a registry deleting registry and creating component with registry flag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:189 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [0.385 seconds] odo devfile init command tests label nocluster checking odo init final output message when the devfile used by `odo init` does not contain a deploy command should not show the interactive mode notice message [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:360 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [0.449 seconds] odo preference and config command tests label nocluster When viewing global config should get the default global config keys in JSON output [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:83 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [0.562 seconds] odo devfile init command tests label nocluster when source directory is empty name in devfile is personalized in non-interactive mode [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:417 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [1.530 seconds] odo preference and config command tests label nocluster when telemetry is enabled when setting value for preference Ephemeral should track parameter that is set along with its plain value [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [1.429 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile-version flag and JSON output to download a specific version should show the requested devfile version [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:212 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ + [0.829 seconds] odo list with devfile devfile has missing metadata when projectType is missing should show the language for 'Type' in odo list [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:314 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [0.389 seconds] odo devfile init command tests label nocluster telemetry should error out if ODO_DISABLE_TELEMETRY=false and ODO_TRACKING_CONSENT=no [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:452 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [2.014 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile-version flag and JSON output to download the latest version should show the requested devfile version [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:212 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [1.386 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile-registry flag should successfully run odo init if specified registry is valid [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:251 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [1.885 seconds] odo devfile init command tests label nocluster running odo init with valid flags when using --devfile-version flag to download the latest version should download the devfile with the requested version [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:198 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [1.570 seconds] odo devfile init command tests label nocluster should successfully run odo init for devfile with starter project on git with main default branch [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:315 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.383 seconds] odo devfile init command tests label nocluster telemetry when recording telemetry data with no caller env var should record the telemetry data correctly [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:563 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.891 seconds] odo init interactive command tests label nocluster should download correct devfile-starter [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:310 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2419578773 << Captured StdOut/StdErr Output ------------------------------ Ran 128 of 956 Specs in 26.063 seconds SUCCESS! -- 128 Passed | 0 Failed | 0 Pending | 828 Skipped Ginkgo ran 1 suite in 1m6.7193308s 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-integration.xml" --label-filter="!unauth && !nocluster && !podman" tests/integration Running Suite: Integration Suite - C:\Users\Administrator.ANSIBLE-TEST-VS\4661\tests\integration ================================================================================================ Random Seed: 1698657765 - will randomize all specs Will run 504 of 956 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSSSSSS ------------------------------ S [14.595 seconds] odo dev command tests when a component is bootstrapped [It] should not set securitycontext for podsecurity admission C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:392 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:394 @ 10/30/23 04:23:15.489 ------------------------------ + [16.839 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4211 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [17.172 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:377 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:414 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:379 @ 10/30/23 04:23:17.475 ------------------------------ S ------------------------------ + [19.364 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:450 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [18.821 seconds] odo describe component command tests should fail, with cluster C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:89 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [19.536 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:46 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [24.074 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [5.231 seconds] odo create/delete/list/set namespace/project tests set namespace should successfully set the namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:147 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [33.090 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:576 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [35.955 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3080 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [20.331 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:595 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [37.335 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:547 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [59.281 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [9.079 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:267 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.725 seconds] odo describe component command tests when creating a component should not describe the component from another directory, with default cluster mode C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:264 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [77.256 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /foobar.txt file should not synchronize it C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1977 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [62.111 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2058 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [3.431 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1815 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1882 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1818 @ 10/30/23 04:24:23.438 ------------------------------ S ------------------------------ + [59.068 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [83.567 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:444 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [2.197 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:654 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [3.032 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:326 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [88.760 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:636 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [58.249 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:736 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [95.155 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1805 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.572 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [102.968 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [89.587 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.268 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:108 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [77.296 seconds] odo dev command tests when running odo dev and composite command are nested - with metadata.name should execute all commands in composite commmand C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2674 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [48.474 seconds] odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=false C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4921 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.382 seconds] odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:233 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [117.783 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:348 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [35.605 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [47.272 seconds] odo dev command tests when a component is bootstrapped when running with --no-commands (debug=true) should start the dev session C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:268 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ Progress Report for Ginkgo Process #1 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: 2m2.488s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1077 In [BeforeEach] (Node Runtime: 2m0.013s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1050 Begin Captured GinkgoWriter Output >> ... [odo] I1030 04:25:18.845267 880 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1030 04:25:18.845267 880 port.go:319] port 8080 not listening in container "runtime" [odo] I1030 04:25:22.642314 880 exec.go:37] Executing command [/bin/sh -c cat /proc/net/tcp /proc/net/udp /proc/net/tcp6 /proc/net/udp6 || true] for pod: pvydod-app-76d6469b45-fzfj2 in container: runtime [odo] I1030 04:25:22.909924 880 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1030 04:25:22.910077 880 exec.go:96] 0: FC0811AC:A2EC 22191068:01BB 06 00000000:00000000 03:00000F00 00000000 0 0 0 3 0000000000000000 [odo] I1030 04:25:22.910249 880 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1030 04:25:22.910506 880 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1030 04:25:22.910506 880 exec.go:96] 0: 00000000000000000000000000000000:0BB8 00000000000000000000000000000000:0000 0A 00000000:00000000 00:00000000 00000000 1000840000 0 1572988255 1 0000000000000000 100 0 0 10 0 [odo] I1030 04:25:22.910506 880 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1030 04:25:22.916215 880 port.go:319] port 8080 not listening in container "runtime" << End Captured GinkgoWriter Output Spec Goroutine goroutine 178 [select, 2 minutes] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc00047d180, {0x2c18dc8?, 0xc000eb3740}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc00047d180, {0x2c18dc8, 0xc000eb3740}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x283ef94, 0x8}, 0xc0008f2c20?, 0xc0008f2c00?, 0xc000aa7dd0) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc000381bc0) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_dev.go:279 > github.com/redhat-developer/odo/tests/integration.glob..func7.5.1.1() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/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({0x2262365, 0xc000cde000}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [117.826 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1743 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS ------------------------------ + [3.788 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=true) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:445 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [84.247 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:161 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [11.035 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:576 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [151.617 seconds] odo dev command tests when running odo dev and composite command is used as a run command - with metadata.name should run successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2709 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.556 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:628 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [55.458 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev [It] should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=false, customAddress=false) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1505 @ 10/30/23 04:25:03.459 ------------------------------ + [28.578 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:291 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [87.871 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:577 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [46.350 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2549 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [80.418 seconds] odo dev debug command tests when a composite command is used as debug command - with metadata.name should run successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:225 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.939 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [2.218 seconds] odo dev command tests when directory is empty should error C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:64 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [56.595 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:389 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [56.891 seconds] odo dev command tests when a component is bootstrapped when recording telemetry data should record the telemetry data correctly C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:458 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.448 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:802 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.781 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:348 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [117.779 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [3.348 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:132 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [4.627 seconds] odo create/delete/list/set namespace/project tests create project should successfully create the project C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:54 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [116.718 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3697 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.172 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:143 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [56.846 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.011 seconds] odo create/delete/list/set namespace/project tests set namespace when running inside a component directory should set the namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:190 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [56.815 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev [It] should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=false, customAddress=true) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1505 @ 10/30/23 04:26:06.072 ------------------------------ S ------------------------------ + [73.766 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2526 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [56.507 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2097 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [118.090 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.893 seconds] odo create/delete/list/set namespace/project tests create namespace should successfully create the namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:54 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [15.985 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:115 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [3.784 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:216 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:244 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_registry_test.go:218 @ 10/30/23 04:26:46.723 ------------------------------ + [5.720 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:725 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.452 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:237 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.525 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [26.816 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [217.177 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1077 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [8.907 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [84.099 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.443 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.294 seconds] odo devfile deploy command tests when recording telemetry data should record the telemetry data correctly C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:270 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [56.499 seconds] odo dev command tests when multiple projects are present - without metadata.name should sync to the correct dir in container C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2130 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.669 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with default variable values (push=false) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:431 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [116.015 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [84.100 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should run odo dev successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:161 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [4.083 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:241 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [57.134 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:736 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.338 seconds] odo dev command tests when a component is bootstrapped should add annotation to use ImageStreams C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:147 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [139.664 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:172 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [4.270 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_deploy_test.go:159 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe deploy' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2090355907 << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [118.081 seconds] odo dev command tests when running odo dev and single env var is set - with metadata.name should be able to exec command C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1691 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.963 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:88 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [115.863 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3873 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [26.183 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [57.453 seconds] odo dev command tests when running odo dev and devfile with composite command - with metadata.name should execute all commands in composite command C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2610 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.476 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:76 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.442 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [87.413 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1965 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.111 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.659 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:326 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [5.121 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.128 seconds] odo create/delete/list/set namespace/project tests set namespace should not succeed to set the namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:162 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [24.832 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [2.401 seconds] odo dev command tests when running odo dev and prestart events are defined should not correctly execute PreStart commands C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2823 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [118.785 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2197 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [35.401 seconds] odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=false should delete the component C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:517 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [3.174 seconds] odo create/delete/list/set namespace/project tests when namespace is created with -w should list the new namespace when listing namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:41 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [79.342 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1965 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [64.899 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:668 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [110.375 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1213 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.042 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:385 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.941 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:538 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [55.203 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.851 seconds] odo create/delete/list/set namespace/project tests delete project should not succeed to delete a non-existent project C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:122 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [57.678 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1639 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [2.921 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:201 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.269 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4211 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [4.008 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [118.975 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [67.977 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:416 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [5.347 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [3.464 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1815 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1882 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1818 @ 10/30/23 04:29:00.867 ------------------------------ SSSSS ------------------------------ + [84.048 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:161 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [131.255 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1237 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.941 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1612 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [68.225 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3181 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [66.532 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1668 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [89.407 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:219 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [35.404 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [67.749 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:108 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [54.579 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.431 seconds] odo dev command tests when devfile has sourcemappings and running odo dev - with metadata.name should sync files to the correct location C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2016 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [4.490 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:226 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [126.906 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3787 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [55.650 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.640 seconds] odo devfile deploy command tests deploying devfile with long-running exec when Automount volumes are present in the namespace should mount the volumes C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:695 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.238 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [65.361 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [56.988 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [75.791 seconds] odo dev command tests when Create and dev java-springboot component should execute default build and run commands correctly C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2931 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [3.738 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:880 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.479 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [2.073 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:63 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.413 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3207 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [136.380 seconds] odo dev command tests when running odo dev and composite command is used as a run command - without metadata.name should run successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2709 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [129.583 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:501 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [46.977 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 [BeforeEach] should trigger a push [BeforeEach] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:746 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:754 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:748 @ 10/30/23 04:30:05.825 ------------------------------ + [118.777 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:642 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [76.964 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:98 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [22.427 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3150 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [56.356 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [86.764 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #3 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: 2m2.932s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4146 In [It] (Node Runtime: 2m0.001s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4146 Begin Captured GinkgoWriter Output >> ... [odo] I1030 04:30:34.901358 8876 kubeexec.go:40] GetProcessInfoForCommand for "run" [odo] I1030 04:30:34.901358 8876 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: hlzydr-app-fbdc99d55-9qfpr in container: runtime [odo] I1030 04:30:34.901863 8876 exec.go:54] ExecuteCommand returned an an err: error while streaming command: error sending request: Post "https://c115-e.eu-de.containers.cloud.ibm.com:31900/api/v1/namespaces/cmd-dev-test4146csr/pods/hlzydr-app-fbdc99d55-9qfpr/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Fopt%2Fodo%2F.odo_cmd_run.pid+%7C%7C+true&container=runtime&stderr=true&stdout=true": dial tcp: lookup c115-e.eu-de.containers.cloud.ibm.com: operation was canceled. for command '[/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true]' [odo] stdout: [] [odo] stderr: [] [odo] I1030 04:30:34.902041 8876 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] I1030 04:30:34.951661 8876 all.go:46] starting to concurrently query 200 APIs [odo] I1030 04:30:34.952246 8876 all.go:62] fired up all goroutines to query APIs [odo] I1030 04:30:35.647850 8876 all.go:67] all goroutines have returned in 696.1856ms [odo] I1030 04:30:35.647850 8876 all.go:76] query result: objects=615 << End Captured GinkgoWriter Output Spec Goroutine goroutine 432 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0006d00e0, {0x2c18b88?, 0xc00032be48}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0006d00e0, {0x2c18b88, 0xc00032be48}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc000e6fd50?, {0xc00091f8d0?, 0x2840c96?, 0x9?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_dev.go:263 github.com/redhat-developer/odo/tests/helper.RunDevMode.func1() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_dev.go:334 github.com/redhat-developer/odo/tests/helper.RunDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...}, ...) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_dev.go:337 > github.com/redhat-developer/odo/tests/integration.glob..func7.64.2() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/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({0x2262365, 0xc000d7a720}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [56.304 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3583 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [115.473 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2230 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [126.692 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4146 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [2.398 seconds] odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces in JSON format C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:228 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [65.030 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 [BeforeEach] should trigger a push [BeforeEach] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:746 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:754 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:748 @ 10/30/23 04:30:35.749 ------------------------------ SSSS ------------------------------ + [4.321 seconds] odo create/delete/list/set namespace/project tests set project when running inside a component directory should set the project C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:190 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [67.785 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1127 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [92.693 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:140 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSS ------------------------------ + [57.491 seconds] odo dev command tests when multiple projects are present - with metadata.name should sync to the correct dir in container C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2130 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [56.396 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1612 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [67.675 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.446 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:226 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.066 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:239 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" <<< Session terminated >>> << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [2.926 seconds] odo describe component command tests should fail, with default cluster mode C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:70 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [74.912 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:5007 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [49.030 seconds] odo dev command tests when a component is bootstrapped when running with --no-commands (debug=false) should start the dev session C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:268 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [52.665 seconds] odo run command tests when a component is bootstrapped when odo dev is executed with --no-commands=true and ready should execute commands C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_run_test.go:100 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [55.863 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [66.613 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2549 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.788 seconds] odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:233 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [46.807 seconds] odo dev command tests when using a Devfile with no commands should start the Dev Session with --no-commands=true C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4921 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.432 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.818 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=false) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:437 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [21.823 seconds] odo dev interactive command tests when a component is bootstrapped should sync files when p is pressed C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_dev_test.go:211 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe dev --random-ports --no-watch' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2282722646 << Captured StdOut/StdErr Output ------------------------------ + [57.056 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1127 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.849 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [147.437 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2278 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [83.422 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.151 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3126 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.741 seconds] odo generic executing odo version command should only print client info when using --client flag C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:201 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #16 Automatically polling progress: 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 (Spec Runtime: 2m3.345s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:161 In [It] (Node Runtime: 2m0.003s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:161 Begin Captured GinkgoWriter Output >> ... [odo] [p] - Manually apply local changes to the application on the cluster [odo] I1030 04:32:37.296328 3520 watch.go:271] deployment watcher Event: Type: MODIFIED, name: bwqcoy-app, rv: 96601200, generation: 1, pods: 1 [odo] I1030 04:32:37.589839 3520 watch.go:348] filesystem watch event: CREATE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3376909178\\.odo\\odo-file-index.json" [odo] I1030 04:32:37.590205 3520 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3376909178\\.odo\\odo-file-index.json" [odo] I1030 04:32:37.590454 3520 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3376909178\\.odo" [odo] I1030 04:32:37.590905 3520 file_watcher.go:101] ignoring watch on path C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3376909178\.odo [odo] I1030 04:32:37.590905 3520 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3376909178\\.odo\\devstate.json" [odo] I1030 04:32:37.591165 3520 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3376909178\\.odo\\devstate.json" [odo] I1030 04:32:37.591434 3520 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3376909178\\.odo\\devstate.3520.json" [odo] I1030 04:32:37.591669 3520 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3376909178\\.odo\\devstate.3520.json" << End Captured GinkgoWriter Output Spec Goroutine goroutine 2576 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0005ba460, {0x2c18dc8?, 0xc000a11950}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0005ba460, {0x2c18dc8, 0xc000a11950}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x284db8b, 0xf}, 0x0?, 0x3?, 0xc000a11920) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.StartDevMode({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, 0x0, 0x0, 0x0, 0x0, ...}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_dev.go:192 > github.com/redhat-developer/odo/tests/integration.glob..func9.6.2.3() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:162 | | It("should run odo dev successfully", func() { > devSession, err := helper.StartDevMode(helper.DevSessionOpts{}) | Expect(err).ToNot(HaveOccurred()) | devSession.Kill() github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2262365, 0xc0019deea0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [124.089 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:161 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [90.953 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:249 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [58.059 seconds] odo dev command tests when a component is bootstrapped should use the index information from previous push operation C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:200 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [56.844 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:171 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [15.361 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:115 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [4.393 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:241 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [25.005 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.004 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [138.210 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4579 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [66.625 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [118.107 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3375 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [55.854 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1589 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [2.920 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:450 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [4.668 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.332 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [56.780 seconds] odo dev command tests when a container component defines a Command or Args - with metadata.name should run odo dev successfully (#5620) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3538 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [10.398 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_dev_test.go:164 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe dev --random-ports' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1438362529 << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [35.439 seconds] odo delete command tests when deleting a component containing preStop event that is deployed with DEV and --files=true should delete the component C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:517 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [60.860 seconds] odo run command tests when a component is bootstrapped when odo dev is executed with --no-commands=false and ready should execute commands C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_run_test.go:100 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [108.752 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:282 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [58.798 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2642 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [5.541 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:552 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.917 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [119.126 seconds] odo dev command tests when running odo dev and single env var is set - without metadata.name should be able to exec command C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1691 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [55.983 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev [It] should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=true, customAddress=true) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1505 @ 10/30/23 04:33:23.565 ------------------------------ + [119.992 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:181 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [48.071 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:736 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [2.132 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:586 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:613 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_init_test.go:588 @ 10/30/23 04:33:59.219 ------------------------------ + [117.198 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:176 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [3.928 seconds] odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:221 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [6.186 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:241 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [2.247 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:676 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:678 @ 10/30/23 04:34:05.343 ------------------------------ S ------------------------------ + [73.793 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4756 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.738 seconds] odo dev command tests when a component is bootstrapped should fail when using --random-ports and --port-forward together C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:218 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.120 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.014 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:538 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [58.558 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2642 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [118.531 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:163 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [3.656 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:708 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:737 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_init_test.go:710 @ 10/30/23 04:34:26.761 ------------------------------ + [47.217 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:981 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [67.565 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:124 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [118.013 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2197 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [6.422 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:552 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [57.080 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [67.320 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:389 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [127.777 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [54.543 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [57.629 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [67.535 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.259 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1668 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [66.890 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [67.671 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3207 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.501 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:372 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [58.099 seconds] odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1955 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.450 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2097 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [57.078 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 [BeforeEach] should react on the Devfile modification (podman=false, manual=true, customPortForwarding=true, customAddress=false) [BeforeEach] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1353 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1356 @ 10/30/23 04:35:04.503 ------------------------------ + [57.488 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [55.715 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1589 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [86.181 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:629 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [67.455 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:98 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [65.699 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [8.790 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:546 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [129.715 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:631 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [26.592 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [121.116 seconds] odo list with devfile when a component created in 'app' application when dev is running on cluster should display platform C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:150 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.382 seconds] odo create/delete/list/set namespace/project tests set project should not succeed to set the project C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:162 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [55.585 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [4.879 seconds] odo devfile deploy command tests when a component is bootstrapped when using a default namespace should display warning when running the deploy command C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:67 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [66.419 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:348 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [119.718 seconds] odo dev command tests when a component is bootstrapped ensure that index information is updated C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:305 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.769 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [105.601 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [2.196 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1815 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1865 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1818 @ 10/30/23 04:36:46.097 ------------------------------ SS ------------------------------ + [25.338 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [127.912 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2772 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [127.761 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:642 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [77.352 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1805 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.780 seconds] odo create/delete/list/set namespace/project tests list project should successfully list all the projects in JSON format C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:228 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.092 seconds] odo dev command tests when a component is bootstrapped when a state file is not writable should fail running odo dev C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:435 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [111.625 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:320 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.764 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:201 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.123 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4220 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [117.626 seconds] odo dev command tests when running odo dev and run command throws an error should error out with some log C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2858 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [5.439 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:67 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.240 seconds] odo devfile deploy command tests when using a devfile.yaml containing two deploy commands should run odo deploy C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:244 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS ------------------------------ S [2.273 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:377 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:444 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on non Kubernetes clusters In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_pref_config_test.go:379 @ 10/30/23 04:37:06.551 ------------------------------ + [5.548 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_deploy_test.go:40 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe deploy -v 4' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3875602713 << Captured StdOut/StdErr Output ------------------------------ + [4.024 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:237 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [69.546 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ Progress Report for Ginkgo Process #12 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: 3m32.981s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:288 In [It] (Node Runtime: 2m0.009s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:288 At [By Step] cleaning up the resources on ending the session (Step Runtime: 27.373s) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:326 Begin Captured GinkgoWriter Output >> ... [odo] stderr: [] [odo] X Finished executing the application (command: start-debug) [1m] [odo] I1030 04:36:53.913441 4536 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] I1030 04:36:53.916707 4536 segment.go:268] Checking telemetry enable status [odo] I1030 04:36:53.916707 4536 segment.go:286] Sending telemetry disabled by env variable [odo] Cleaning resources, please wait [odo] I1030 04:36:54.077173 4536 all.go:46] starting to concurrently query 200 APIs [odo] I1030 04:36:54.078734 4536 all.go:62] fired up all goroutines to query APIs [odo] I1030 04:36:54.873495 4536 all.go:67] all goroutines have returned in 796.3217ms [odo] I1030 04:36:54.873705 4536 all.go:76] query result: objects=652 << End Captured GinkgoWriter Output Spec Goroutine goroutine 540 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0004a4070, {0x2c18b88?, 0xc00148c1c8}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0004a4070, {0x2c18b88, 0xc00148c1c8}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc0007263c0?, {0xc000774040?, 0x0?, 0x0?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_dev.go:263 > github.com/redhat-developer/odo/tests/integration.glob..func6.7.2.8() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/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(0xc00049a000, {0x289cbac, 0x2f}, {0xc000331e70, 0x1, 0x3a746e6576652068?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:309 github.com/onsi/ginkgo/v2.By({0x289cbac?, 0x6e696d64415c5c73?}, {0xc000331e70?, 0x454c4249534e412e?, 0x53562d545345542d?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/core_dsl.go:547 > github.com/redhat-developer/odo/tests/integration.glob..func6.7.2() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/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({0x746170206e6f2068, 0x6573555c3a432068}) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/node.go:463 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode.func3() C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4661/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [56.880 seconds] odo dev command tests when no project is present - without metadata.name should sync to the correct dir in container C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2164 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [2.452 seconds] odo run command tests when a component is bootstrapped should fail if odo dev is not running C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_run_test.go:72 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [225.319 seconds] odo dev debug command tests when a composite apply command is used as debug command should execute the composite apply commands successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:288 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [67.540 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1639 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [68.089 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:334 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [35.721 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.885 seconds] odo create/delete/list/set namespace/project tests list project should successfully list all the projects C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:221 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.197 seconds] odo describe component command tests when a non-odo application is present on the cluster should describe the component C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:694 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [4.451 seconds] odo devfile deploy command tests when using a devfile.yaml containing a deploy command when running odo deploy should succeed C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:143 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [65.121 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [58.317 seconds] odo dev command tests when a component is bootstrapped should sync .git directory and subfiles with --sync-git-dir C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:182 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSS ------------------------------ + [5.448 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [4.542 seconds] odo deploy interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_deploy_test.go:75 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe deploy' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\241204510 << Captured StdOut/StdErr Output ------------------------------ + [96.485 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:609 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [23.803 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:128 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [67.425 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3112 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [67.205 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3195 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.662 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4105 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [7.674 seconds] odo generic When deleting two project one after the other should be able to delete them in any order C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:107 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.990 seconds] odo dev command tests when devfile has sourcemappings and running odo dev - without metadata.name should sync files to the correct location C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2016 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [26.014 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [56.990 seconds] odo dev command tests when no project is present - with metadata.name should sync to the correct dir in container C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2164 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.682 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [4.147 seconds] odo describe component command tests when creating a component should not describe the component from another directory, with cluster C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:289 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [68.265 seconds] odo dev debug command tests when a component is bootstrapped when running odo dev with debug flag should connect to relevant ports forwarded C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:112 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [55.550 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 [BeforeEach] should react on the Devfile modification (podman=false, manual=true, customPortForwarding=false, customAddress=false) [BeforeEach] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1353 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1356 @ 10/30/23 04:37:41.924 ------------------------------ + [4.271 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:143 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [67.807 seconds] odo dev command tests when a component is bootstrapped should show validation errors if the devfile is incorrect C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:156 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [3.074 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:143 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [21.369 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:595 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [83.651 seconds] odo dev command tests when a component with endpoints is bootstrapped and pushed should not create Ingress or Route resources in the cluster C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.709 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [2.327 seconds] odo dev command tests when a component is bootstrapped [It] should start on cluster even if Podman client takes long to initialize C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:91 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] skipped on Windows as it requires Unix permissions In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:93 @ 10/30/23 04:38:40.693 ------------------------------ + [23.756 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3150 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [5.587 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [68.743 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [68.156 seconds] odo dev command tests when running odo dev and devfile with composite command - without metadata.name should execute all commands in composite command C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2610 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [58.249 seconds] odo dev command tests when a component is bootstrapped should not sync .git directory C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:166 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [5.068 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [2.277 seconds] odo dev interactive command tests directory is not empty when there is a match from Alizer [It] should display welcoming messages first C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_dev_test.go:112 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Unix specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_dev_test.go:115 @ 10/30/23 04:39:01.573 ------------------------------ SSSS ------------------------------ S [2.004 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:387 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:412 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:390 @ 10/30/23 04:39:03.632 ------------------------------ S ------------------------------ S [2.276 seconds] odo devfile deploy command tests deploying devfile with exec [It] should not set securitycontext for podsecurity admission on job's pod template C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:601 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:603 @ 10/30/23 04:39:05.842 ------------------------------ + [67.824 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:123 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.565 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:477 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.412 seconds] odo create/delete/list/set namespace/project tests set project should successfully set the project C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:147 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.977 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with --var-file (push=false) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:445 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [79.726 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:363 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [55.572 seconds] odo dev command tests when a component with multiple endpoints is run should create state files containing information, including forwarded ports C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3622 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" PID: 5196 << Captured StdOut/StdErr Output ------------------------------ + [14.958 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:648 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [116.007 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2230 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [23.820 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [80.844 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_dev_test.go:40 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe dev --random-ports -v 4' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\334779582 << Captured StdOut/StdErr Output ------------------------------ + [57.974 seconds] odo dev command tests when a container component defines a Command or Args - without metadata.name should run odo dev successfully (#5620) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3538 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [127.771 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3834 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [116.619 seconds] odo dev command tests when running odo dev and multiple env variables are set - with metadata.name should be able to exec command C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1717 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [56.589 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1002 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [116.685 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1743 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [5.480 seconds] odo generic When deleting two project one after the other should be able to delete sequentially C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/generic_test.go:100 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.003 seconds] odo create/delete/list/set namespace/project tests create namespace should fail to create namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:63 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [3.877 seconds] odo devfile deploy command tests when directory is empty should error C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:47 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [23.734 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3080 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.687 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with default variable values (push=true) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:431 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [132.015 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:833 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [66.686 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:130 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [59.239 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:124 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [56.355 seconds] odo dev command tests when running applications listening on the container loopback interface when running on default cluster platform should port-forward successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4244 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [3.195 seconds] odo deploy interactive command tests directory is not empty when there is a match from Alizer [It] should display welcoming messages first C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_deploy_test.go:109 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Unix specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_deploy_test.go:112 @ 10/30/23 04:40:10.894 ------------------------------ SSSS ------------------------------ + [94.852 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:789 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [56.201 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3195 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [116.652 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [15.139 seconds] odo create/delete/list/set namespace/project tests delete namespace when force-deleting a valid namespace should successfully delete the namespace asynchronously C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:107 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [62.102 seconds] odo dev command tests when adding local files to gitignore and running odo dev should not sync ignored files to the container C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1955 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [47.599 seconds] odo dev command tests when running odo dev and build command throws an error should error out with some log C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2898 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [4.737 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:372 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [5.126 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:71 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.478 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:99 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ S [57.038 seconds] odo dev command tests port-forwarding for the component when devfile has multiple endpoints when running odo dev [It] should expose all endpoints on localhost regardless of exposure(podman=false, manual=true, customPortForwarding=true, customAddress=false) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1505 @ 10/30/23 04:40:13.827 ------------------------------ SS ------------------------------ + [67.656 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3181 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [89.228 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [66.701 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [75.620 seconds] odo dev command tests when a component with multiple endpoints is run should fail running a second session on the same platform C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3615 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [67.670 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:416 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [61.375 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2526 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [78.426 seconds] odo dev debug command tests when a composite command is used as debug command - without metadata.name should run successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:225 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.121 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:477 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [25.122 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [5.233 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:43 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [68.262 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_debug_test.go:124 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [3.047 seconds] odo create/delete/list/set namespace/project tests delete namespace should not succeed to delete a non-existent namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:122 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [24.726 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.039 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1338 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [55.388 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [83.316 seconds] odo dev interactive command tests directory is not empty when there is a match from Alizer should run alizer to download devfile C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/interactive_dev_test.go:76 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4661\bin\odo.exe dev --random-ports' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3852487213 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [2.245 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] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1815 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1865 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] Skipping service binding tests as SKIP_SERVICE_BINDING_TESTS is true In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1818 @ 10/30/23 04:41:41.945 ------------------------------ + [5.605 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [106.406 seconds] odo dev command tests when hotReload capable Build and Run commands are used with odo dev should execute the build and run commands C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3818 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [3.814 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:502 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [3.881 seconds] odo logs command tests when directory is empty should error C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_logs_test.go:86 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [5.699 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:241 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [34.418 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [3.867 seconds] odo dev command tests when a component is bootstrapped when pod security is enforced as restricted [It] should set securitycontext for podsecurity admission C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:414 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:416 @ 10/30/23 04:41:59.354 ------------------------------ SS ------------------------------ + [5.272 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:274 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSS ------------------------------ + [147.526 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2278 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [67.546 seconds] odo dev command tests when Devfile contains metadata.language when running odo dev should set the correct value in labels of resources C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [57.671 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 [BeforeEach] should react on the Devfile modification (podman=false, manual=true, customPortForwarding=true, customAddress=true) [BeforeEach] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1353 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1356 @ 10/30/23 04:41:39.129 ------------------------------ S ------------------------------ + [56.955 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.490 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:507 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [67.198 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2058 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [2.679 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:622 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [158.386 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3269 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ S [3.473 seconds] odo devfile deploy command tests deploying devfile with exec [It] should not set securitycontext for podsecurity admission on job's pod template C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:601 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a Kubernetes specific scenario, skipping In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:603 @ 10/30/23 04:42:30.744 ------------------------------ + [65.382 seconds] odo dev command tests when adding local files to gitignore and running odo dev when modifying /foobar.txt file should not synchronize it C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1977 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [68.136 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1788 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [65.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 [BeforeEach] should trigger a push [BeforeEach] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:746 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:754 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:748 @ 10/30/23 04:42:09.881 ------------------------------ + [129.535 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4466 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [56.205 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1788 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [116.250 seconds] odo dev command tests when running odo dev and multiple env variables are set - without metadata.name should be able to exec command C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1717 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [69.232 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:178 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [2.617 seconds] odo devfile build-images command tests when using a Devfile with variable image names should build images with --var (push=true) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:437 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.202 seconds] odo dev command tests when Devfile contains metadata.projectType when running odo dev should set the correct value in labels of resources C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [86.189 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1077 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.769 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4220 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [FAILED] [55.013 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command [It] should execute the custom non-default build command successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3112 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output Timeline >> Created dir: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 Created dir: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194 Setting KUBECONFIG=C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194\config Running oc.exe with args [oc get project cmd-dev-test3112vlm -o jsonpath={.metadata.name}] and odo env: [] [oc] Error from server (NotFound): namespaces "cmd-dev-test3112vlm" not found Creating a new project: cmd-dev-test3112vlm Running oc.exe with args [oc new-project cmd-dev-test3112vlm] and odo env: [] [oc] Now using project "cmd-dev-test3112vlm" on server "https://c115-e.eu-de.containers.cloud.ibm.com:31900". [oc] [oc] You can add applications to this project with the 'new-app' command. For example, try: [oc] [oc] oc new-app rails-postgresql-example [oc] [oc] to build a new example application in Ruby. Or use kubectl to deploy a simple Kubernetes application: [oc] [oc] kubectl create deployment hello-node --image=k8s.gcr.io/serve_hostname [oc] Running oc.exe with args [oc get project] and odo env: [] [oc] NAME DISPLAY NAME STATUS [oc] calico-system Active [oc] cmd-delete-test151tmg Terminating [oc] cmd-delete-test178eff Active [oc] cmd-describe-component-test642qgv Active [oc] cmd-dev-api-server-test123pee Active [oc] cmd-dev-test1077xmg Active [oc] cmd-dev-test1282yed Active [oc] cmd-dev-test1717ssj Active [oc] cmd-dev-test1788ebc Terminating [oc] cmd-dev-test1788mjl Active [oc] cmd-dev-test1977pcu Terminating [oc] cmd-dev-test1987tez Active [oc] cmd-dev-test2058rgb Terminating [oc] cmd-dev-test2772qwv Active [oc] cmd-dev-test3112vlm Active [oc] cmd-dev-test3126hfd Active [oc] cmd-dev-test3269tnn Terminating [oc] cmd-dev-test3324hfw Active [oc] cmd-dev-test3771oqp Active [oc] cmd-dev-test4089vla Active [oc] cmd-dev-test4466ccl Terminating [oc] cmd-dev-test507wlt Terminating [oc] cmd-dev-test754jsu Active [oc] cmd-devfile-deploy-test226vra Active [oc] cmd-devfile-deploy-test601nuj Terminating [oc] cmd-devfile-deploy-test622tcn Terminating [oc] default Active [oc] generic-test107ssf Active [oc] ibm-cert-store Active [oc] ibm-odf-validation-webhook Active [oc] ibm-system Active [oc] jsbm-project Active [oc] kube-node-lease Active [oc] kube-public Active [oc] kube-system Active [oc] openshift Active [oc] openshift-apiserver Active [oc] openshift-apiserver-operator Active [oc] openshift-authentication Active [oc] openshift-authentication-operator Active [oc] openshift-cloud-credential-operator Active [oc] openshift-cloud-network-config-controller Active [oc] openshift-cluster-csi-drivers Active [oc] openshift-cluster-machine-approver Active [oc] openshift-cluster-node-tuning-operator Active [oc] openshift-cluster-samples-operator Active [oc] openshift-cluster-storage-operator Active [oc] openshift-cluster-version Active [oc] openshift-config Active [oc] openshift-config-managed Active [oc] openshift-config-operator Active [oc] openshift-console Active [oc] openshift-console-operator Active [oc] openshift-console-user-settings Active [oc] openshift-controller-manager Active [oc] openshift-controller-manager-operator Active [oc] openshift-dns Active [oc] openshift-dns-operator Active [oc] openshift-etcd Active [oc] openshift-etcd-operator Active [oc] openshift-image-registry Active [oc] openshift-infra Active [oc] openshift-ingress Active [oc] openshift-ingress-canary Active [oc] openshift-ingress-operator Active [oc] openshift-insights Active [oc] openshift-kube-apiserver Active [oc] openshift-kube-apiserver-operator Active [oc] openshift-kube-controller-manager Active [oc] openshift-kube-controller-manager-operator Active [oc] openshift-kube-proxy Active [oc] openshift-kube-scheduler Active [oc] openshift-kube-scheduler-operator Active [oc] openshift-kube-storage-version-migrator Active [oc] openshift-kube-storage-version-migrator-operator Active [oc] openshift-machine-api Active [oc] openshift-machine-config-operator Active [oc] openshift-marketplace Active [oc] openshift-monitoring Active [oc] openshift-multus Active [oc] openshift-network-diagnostics Active [oc] openshift-network-operator Active [oc] openshift-node Active [oc] openshift-operator-lifecycle-manager Active [oc] openshift-operators Active [oc] openshift-roks-metrics Active [oc] openshift-route-controller-manager Active [oc] openshift-service-ca Active [oc] openshift-service-ca-operator Active [oc] openshift-user-workload-monitoring Active [oc] qyzg-namespace Active [oc] tigera-operator Active [oc] yxnt-project Active Running oc.exe with args [oc create configmap config-map-for-cleanup --from-literal type=testing --from-literal team=odo -n cmd-dev-test3112vlm] and odo env: [] [oc] configmap/config-map-for-cleanup created Current working dir: C:\Users\Administrator.ANSIBLE-TEST-VS\4661\tests\integration Setting current dir to: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 Running odo.exe with args [odo preference remove registry DefaultDevfileRegistry -f] and odo env: [] [odo] I1030 04:42:33.594988 1588 implem.go:114] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194\preference.yaml [odo] Successfully removed registry [odo] I1030 04:42:33.597298 1588 implem.go:114] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194\preference.yaml [odo] I1030 04:42:33.600719 1588 segment.go:268] Checking telemetry enable status [odo] I1030 04:42:33.600719 1588 segment.go:286] Sending telemetry disabled by env variable Running odo.exe with args [odo preference add registry DefaultDevfileRegistry https://registry.stage.devfile.io] and odo env: [] [odo] I1030 04:42:33.733186 6304 implem.go:114] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194\preference.yaml [odo] New registry successfully added [odo] I1030 04:42:33.734958 6304 implem.go:114] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194\preference.yaml [odo] I1030 04:42:33.738186 6304 segment.go:268] Checking telemetry enable status [odo] I1030 04:42:33.738186 6304 segment.go:286] Sending telemetry disabled by env variable Setting current dir to: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 Replacing "nodejs-starter" with "huqxgu" in C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json Running odo.exe with args [odo dev --random-ports --api-server=false --build-command my-custom-build] and odo env: [ODO_LOG_LEVEL=4 ODO_TRACKING_CONSENT=no] [odo] I1030 04:42:33.940739 6364 version.go:37] executing [podman version --format json] [odo] I1030 04:42:33.941846 6364 clientset.go:243] no Podman client initialized: exec: "podman": executable file not found in %PATH% [odo] I1030 04:42:33.941846 6364 implem.go:114] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194\preference.yaml [odo] I1030 04:42:33.942213 6364 context.go:172] absolute devfile path: 'C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml' [odo] I1030 04:42:33.942213 6364 context.go:113] absolute devfile path: 'C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml' [odo] I1030 04:42:33.942811 6364 content.go:48] converted devfile YAML to JSON [odo] I1030 04:42:33.942811 6364 apiVersion.go:60] devfile schemaVersion: '2.0.0' [odo] I1030 04:42:33.942811 6364 helper.go:56] devfile apiVersion '2.0.0' is supported [odo] I1030 04:42:33.947825 6364 schema.go:61] validated devfile schema [odo] I1030 04:42:33.949177 6364 validate.go:45] Successfully validated devfile sections [odo] I1030 04:42:33.949177 6364 validate.go:45] Successfully validated devfile sections [odo] I1030 04:42:34.131882 6364 alizer.go:104] Found components: [{huqxgu C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\ [{JavaScript [js node nodejs TypeScript] 100 [Express] [NodeJs Node.js] true false}] [3000]}] [odo] I1030 04:42:34.132022 6364 alizer.go:124] Path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831, Detected name: huqxgu, Sanitized name: huqxgu [odo] I1030 04:42:34.132022 6364 kclient.go:237] Checking if "projects" resource is supported [odo] __ [odo] / \__ Developing using the "huqxgu" Devfile [odo] \__/ \ Namespace: cmd-dev-test3112vlm [odo] / \__/ odo version: v3.15.0 (451e30740) [odo] \__/ [odo] [odo] - Running on the cluster in Dev mode [odo] I1030 04:42:34.212864 6364 kubedev.go:79] Creating new adapter [odo] I1030 04:42:34.212989 6364 kubedev.go:87] Creating inner-loop resources for the component [odo] I1030 04:42:34.212989 6364 watch.go:105] starting WatchAndPush, path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831, component: huqxgu, ignores [.git .odo .odo\odo-file-index.json] [odo] I1030 04:42:34.214028 6364 file_watcher.go:130] adding watch on path C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 [odo] I1030 04:42:34.214652 6364 file_watcher.go:130] adding watch on path C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.odo [odo] I1030 04:42:34.215043 6364 file_watcher.go:130] adding watch on path C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test [odo] I1030 04:42:34.230838 6364 watch.go:423] Copying files [] to pod [odo] I1030 04:42:34.231038 6364 context.go:172] absolute devfile path: 'C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml' [odo] I1030 04:42:34.231038 6364 context.go:113] absolute devfile path: 'C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml' [odo] I1030 04:42:34.231481 6364 content.go:48] converted devfile YAML to JSON [odo] I1030 04:42:34.231607 6364 apiVersion.go:60] devfile schemaVersion: '2.0.0' [odo] I1030 04:42:34.231607 6364 helper.go:56] devfile apiVersion '2.0.0' is supported [odo] I1030 04:42:34.236705 6364 schema.go:61] validated devfile schema [odo] I1030 04:42:34.237001 6364 validate.go:45] Successfully validated devfile sections [odo] I1030 04:42:34.237132 6364 components.go:69] component state: "" [odo] - Waiting for Kubernetes resources ... [odo] I1030 04:42:34.292478 6364 components.go:260] We are deploying these annotations: map[alpha.image.policy.openshift.io/resolve-names:* odo.dev/project-type:Not available] [odo] I1030 04:42:34.311748 6364 utils.go:149] No entrypoint defined for the component, setting container runtime entrypoint to 'tail -f /dev/null'. You can set a 'command' and/or 'args' for the component to override this default entrypoint. [odo] I1030 04:42:34.385414 6364 utils.go:77] Updating container runtime with mandatory volume mounts [odo] I1030 04:42:34.448896 6364 components.go:346] Creating deployment huqxgu-app [odo] I1030 04:42:34.448896 6364 components.go:347] The component name is huqxgu [odo] I1030 04:42:34.452624 6364 kclient.go:286] Kubernetes version is "v1.25.12+ba5cc25" [odo] I1030 04:42:34.452657 6364 kclient.go:298] Cluster has support for SSA: true [odo] Warning: would violate PodSecurity "restricted:v1.24": allowPrivilegeEscalation != false (container "runtime" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "runtime" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "runtime" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "runtime" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost") [odo] I1030 04:42:34.632267 6364 components.go:378] Successfully created component huqxgu [odo] I1030 04:42:34.672687 6364 components.go:390] Successfully created Service for component huqxgu [odo] I1030 04:42:34.700524 6364 all.go:46] starting to concurrently query 200 APIs [odo] I1030 04:42:34.700524 6364 all.go:62] fired up all goroutines to query APIs [odo] I1030 04:42:34.847547 6364 all.go:67] all goroutines have returned in 147.0229ms [odo] I1030 04:42:34.847547 6364 all.go:76] query result: objects=5 [odo] I1030 04:42:34.847687 6364 kclient.go:237] Checking if "servicebindings" resource is supported [odo] I1030 04:42:34.851838 6364 kclient.go:237] Checking if "clusterserviceversions" resource is supported [odo] I1030 04:42:34.855424 6364 service.go:75] Getting list of services [odo] I1030 04:42:34.855424 6364 operators.go:30] Fetching list of operators installed in cluster [odo] I1030 04:42:34.882212 6364 service.go:93] Getting services started from operator: service-binding-operator.v1.3.3 [odo] I1030 04:42:34.882212 6364 service.go:124] Getting instances of: bindablekinds.binding.operators.coreos.com [odo] I1030 04:42:34.891296 6364 service.go:124] Getting instances of: clusterworkloadresourcemappings.servicebinding.io [odo] I1030 04:42:34.894865 6364 service.go:124] Getting instances of: clusterworkloadresourcemappings.servicebinding.io [odo] I1030 04:42:34.898741 6364 service.go:124] Getting instances of: servicebindings.binding.operators.coreos.com [odo] I1030 04:42:34.946180 6364 service.go:124] Getting instances of: servicebindings.servicebinding.io [odo] I1030 04:42:34.962705 6364 service.go:124] Getting instances of: servicebindings.servicebinding.io [odo] I1030 04:42:35.027953 6364 components.go:134] Deployment has been updated to generation 1. Waiting new event... [odo] I1030 04:42:35.027953 6364 status.go:34] setting inner loop State "WaitDeployment" [odo] ================= [odo] ! Pod is Pending [odo] ================= [odo] I1030 04:42:35.051377 6364 watch.go:271] deployment watcher Event: Type: ADDED, name: huqxgu-app, rv: 96638084, generation: 1, pods: 0 [odo] I1030 04:42:35.052473 6364 watch.go:271] deployment watcher Event: Type: MODIFIED, name: huqxgu-app, rv: 96638091, generation: 1, pods: 0 [odo] I1030 04:42:35.053031 6364 watch.go:271] deployment watcher Event: Type: MODIFIED, name: huqxgu-app, rv: 96638096, generation: 1, pods: 0 [odo] I1030 04:42:35.053567 6364 watch.go:271] deployment watcher Event: Type: MODIFIED, name: huqxgu-app, rv: 96638112, generation: 1, pods: 0 [odo] I1030 04:42:35.351979 6364 watch.go:423] Copying files [] to pod [odo] I1030 04:42:35.352415 6364 context.go:172] absolute devfile path: 'C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml' [odo] I1030 04:42:35.352415 6364 context.go:113] absolute devfile path: 'C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml' [odo] I1030 04:42:35.353308 6364 content.go:48] converted devfile YAML to JSON [odo] I1030 04:42:35.353308 6364 apiVersion.go:60] devfile schemaVersion: '2.0.0' [odo] I1030 04:42:35.353308 6364 helper.go:56] devfile apiVersion '2.0.0' is supported [odo] I1030 04:42:35.360056 6364 schema.go:61] validated devfile schema [odo] I1030 04:42:35.360313 6364 validate.go:45] Successfully validated devfile sections [odo] I1030 04:42:35.360313 6364 components.go:69] component state: "WaitDeployment" [odo] I1030 04:42:35.376877 6364 components.go:260] We are deploying these annotations: map[alpha.image.policy.openshift.io/resolve-names:* odo.dev/project-type:Not available] [odo] I1030 04:42:35.391622 6364 utils.go:149] No entrypoint defined for the component, setting container runtime entrypoint to 'tail -f /dev/null'. You can set a 'command' and/or 'args' for the component to override this default entrypoint. [odo] I1030 04:42:35.489042 6364 utils.go:77] Updating container runtime with mandatory volume mounts [odo] I1030 04:42:35.596862 6364 components.go:346] Creating deployment huqxgu-app [odo] I1030 04:42:35.596862 6364 components.go:347] The component name is huqxgu [odo] I1030 04:42:35.596862 6364 components.go:350] The component already exists, attempting to update it [odo] I1030 04:42:35.596862 6364 components.go:352] Applying deployment [odo] I1030 04:42:35.663510 6364 components.go:361] Successfully updated component huqxgu [odo] I1030 04:42:35.698739 6364 components.go:748] Successfully update Service for component huqxgu [odo] I1030 04:42:35.714287 6364 all.go:46] starting to concurrently query 200 APIs [odo] I1030 04:42:35.714287 6364 all.go:62] fired up all goroutines to query APIs [odo] I1030 04:42:35.797290 6364 all.go:67] all goroutines have returned in 83.0028ms [odo] I1030 04:42:35.797381 6364 all.go:76] query result: objects=6 [odo] I1030 04:42:35.797381 6364 kclient.go:237] Checking if "servicebindings" resource is supported [odo] I1030 04:42:35.797381 6364 kclient.go:237] Checking if "clusterserviceversions" resource is supported [odo] I1030 04:42:35.797478 6364 service.go:75] Getting list of services [odo] I1030 04:42:35.797478 6364 operators.go:30] Fetching list of operators installed in cluster [odo] I1030 04:42:35.829140 6364 service.go:93] Getting services started from operator: cloud-native-postgresql.v1.18.7 [odo] I1030 04:42:35.829140 6364 service.go:124] Getting instances of: backups.postgresql.k8s.enterprisedb.io [odo] I1030 04:42:35.919303 6364 service.go:124] Getting instances of: clusters.postgresql.k8s.enterprisedb.io [odo] I1030 04:42:35.987116 6364 service.go:124] Getting instances of: poolers.postgresql.k8s.enterprisedb.io [odo] I1030 04:42:36.009546 6364 service.go:124] Getting instances of: scheduledbackups.postgresql.k8s.enterprisedb.io [odo] I1030 04:42:36.025065 6364 service.go:93] Getting services started from operator: service-binding-operator.v1.3.3 [odo] I1030 04:42:36.025065 6364 service.go:124] Getting instances of: bindablekinds.binding.operators.coreos.com [odo] I1030 04:42:36.034888 6364 service.go:124] Getting instances of: clusterworkloadresourcemappings.servicebinding.io [odo] I1030 04:42:36.038434 6364 service.go:124] Getting instances of: clusterworkloadresourcemappings.servicebinding.io [odo] I1030 04:42:36.042645 6364 service.go:124] Getting instances of: servicebindings.binding.operators.coreos.com [odo] I1030 04:42:36.091817 6364 service.go:124] Getting instances of: servicebindings.servicebinding.io [odo] I1030 04:42:36.103202 6364 service.go:124] Getting instances of: servicebindings.servicebinding.io [odo] I1030 04:42:36.174115 6364 components.go:141] Deployment has 0 ready replicas. Waiting new event... [odo] I1030 04:42:36.174115 6364 status.go:34] setting inner loop State "WaitDeployment" [odo] I1030 04:42:36.174115 6364 watch.go:271] deployment watcher Event: Type: MODIFIED, name: huqxgu-app, rv: 96638165, generation: 1, pods: 0 [odo] V Pod is Running [odo] I1030 04:42:39.084192 6364 watch.go:271] deployment watcher Event: Type: MODIFIED, name: huqxgu-app, rv: 96638337, generation: 1, pods: 1 [odo] I1030 04:42:39.387390 6364 watch.go:423] Copying files [] to pod [odo] I1030 04:42:39.387697 6364 context.go:172] absolute devfile path: 'C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml' [odo] I1030 04:42:39.387697 6364 context.go:113] absolute devfile path: 'C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml' [odo] I1030 04:42:39.388252 6364 content.go:48] converted devfile YAML to JSON [odo] I1030 04:42:39.388252 6364 apiVersion.go:60] devfile schemaVersion: '2.0.0' [odo] I1030 04:42:39.388363 6364 helper.go:56] devfile apiVersion '2.0.0' is supported [odo] I1030 04:42:39.393450 6364 schema.go:61] validated devfile schema [odo] I1030 04:42:39.393680 6364 validate.go:45] Successfully validated devfile sections [odo] I1030 04:42:39.393680 6364 components.go:69] component state: "WaitDeployment" [odo] I1030 04:42:39.409093 6364 components.go:260] We are deploying these annotations: map[alpha.image.policy.openshift.io/resolve-names:* odo.dev/project-type:Not available] [odo] I1030 04:42:39.416173 6364 utils.go:149] No entrypoint defined for the component, setting container runtime entrypoint to 'tail -f /dev/null'. You can set a 'command' and/or 'args' for the component to override this default entrypoint. [odo] I1030 04:42:39.477109 6364 utils.go:77] Updating container runtime with mandatory volume mounts [odo] I1030 04:42:39.537001 6364 components.go:346] Creating deployment huqxgu-app [odo] I1030 04:42:39.537001 6364 components.go:347] The component name is huqxgu [odo] I1030 04:42:39.537001 6364 components.go:350] The component already exists, attempting to update it [odo] I1030 04:42:39.537001 6364 components.go:352] Applying deployment [odo] I1030 04:42:39.677108 6364 components.go:361] Successfully updated component huqxgu [odo] I1030 04:42:39.716909 6364 components.go:748] Successfully update Service for component huqxgu [odo] I1030 04:42:39.732819 6364 all.go:46] starting to concurrently query 200 APIs [odo] I1030 04:42:39.733036 6364 all.go:62] fired up all goroutines to query APIs [odo] I1030 04:42:39.789105 6364 all.go:67] all goroutines have returned in 56.3937ms [odo] I1030 04:42:39.789105 6364 all.go:76] query result: objects=6 [odo] I1030 04:42:39.789105 6364 kclient.go:237] Checking if "servicebindings" resource is supported [odo] I1030 04:42:39.789105 6364 kclient.go:237] Checking if "clusterserviceversions" resource is supported [odo] I1030 04:42:39.789105 6364 service.go:75] Getting list of services [odo] I1030 04:42:39.789729 6364 operators.go:30] Fetching list of operators installed in cluster [odo] I1030 04:42:39.839351 6364 service.go:93] Getting services started from operator: cloud-native-postgresql.v1.18.7 [odo] I1030 04:42:39.839526 6364 service.go:124] Getting instances of: backups.postgresql.k8s.enterprisedb.io [odo] I1030 04:42:39.848839 6364 service.go:124] Getting instances of: clusters.postgresql.k8s.enterprisedb.io [odo] I1030 04:42:39.865981 6364 service.go:124] Getting instances of: poolers.postgresql.k8s.enterprisedb.io [odo] I1030 04:42:39.881812 6364 service.go:124] Getting instances of: scheduledbackups.postgresql.k8s.enterprisedb.io [odo] I1030 04:42:39.892414 6364 service.go:93] Getting services started from operator: service-binding-operator.v1.3.3 [odo] I1030 04:42:39.892414 6364 service.go:124] Getting instances of: bindablekinds.binding.operators.coreos.com [odo] I1030 04:42:39.897976 6364 service.go:124] Getting instances of: clusterworkloadresourcemappings.servicebinding.io [odo] I1030 04:42:39.902779 6364 service.go:124] Getting instances of: clusterworkloadresourcemappings.servicebinding.io [odo] I1030 04:42:39.907897 6364 service.go:124] Getting instances of: servicebindings.binding.operators.coreos.com [odo] I1030 04:42:39.925931 6364 service.go:124] Getting instances of: servicebindings.servicebinding.io [odo] I1030 04:42:39.937548 6364 service.go:124] Getting instances of: servicebindings.servicebinding.io [odo] I1030 04:42:40.038761 6364 file_indexer.go:400] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831, destBase: ., destFile: . [odo] I1030 04:42:40.038761 6364 file_indexer.go:406] Corrected destinations: base: . file: . [odo] I1030 04:42:40.039053 6364 file_indexer.go:400] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\.gitignore, destBase: ., destFile: .gitignore [odo] I1030 04:42:40.039166 6364 file_indexer.go:406] Corrected destinations: base: . file: .gitignore [odo] I1030 04:42:40.039292 6364 file_indexer.go:453] file added: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.gitignore [odo] I1030 04:42:40.039292 6364 file_indexer.go:400] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\.odo, destBase: ., destFile: .odo [odo] I1030 04:42:40.039292 6364 file_indexer.go:406] Corrected destinations: base: . file: .odo [odo] I1030 04:42:40.039425 6364 file_indexer.go:400] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\devfile.yaml, destBase: ., destFile: devfile.yaml [odo] I1030 04:42:40.039425 6364 file_indexer.go:406] Corrected destinations: base: . file: devfile.yaml [odo] I1030 04:42:40.039555 6364 file_indexer.go:453] file added: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml [odo] I1030 04:42:40.039555 6364 file_indexer.go:400] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\package.json, destBase: ., destFile: package.json [odo] I1030 04:42:40.039555 6364 file_indexer.go:406] Corrected destinations: base: . file: package.json [odo] I1030 04:42:40.039678 6364 file_indexer.go:453] file added: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json [odo] I1030 04:42:40.039834 6364 file_indexer.go:400] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\server.js, destBase: ., destFile: server.js [odo] I1030 04:42:40.039834 6364 file_indexer.go:406] Corrected destinations: base: . file: server.js [odo] I1030 04:42:40.039868 6364 file_indexer.go:453] file added: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\server.js [odo] I1030 04:42:40.039987 6364 file_indexer.go:400] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\test, destBase: ., destFile: test [odo] I1030 04:42:40.039987 6364 file_indexer.go:406] Corrected destinations: base: . file: test [odo] I1030 04:42:40.040101 6364 file_indexer.go:453] file added: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test [odo] I1030 04:42:40.040101 6364 file_indexer.go:400] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\test\test.js, destBase: ., destFile: test\test.js [odo] I1030 04:42:40.040101 6364 file_indexer.go:406] Corrected destinations: base: . file: test/test.js [odo] I1030 04:42:40.040330 6364 file_indexer.go:453] file added: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test\test.js [odo] I1030 04:42:40.040447 6364 sync.go:138] List of files to be deleted: +[] [odo] I1030 04:42:40.040447 6364 sync.go:140] List of files changed: +[C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\server.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test\test.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.gitignore C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json] [odo] I1030 04:42:40.040447 6364 sync.go:193] Push: componentName: huqxgu, path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831, files: [C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\server.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test\test.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.gitignore C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json], delFiles: [*], isForcePush: true [odo] I1030 04:42:40.040565 6364 sync.go:310] remote files marked for deletion are [/projects/*] [odo] I1030 04:42:40.040565 6364 exec.go:37] Executing command [rm -rf /projects/*] for pod: huqxgu-app-78d8d975b-jq727 in container: runtime [odo] - Syncing files into the container ... [odo] I1030 04:42:40.444230 6364 sync.go:233] Copying files C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\server.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test\test.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.gitignore C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json to pod [odo] I1030 04:42:40.444230 6364 copy.go:36] CopyFile arguments: localPath C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831, dest /projects/3028052831, targetPath /projects, copyFiles [C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\server.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test\test.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.gitignore C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json], globalExps [.git .odo .odo\odo-file-index.json] [odo] I1030 04:42:40.444381 6364 copy.go:63] Executing command tar xf - -C /projects --no-same-owner [odo] I1030 04:42:40.445165 6364 copy.go:96] makeTar arguments: srcPath: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831, destPath: /projects/3028052831, files: [C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\server.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test\test.js C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.gitignore C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json] [odo] I1030 04:42:40.445717 6364 copy.go:127] Got abs path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\server.js [odo] I1030 04:42:40.445717 6364 copy.go:128] Making C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 relative to C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\server.js [odo] I1030 04:42:40.445717 6364 copy.go:144] makeTar srcFile: 3028052831\server.js [odo] I1030 04:42:40.445717 6364 copy.go:145] makeTar destFile: server.js [odo] I1030 04:42:40.445717 6364 copy.go:165] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\server.js, destBase: \projects, destFile: server.js [odo] I1030 04:42:40.445717 6364 copy.go:171] Corrected destinations: base: /projects file: server.js [odo] I1030 04:42:40.856862 6364 copy.go:127] Got abs path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test [odo] I1030 04:42:40.857002 6364 copy.go:128] Making C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 relative to C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test [odo] I1030 04:42:40.857002 6364 copy.go:144] makeTar srcFile: 3028052831\test [odo] I1030 04:42:40.857002 6364 copy.go:145] makeTar destFile: test [odo] I1030 04:42:40.857002 6364 copy.go:165] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\test, destBase: \projects, destFile: test [odo] I1030 04:42:40.857002 6364 copy.go:171] Corrected destinations: base: /projects file: test [odo] I1030 04:42:40.857152 6364 copy.go:127] Got abs path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test\test.js [odo] I1030 04:42:40.857152 6364 copy.go:128] Making C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 relative to C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\test\test.js [odo] I1030 04:42:40.857152 6364 copy.go:144] makeTar srcFile: 3028052831\test\test.js [odo] I1030 04:42:40.857290 6364 copy.go:145] makeTar destFile: test\test.js [odo] I1030 04:42:40.857290 6364 copy.go:165] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\test\test.js, destBase: \projects, destFile: test\test.js [odo] I1030 04:42:40.857290 6364 copy.go:171] Corrected destinations: base: /projects file: test/test.js [odo] I1030 04:42:40.858082 6364 copy.go:127] Got abs path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.gitignore [odo] I1030 04:42:40.858082 6364 copy.go:128] Making C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 relative to C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\.gitignore [odo] I1030 04:42:40.858082 6364 copy.go:144] makeTar srcFile: 3028052831\.gitignore [odo] I1030 04:42:40.858082 6364 copy.go:145] makeTar destFile: .gitignore [odo] I1030 04:42:40.858082 6364 copy.go:165] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\.gitignore, destBase: \projects, destFile: .gitignore [odo] I1030 04:42:40.858082 6364 copy.go:171] Corrected destinations: base: /projects file: .gitignore [odo] I1030 04:42:40.858602 6364 copy.go:127] Got abs path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml [odo] I1030 04:42:40.858602 6364 copy.go:128] Making C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 relative to C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\devfile.yaml [odo] I1030 04:42:40.858602 6364 copy.go:144] makeTar srcFile: 3028052831\devfile.yaml [odo] I1030 04:42:40.858602 6364 copy.go:145] makeTar destFile: devfile.yaml [odo] I1030 04:42:40.858602 6364 copy.go:165] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\devfile.yaml, destBase: \projects, destFile: devfile.yaml [odo] I1030 04:42:40.858602 6364 copy.go:171] Corrected destinations: base: /projects file: devfile.yaml [odo] I1030 04:42:40.859403 6364 copy.go:127] Got abs path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json [odo] I1030 04:42:40.859403 6364 copy.go:128] Making C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 relative to C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831\package.json [odo] I1030 04:42:40.859403 6364 copy.go:144] makeTar srcFile: 3028052831\package.json [odo] I1030 04:42:40.859403 6364 copy.go:145] makeTar destFile: package.json [odo] I1030 04:42:40.859558 6364 copy.go:165] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 3028052831\package.json, destBase: \projects, destFile: package.json [odo] I1030 04:42:40.859558 6364 copy.go:171] Corrected destinations: base: /projects file: package.json [odo] V Syncing files into the container [1s] [odo] I1030 04:42:41.062865 6364 kubeexec.go:40] GetProcessInfoForCommand for "devrun" [odo] I1030 04:42:41.062865 6364 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_devrun.pid || true] for pod: huqxgu-app-78d8d975b-jq727 in container: runtime [odo] I1030 04:42:41.516584 6364 exec.go:96] cat: /opt/odo/.odo_cmd_devrun.pid: No such file or directory [odo] I1030 04:42:41.519559 6364 innerloop.go:131] running=false, execRequired=true [odo] - Building your application in container (command: my-custom-build) ... [odo] I1030 04:42:41.519559 6364 exec.go:37] Executing command [/bin/sh -c cd ${PROJECTS_ROOT} && (echo waiting for one second before starting & sleep 1; mkdir /projects/file-from-my-custom-build && npm install) 1>>/proc/1/fd/1 2>>/proc/1/fd/2] for pod: huqxgu-app-78d8d975b-jq727 in container: runtime [odo] I1030 04:42:45.805565 6364 exec.go:54] ExecuteCommand returned an an err: error while streaming command: command terminated with exit code 1. for command '[/bin/sh -c cd ${PROJECTS_ROOT} && (echo waiting for one second before starting & sleep 1; mkdir /projects/file-from-my-custom-build && npm install) 1>>/proc/1/fd/1 2>>/proc/1/fd/2]' [odo] stdout: [] [odo] stderr: [] [odo] X Building your application in container (command: my-custom-build) [4s] [odo] waiting for one second before starting [odo] npm ERR! Unexpected end of JSON input while parsing near '...MEUCIQCunWiseqob+u+OP' [odo] [odo] npm ERR! A complete log of this run can be found in: [odo] npm ERR! /opt/app-root/src/.npm/_logs/2023-10-30T09_42_45_684Z-debug.log [odo] I1030 04:42:45.890562 6364 status.go:34] setting inner loop State "Ready" [odo] I1030 04:42:45.890562 6364 watch.go:437] Error from Push: watch command was unable to push component: unable to exec command [/bin/sh -c cd ${PROJECTS_ROOT} && (echo waiting for one second before starting & sleep 1; mkdir /projects/file-from-my-custom-build && npm install) 1>>/proc/1/fd/1 2>>/proc/1/fd/2]: error while streaming command: command terminated with exit code 1 [odo] Error occurred on Push - watch command was unable to push component: unable to exec command [/bin/sh -c cd ${PROJECTS_ROOT} && (echo waiting for one second before starting & sleep 1; mkdir /projects/file-from-my-custom-build && npm install) 1>>/proc/1/fd/1 2>>/proc/1/fd/2]: error while streaming command: command terminated with exit code 1 [odo] [odo] [odo] - Dev mode [odo] Status: [odo] Watching for changes in the current directory C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 [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] I1030 04:42:45.890562 6364 watch.go:271] deployment watcher Event: Type: MODIFIED, name: huqxgu-app, rv: 96638367, generation: 1, pods: 1 [odo] I1030 04:42:46.002866 6364 watch.go:348] filesystem watch event: CREATE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3028052831\\.odo\\odo-file-index.json" [odo] I1030 04:42:46.003481 6364 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\3028052831\\.odo\\odo-file-index.json" STEP: checking the output of the command @ 10/30/23 04:42:53.866 [odo] I1030 04:42:53.868325 6364 watch.go:333] Dev mode interrupted by user [odo] I1030 04:42:53.868837 6364 implem.go:114] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194\preference.yaml [odo] I1030 04:42:53.871550 6364 segment.go:268] Checking telemetry enable status [odo] I1030 04:42:53.871550 6364 segment.go:286] Sending telemetry disabled by env variable [odo] Cleaning resources, please wait [odo] I1030 04:42:53.994273 6364 all.go:46] starting to concurrently query 200 APIs [odo] I1030 04:42:53.994549 6364 all.go:62] fired up all goroutines to query APIs [odo] I1030 04:42:54.730677 6364 all.go:67] all goroutines have returned in 736.4041ms [odo] I1030 04:42:54.730677 6364 all.go:76] query result: objects=609 [FAILED] in [It] - C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_generic.go:81 @ 10/30/23 04:43:26.554 Running oc.exe with args [oc get project cmd-dev-test3112vlm -o jsonpath={.metadata.name}] and odo env: [] [oc] cmd-dev-test3112vlmDeleting project: cmd-dev-test3112vlm Running oc.exe with args [oc delete project cmd-dev-test3112vlm --wait=false] and odo env: [] [oc] project.project.openshift.io "cmd-dev-test3112vlm" deleted Setting current dir to: C:\Users\Administrator.ANSIBLE-TEST-VS\4661\tests\integration Deleting dir: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 Deleting dir: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\835314194 << Timeline [FAILED] Expected : __ / \__ Developing using the "huqxgu" Devfile \__/ \ Namespace: cmd-dev-test3112vlm / \__/ odo version: v3.15.0 (451e30740) \__/ - Running on the cluster in Dev mode - Waiting for Kubernetes resources ... ================= ! Pod is Pending ================= V Pod is Running - Syncing files into the container ... V Syncing files into the container [1s] - Building your application in container (command: my-custom-build) ... X Building your application in container (command: my-custom-build) [4s] Error occurred on Push - watch command was unable to push component: unable to exec command [/bin/sh -c cd ${PROJECTS_ROOT} && (echo waiting for one second before starting & sleep 1; mkdir /projects/file-from-my-custom-build && npm install) 1>>/proc/1/fd/1 2>>/proc/1/fd/2]: error while streaming command: command terminated with exit code 1 - Dev mode Status: Watching for changes in the current directory C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3028052831 Keyboard Commands: [Ctrl+c] - Exit and delete resources from the cluster [p] - Manually apply local changes to the application on the cluster to contain substring : Executing the application (command: devrun) In [It] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_generic.go:81 @ 10/30/23 04:43:26.554 ------------------------------ S ------------------------------ + [66.768 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1987 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.183 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:123 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.811 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_build_images_test.go:364 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [3.952 seconds] odo list with devfile listing non-odo managed components when a non-odo managed component is deployed should list the component in JSON C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:47 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [26.786 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:428 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [67.299 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3126 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [2.698 seconds] odo dev command tests when a component is bootstrapped should fail when using --no-commands and --build-command and/or --run-command together C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:233 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSS ------------------------------ + [67.144 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1282 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.476 seconds] odo dev command tests when running odo dev and composite command are nested - without metadata.name should execute all commands in composite commmand C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2674 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [45.484 seconds] odo dev command tests when running odo dev --no-watch and build command throws an error should error out with some log C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2898 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.008 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_deploy_test.go:502 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [4.167 seconds] odo create/delete/list/set namespace/project tests create project should fail to create project C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:63 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [14.944 seconds] odo create/delete/list/set namespace/project tests delete project when force-deleting a valid project should successfully delete the project asynchronously C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_namespace_test.go:107 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [129.132 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2772 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [117.915 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_describe_component_test.go:642 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [106.268 seconds] odo dev command tests when a hotReload capable Run command is used with odo dev should execute the build and run commands C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3771 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [35.427 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:473 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [67.557 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_api_server_test.go:221 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.078 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:4089 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [69.770 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_delete_test.go:151 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S [66.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 [BeforeEach] should react on the Devfile modification (podman=false, manual=true, customPortForwarding=false, customAddress=true) [BeforeEach] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1353 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1379 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output [SKIPPED] This is a unix-terminal specific scenario, skipping In [BeforeEach] at: C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1356 @ 10/30/23 04:44:01.626 ------------------------------ + [66.618 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1987 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.083 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1282 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [155.953 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3324 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [103.061 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [57.214 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2966 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [82.866 seconds] odo dev command tests 1. devfile contains composite apply command when odo dev is running should execute the composite apply commands successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [82.486 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:2388 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [87.395 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) C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:1463 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [121.261 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_devfile_list_test.go:193 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [241.272 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 C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/integration/cmd_dev_test.go:3391 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ Summarizing 1 Failure: [FAIL] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command [It] should execute the custom non-default build command successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4661/tests/helper/helper_generic.go:81 Ran 390 of 956 Specs in 1485.035 seconds FAIL! -- 389 Passed | 1 Failed | 0 Pending | 566 Skipped Ginkgo ran 1 suite in 25m2.8174923s Test Suite Failed