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\4654\tests\integration ================================================================================================ Random Seed: 1698219261 - will randomize all specs Will run 135 of 956 specs Running in parallel across 7 processes SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [0.847 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/4654/tests/integration/generic_test.go:52 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ + [0.898 seconds] odo run command tests when directory is empty should error [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ S ------------------------------ + [0.946 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/4654/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.877 seconds] odo devfile registry command tests label nocluster Should fail with an error with no registries [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSSS ------------------------------ + [0.920 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/4654/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.650 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/4654/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 ------------------------------ + [1.795 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/4654/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 ------------------------------ SSSSSSSSSSSSSSSSSSS ------------------------------ + [1.045 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/4654/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 ------------------------------ SS ------------------------------ S [0.382 seconds] odo init interactive command tests label nocluster [It] should print automation command with proper values [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/interactive_init_test.go:184 @ 10/25/23 02:35:04.761 ------------------------------ SSSSSSSSS ------------------------------ + [1.881 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/4654/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 ------------------------------ S ------------------------------ + [2.400 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/4654/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 ------------------------------ SSSSSSSSS ------------------------------ + [1.134 seconds] odo preference and config command tests label nocluster check that help works should display help info [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SS ------------------------------ + [1.863 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/4654/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 ------------------------------ + [2.762 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/4654/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 ------------------------------ SSSSSSSSSSSSSSSSS ------------------------------ + [0.575 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/4654/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 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [0.562 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/4654/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 ------------------------------ SSSSSSSS ------------------------------ + [0.457 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/4654/tests/integration/generic_test.go:38 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [0.821 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/4654/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 ------------------------------ SSSSSSSSSSSSSSSSSS ------------------------------ + [0.406 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/4654/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 ------------------------------ SSSSSSSSS ------------------------------ + [0.518 seconds] odo generic label nocluster returns error when using an invalid command with --help [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/generic_test.go:92 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [0.475 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/4654/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 ------------------------------ S ------------------------------ + [0.388 seconds] odo generic label nocluster when running odo --help does not support the --kubeconfig flag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/generic_test.go:42 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.486 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/4654/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 ------------------------------ SSSSSS ------------------------------ + [3.976 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/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2247655176 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSS ------------------------------ S [0.279 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/4654/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/4654/tests/integration/interactive_init_test.go:412 @ 10/25/23 02:35:07.459 ------------------------------ SSSSSSSSSSS ------------------------------ + [0.437 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/4654/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 ------------------------------ SSS ------------------------------ + [0.667 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/4654/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 ------------------------------ + [1.138 seconds] odo run command tests when a component is bootstrapped should fail if platform is not available [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSSSSS ------------------------------ + [0.899 seconds] odo describe component command tests should fail, without cluster [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSSSSS ------------------------------ + [0.938 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/4654/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 ------------------------------ + [1.471 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/4654/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 ------------------------------ + [0.337 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/4654/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 ------------------------------ SSSSSSSSSSSSS ------------------------------ + [0.678 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/4654/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 ------------------------------ S ------------------------------ + [2.486 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/4654/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 ------------------------------ SSSSSSSSSSSSSS ------------------------------ + [6.797 seconds] odo init interactive command tests label nocluster should download correct devfile-starter [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2419899013 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSSSSS ------------------------------ + [0.654 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/4654/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 ------------------------------ SS ------------------------------ + [0.416 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/4654/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 ------------------------------ S ------------------------------ + [1.958 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/4654/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 ------------------------------ SSSS ------------------------------ + [2.315 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/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3245372299 << Captured StdOut/StdErr Output ------------------------------ SSSSSS ------------------------------ + [1.455 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/4654/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 ------------------------------ SSSSSSS ------------------------------ S [0.265 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/4654/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/4654/tests/integration/interactive_init_test.go:463 @ 10/25/23 02:35:11.104 ------------------------------ + [2.601 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/4654/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 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [2.447 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/4654/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 ------------------------------ + [3.850 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/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\597423725 << Captured StdOut/StdErr Output ------------------------------ + [0.559 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/4654/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 ------------------------------ + [0.557 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/4654/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 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [2.493 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/4654/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 ------------------------------ + [1.463 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [0.723 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/4654/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 ------------------------------ SSSS ------------------------------ + [0.791 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [0.345 seconds] odo generic label nocluster returns error when using an invalid command [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/generic_test.go:57 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [2.454 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/4654/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 ------------------------------ + [1.389 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/4654/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 ------------------------------ S ------------------------------ + [2.438 seconds] odo devfile registry command tests label nocluster Should list detailed information regarding nodejs [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SS ------------------------------ + [1.407 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/4654/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 ------------------------------ SSSSSSSSSSS ------------------------------ + [0.603 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/4654/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 ------------------------------ SSSSSSSSS ------------------------------ + [0.639 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/4654/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 ------------------------------ SSS ------------------------------ + [1.228 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/4654/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 ------------------------------ SSSS ------------------------------ + [0.526 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/4654/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 ------------------------------ S ------------------------------ + [0.508 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/4654/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 ------------------------------ SSSS ------------------------------ + [0.990 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/4654/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 ------------------------------ SSSSS ------------------------------ + [0.367 seconds] odo devfile registry command tests label nocluster should fail when adding a git based registry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSS ------------------------------ + [0.626 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/4654/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 ------------------------------ SSSSSSSSS ------------------------------ + [0.628 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [0.452 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/4654/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 ------------------------------ SSSSSSSSSS ------------------------------ + [0.552 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/4654/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 ------------------------------ SSSSSS ------------------------------ + [1.220 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/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\4019412820 << Captured StdOut/StdErr Output ------------------------------ + [1.498 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [2.486 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/4654/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 ------------------------------ + [2.625 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/4654/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 ------------------------------ SS ------------------------------ + [0.957 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/4654/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 ------------------------------ + [0.632 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/4654/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 ------------------------------ SSSSSSSSSSS ------------------------------ + [0.494 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [0.425 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [0.456 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/4654/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 ------------------------------ + [5.355 seconds] odo preference and config command tests label nocluster When configuring global config values should successfully updated [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSSSSSSSSSS ------------------------------ + [1.559 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/4654/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 ------------------------------ SSSSSSSSSSS ------------------------------ + [3.358 seconds] odo init interactive command tests label nocluster should download correct devfile [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\3188004089 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [0.532 seconds] odo devfile registry command tests label nocluster when adding a registry should list newly added registry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [0.630 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/4654/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 ------------------------------ SSSSSSSSSSSSS ------------------------------ + [0.378 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/4654/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 ------------------------------ SSSSSSSSSSSS ------------------------------ + [2.356 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/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2202951246 << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [2.642 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/4654/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 ------------------------------ + [0.427 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/4654/tests/integration/generic_test.go:184 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [1.312 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/4654/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 ------------------------------ SSSSSSSSSSSSS ------------------------------ + [2.387 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/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1896251890 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [0.401 seconds] odo generic Experimental Mode when experimental mode is enabled should display warning message [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/generic_test.go:233 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.451 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/4654/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 ------------------------------ SSSSS ------------------------------ + [1.509 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/4654/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 ------------------------------ + [1.417 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/4654/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 ------------------------------ SSSSSSSS ------------------------------ + [0.548 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/4654/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 ------------------------------ + [0.424 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/4654/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 ------------------------------ SSS ------------------------------ + [1.006 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/4654/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 ------------------------------ SSS ------------------------------ + [2.580 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/4654/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 ------------------------------ + [0.712 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/4654/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 ------------------------------ SSSSSSSSSSSSSS ------------------------------ + [0.533 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/4654/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.683 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/4654/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.441 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/4654/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 ------------------------------ S ------------------------------ + [2.439 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/4654/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 ------------------------------ + [1.395 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/4654/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 ------------------------------ S ------------------------------ + [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 an error should not run 'odo build-images --push' [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSS ------------------------------ + [1.439 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [0.548 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/4654/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 ------------------------------ + [3.422 seconds] odo init interactive command tests label nocluster should not fail when using -v flag [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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\4654\bin\odo.exe init -v 4' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\4162648910 << Captured StdOut/StdErr Output ------------------------------ SSSSSSSSSSSSS ------------------------------ + [1.460 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/4654/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 ------------------------------ SSSSSSSSSSS ------------------------------ + [4.522 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/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\4052781058 << Captured StdOut/StdErr Output ------------------------------ SSSSSSS ------------------------------ + [2.278 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/4654/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 ------------------------------ + [0.464 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/4654/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 ------------------------------ SSSSSSSSSS ------------------------------ + [1.422 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/4654/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 ------------------------------ S ------------------------------ + [0.701 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/4654/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 ------------------------------ SSSSSSSSSSSSSSSS ------------------------------ + [0.567 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/4654/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 ------------------------------ SSS ------------------------------ + [0.521 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/4654/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.458 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/4654/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 ------------------------------ SSSSSSSSSSS ------------------------------ + [0.328 seconds] odo create/delete/list/set namespace/project tests list project should fail, without cluster [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSSSSSSSSSSS ------------------------------ + [2.703 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/4654/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 ------------------------------ + [2.511 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/4654/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 ------------------------------ SSSSSSSSSSSS ------------------------------ + [0.397 seconds] odo create/delete/list/set namespace/project tests list namespace should fail, without cluster [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSSSSSSSSSSSS ------------------------------ + [2.579 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/4654/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.176 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/4654/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 ------------------------------ SSSSSSSSSSSSSSSSSSSSSSSSSSS ------------------------------ + [0.505 seconds] odo devfile registry command tests label nocluster when adding a registry should successfully delete registry [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSSSSSSSSS ------------------------------ + [0.412 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/4654/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 ------------------------------ SSS ------------------------------ + [0.823 seconds] odo generic label nocluster returns JSON error [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/generic_test.go:62 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ + [0.428 seconds] odo devfile registry command tests label nocluster Should list all default registries [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSS ------------------------------ + [0.434 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/4654/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 ------------------------------ + [0.390 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/4654/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.408 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/4654/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 ------------------------------ + [2.655 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/4654/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 ------------------------------ + [1.486 seconds] odo devfile registry command tests label nocluster Should list java-openliberty specifically [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [4.665 seconds] odo devfile init command tests label nocluster should fail [nocluster] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [2.575 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/4654/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 ------------------------------ + [3.910 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/4654/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\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2343797985 << Captured StdOut/StdErr Output ------------------------------ Ran 128 of 956 Specs in 27.800 seconds SUCCESS! -- 128 Passed | 0 Failed | 0 Pending | 828 Skipped Ginkgo ran 1 suite in 1m8.9751428s 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\4654\tests\integration ================================================================================================ Random Seed: 1698219345 - will randomize all specs Will run 504 of 956 specs Running in parallel across 16 processes SSSSSSSSSSSSSSSSS ------------------------------ + [18.487 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/4654/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 [19.769 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/4654/tests/integration/cmd_dev_test.go:1815 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:1818 @ 10/25/23 02:36:20.811 ------------------------------ S [19.167 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/4654/tests/integration/interactive_init_test.go:708 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/interactive_init_test.go:710 @ 10/25/23 02:36:20.75 ------------------------------ S ------------------------------ + [21.911 seconds] odo create/delete/list/set namespace/project tests create project should fail to create project C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSS ------------------------------ + [5.330 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/4654/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 ------------------------------ + [24.761 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/4654/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 ------------------------------ SSS ------------------------------ + [24.725 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/4654/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 ------------------------------ S ------------------------------ + [25.797 seconds] odo create/delete/list/set namespace/project tests create project should successfully create the project C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [34.614 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/4654/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 ------------------------------ + [57.963 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/4654/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 ------------------------------ S ------------------------------ + [3.419 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/4654/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 ------------------------------ + [81.364 seconds] odo delete command tests when a component is bootstrapped using a devfile.yaml with URI-referenced Kubernetes components when the component is running in both DEV and DEPLOY mode and dev mode is killed when the component is deleted while having access to the devfile.yaml should delete the appropriate resources C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSSSSS ------------------------------ + [2.272 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/4654/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 ------------------------------ S ------------------------------ + [84.902 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/4654/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 ------------------------------ + [86.039 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/4654/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 ------------------------------ + [3.774 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/4654/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 ------------------------------ + [6.065 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/4654/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 ------------------------------ S ------------------------------ + [67.723 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/4654/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 ------------------------------ SSSSSS ------------------------------ + [91.252 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/4654/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 ------------------------------ + [67.290 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/4654/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 ------------------------------ + [67.092 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/4654/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 ------------------------------ + [3.318 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/4654/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 ------------------------------ S [71.921 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/4654/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/4654/tests/integration/cmd_dev_test.go:1505 @ 10/25/23 02:37:10.162 ------------------------------ + [108.571 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/4654/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 ------------------------------ S [2.218 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/4654/tests/integration/cmd_devfile_registry_test.go:216 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_devfile_registry_test.go:218 @ 10/25/23 02:37:52.042 ------------------------------ SSSS ------------------------------ + [4.368 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/4654/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 ------------------------------ SSSSSS ------------------------------ + [36.707 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/4654/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 ------------------------------ + [135.715 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/4654/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 ------------------------------ + [118.364 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/4654/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 [56.996 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/4654/tests/integration/cmd_dev_test.go:1353 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:1356 @ 10/25/23 02:37:52.392 ------------------------------ + [144.858 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/4654/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 ------------------------------ SS ------------------------------ Progress Report for Ginkgo Process #13 Automatically polling progress: 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 (Spec Runtime: 2m3.151s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_debug_test.go:163 In [BeforeEach] (Node Runtime: 2m0.003s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_debug_test.go:138 Begin Captured GinkgoWriter Output >> ... [odo] I1025 02:38:24.337993 5604 exec.go:96] 5: F30811AC:B89A 221F1068:01BB 06 00000000:00000000 03:0000033E 00000000 0 0 0 3 0000000000000000 [odo] I1025 02:38:24.337993 5604 exec.go:96] 6: F30811AC:B88E 221F1068:01BB 06 00000000:00000000 03:0000033E 00000000 0 0 0 3 0000000000000000 [odo] I1025 02:38:24.337993 5604 exec.go:96] 7: F30811AC:B880 221F1068:01BB 06 00000000:00000000 03:0000033E 00000000 0 0 0 3 0000000000000000 [odo] I1025 02:38:24.337993 5604 exec.go:96] 8: F30811AC:B8B4 221F1068:01BB 06 00000000:00000000 03:0000033E 00000000 0 0 0 3 0000000000000000 [odo] I1025 02:38:24.337993 5604 exec.go:96] 9: F30811AC:B876 221F1068:01BB 06 00000000:00000000 03:0000033E 00000000 0 0 0 3 0000000000000000 [odo] I1025 02:38:24.337993 5604 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 02:38:24.339387 5604 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1025 02:38:24.339387 5604 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 02:38:24.350273 5604 port.go:319] port 3000 not listening in container "runtime" [odo] I1025 02:38:24.350273 5604 port.go:319] port 5858 not listening in container "runtime" << End Captured GinkgoWriter Output Spec Goroutine goroutine 149 [select, 2 minutes] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000555260, {0x2a08dc8?, 0xc001263770}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000555260, {0x2a08dc8, 0xc001263770}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x263db8b, 0xf}, 0x0?, 0x4?, 0xc001263740) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.StartDevMode({{0x0, 0x0, 0x0}, {0xc00087ca70, 0x1, 0x1}, 0x0, 0x0, 0x0, 0x0, ...}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:192 > github.com/redhat-developer/odo/tests/integration.glob..func6.4.1() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_debug_test.go:149 | helper.ReplaceString("package.json", "node server.js", "node server-debug/server.js") | var err error > devSession, err = helper.StartDevMode(helper.DevSessionOpts{ | RunOnPodman: podman, | CmdlineArgs: []string{"--debug"}, github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2052365, 0xc001242900}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [3.795 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/4654/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 ------------------------------ + [25.244 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/4654/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 ------------------------------ + [129.824 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/4654/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 ------------------------------ S ------------------------------ + [69.073 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/4654/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 ------------------------------ S ------------------------------ + [161.554 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/4654/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 ------------------------------ SSS ------------------------------ + [3.532 seconds] odo create/delete/list/set namespace/project tests list namespace should successfully list all the namespaces C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [56.542 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/4654/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 ------------------------------ + [23.944 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/4654/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 ------------------------------ + [4.467 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/4654/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 ------------------------------ SS ------------------------------ + [14.425 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/4654/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 ------------------------------ S ------------------------------ + [22.727 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/4654/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 ------------------------------ SS ------------------------------ + [2.597 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [5.049 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/4654/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 ------------------------------ SSS ------------------------------ + [25.212 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/4654/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 ------------------------------ + [74.697 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/4654/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 ------------------------------ SSSS ------------------------------ + [3.680 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/4654/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 ------------------------------ + [168.487 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/4654/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 ------------------------------ + [56.725 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/4654/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 ------------------------------ S [3.456 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/4654/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/4654/tests/integration/cmd_devfile_deploy_test.go:603 @ 10/25/23 02:39:19.552 ------------------------------ + [117.827 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/4654/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 ------------------------------ + [116.052 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/4654/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 ------------------------------ + [118.354 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/4654/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 ------------------------------ SS ------------------------------ + [68.770 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/4654/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 ------------------------------ SSSS ------------------------------ + [3.064 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/4654/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 ------------------------------ + [118.649 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [58.082 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/4654/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 ------------------------------ + [5.628 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/4654/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 ------------------------------ SSS ------------------------------ + [57.696 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [56.320 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/4654/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 ------------------------------ + [57.356 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/4654/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 ------------------------------ + [57.934 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/4654/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 ------------------------------ + [5.321 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/4654/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 ------------------------------ + [3.725 seconds] odo dev command tests when directory is empty should error C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSS ------------------------------ + [140.084 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/4654/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 ------------------------------ + [4.161 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/4654/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 ------------------------------ + [24.996 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/4654/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 [3.484 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/4654/tests/integration/cmd_pref_config_test.go:377 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_pref_config_test.go:379 @ 10/25/23 02:40:01.312 ------------------------------ S [57.627 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/4654/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/4654/tests/integration/cmd_dev_test.go:1505 @ 10/25/23 02:39:34.404 ------------------------------ SSS ------------------------------ + [58.580 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/4654/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 ------------------------------ + [56.372 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/4654/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 ------------------------------ + [83.947 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/4654/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 ------------------------------ + [55.358 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/4654/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 ------------------------------ + [61.338 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/4654/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 ------------------------------ S [44.757 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/4654/tests/integration/cmd_dev_test.go:746 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:748 @ 10/25/23 02:40:05.301 ------------------------------ + [55.358 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/4654/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 ------------------------------ + [23.586 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/4654/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 ------------------------------ + [57.126 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/4654/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 ------------------------------ + [2.866 seconds] odo describe component command tests should fail, with default cluster mode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SS ------------------------------ + [84.600 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/4654/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 ------------------------------ + [57.106 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/4654/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 ------------------------------ SSS ------------------------------ + [4.480 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/4654/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 ------------------------------ SSS ------------------------------ + [3.925 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/4654/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 ------------------------------ + [3.667 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/4654/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 ------------------------------ SSSSSS ------------------------------ S [56.145 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/4654/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/4654/tests/integration/cmd_dev_test.go:1505 @ 10/25/23 02:40:39.531 ------------------------------ S ------------------------------ + [56.047 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/4654/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 ------------------------------ SS ------------------------------ + [127.622 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/4654/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 ------------------------------ + [117.754 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/4654/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 ------------------------------ + [25.549 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/4654/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 ------------------------------ S [3.708 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/4654/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/4654/tests/integration/cmd_dev_test.go:416 @ 10/25/23 02:41:25.587 ------------------------------ SS ------------------------------ + [119.965 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/4654/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 ------------------------------ + [78.829 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/4654/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 ------------------------------ SSS ------------------------------ + [20.451 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/4654/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 ------------------------------ + [56.583 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/4654/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 ------------------------------ + [118.946 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/4654/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 ------------------------------ + [117.272 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/4654/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 ------------------------------ + [87.298 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/4654/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 ------------------------------ + [86.532 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/4654/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 ------------------------------ SSSSSSSSSSS ------------------------------ + [116.354 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/4654/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 ------------------------------ SSSS ------------------------------ + [3.786 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/4654/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 ------------------------------ + [2.614 seconds] odo logs command tests when directory is empty should error C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSS ------------------------------ + [4.315 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/4654/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 ------------------------------ + [57.227 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/4654/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 ------------------------------ S ------------------------------ S [3.507 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/4654/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/4654/tests/integration/cmd_devfile_deploy_test.go:678 @ 10/25/23 02:42:12.144 ------------------------------ + [5.049 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/4654/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 ------------------------------ + [56.325 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/4654/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 ------------------------------ SSSSSS ------------------------------ + [66.489 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/4654/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 ------------------------------ + [45.442 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/4654/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 ------------------------------ + [57.762 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/4654/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 ------------------------------ + [2.430 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/4654/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 ------------------------------ + [23.568 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/4654/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 ------------------------------ + [116.014 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [3.651 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/4654/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 ------------------------------ + [69.379 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/4654/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 ------------------------------ S ------------------------------ + [4.902 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/4654/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 ------------------------------ + [109.099 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/4654/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 ------------------------------ + [87.987 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/4654/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.139 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/4654/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 ------------------------------ S ------------------------------ + [47.814 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/4654/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 ------------------------------ S ------------------------------ + [3.610 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/4654/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 ------------------------------ + [115.581 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/4654/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 ------------------------------ + [3.688 seconds] odo run command tests when a component is bootstrapped should fail if odo dev is not running C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [97.516 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/4654/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 ------------------------------ + [77.481 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/4654/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 ------------------------------ + [56.766 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/4654/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 ------------------------------ + [3.586 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/4654/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 ------------------------------ SSS ------------------------------ + [57.933 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/4654/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 ------------------------------ + [57.222 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/4654/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 ------------------------------ + [84.123 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/4654/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 ------------------------------ + [57.543 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/4654/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 ------------------------------ SS ------------------------------ + [14.724 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/4654/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 ------------------------------ + [56.449 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/4654/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 ------------------------------ + [23.670 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/4654/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 ------------------------------ SSSSSS ------------------------------ + [48.367 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/4654/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 ------------------------------ SSS ------------------------------ + [75.858 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/4654/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 ------------------------------ + [24.494 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/4654/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 ------------------------------ SSSS ------------------------------ + [57.378 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/4654/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 ------------------------------ + [5.829 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/4654/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 ------------------------------ + [6.304 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/4654/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 ------------------------------ + [85.123 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/4654/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 ------------------------------ S ------------------------------ + [3.702 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/4654/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 ------------------------------ S ------------------------------ + [67.852 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/4654/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 ------------------------------ + [137.185 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/4654/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 ------------------------------ + [116.080 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/4654/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 ------------------------------ + [84.016 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/4654/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 ------------------------------ + [64.500 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/4654/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 ------------------------------ + [56.431 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/4654/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.636 seconds] odo create/delete/list/set namespace/project tests set project should successfully set the project C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [4.880 seconds] odo create/delete/list/set namespace/project tests set namespace should successfully set the namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [23.603 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/4654/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 ------------------------------ + [2.730 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/4654/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 ------------------------------ Progress Report for Ginkgo Process #6 Automatically polling progress: odo dev command tests when doing odo dev and there is a env variable with spaces - without metadata.name should be able to exec command (Spec Runtime: 2m1.677s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:1743 In [It] (Node Runtime: 2m0.012s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:1743 Begin Captured GinkgoWriter Output >> ... [oc] 947164 drwxr-sr-x. 2 1002190000 1002190000 4096 Oct 25 07:42 test [odo] I1025 02:44:08.106856 5388 watch.go:333] Dev mode interrupted by user [odo] I1025 02:44:08.107114 5388 implem.go:114] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2392202072\preference.yaml [odo] I1025 02:44:08.107509 5388 segment.go:268] Checking telemetry enable status [odo] I1025 02:44:08.107509 5388 segment.go:286] Sending telemetry disabled by env variable [odo] Cleaning resources, please wait [odo] I1025 02:44:08.188340 5388 all.go:46] starting to concurrently query 200 APIs [odo] I1025 02:44:08.188561 5388 all.go:62] fired up all goroutines to query APIs [odo] I1025 02:44:08.882894 5388 all.go:67] all goroutines have returned in 694.5556ms [odo] I1025 02:44:08.882894 5388 all.go:76] query result: objects=610 << End Captured GinkgoWriter Output Spec Goroutine goroutine 400 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000840d20, {0x2a08b88?, 0xc0011acfc0}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000840d20, {0x2a08b88, 0xc0011acfc0}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc001589d70?, {0xc000abe710?, 0xc001589c38?, 0x2?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:263 github.com/redhat-developer/odo/tests/helper.RunDevMode.func1() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/helper/helper_dev.go:337 > github.com/redhat-developer/odo/tests/integration.glob..func7.13.2() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:1744 | | It("should be able to exec command", func() { > err := helper.RunDevMode(helper.DevSessionOpts{ | RunOnPodman: podman, | }, func(session *gexec.Session, out, err string, ports map[string]string) { github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0xbe315e, 0xc000a0b830}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [55.624 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/4654/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 ------------------------------ SSSSSSS ------------------------------ Progress Report for Ginkgo Process #12 Automatically polling progress: odo dev command tests when a component is bootstrapped ensure that index information is updated (Spec Runtime: 2m3.19s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:305 In [It] (Node Runtime: 2m0.002s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:305 Begin Captured GinkgoWriter Output >> ... [odo] [p] - Manually apply local changes to the application on the cluster [odo] I1025 02:44:23.358191 7328 watch.go:333] Dev mode interrupted by user [odo] I1025 02:44:23.358786 7328 implem.go:114] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1428241644\preference.yaml [odo] I1025 02:44:23.359470 7328 segment.go:268] Checking telemetry enable status [odo] I1025 02:44:23.359470 7328 segment.go:286] Sending telemetry disabled by env variable [odo] Cleaning resources, please wait [odo] I1025 02:44:23.483861 7328 all.go:46] starting to concurrently query 200 APIs [odo] I1025 02:44:23.483861 7328 all.go:62] fired up all goroutines to query APIs [odo] I1025 02:44:24.453024 7328 all.go:67] all goroutines have returned in 969.165ms [odo] I1025 02:44:24.453311 7328 all.go:76] query result: objects=610 << End Captured GinkgoWriter Output Spec Goroutine goroutine 329 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0007e5260, {0x2a08b88?, 0xc0002d8600}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0007e5260, {0x2a08b88, 0xc0002d8600}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc001899df8?, {0xc00077ef70?, 0xc001696420?, 0xc0006d21c0?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:263 github.com/redhat-developer/odo/tests/helper.RunDevMode.func1() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/helper/helper_dev.go:337 > github.com/redhat-developer/odo/tests/integration.glob..func7.4.14() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:306 | | It("ensure that index information is updated", func() { > err := helper.RunDevMode(helper.DevSessionOpts{}, func(session *gexec.Session, outContents, errContents string, ports map[string]string) { | indexAfterPush, err := util.ReadFileIndex(filepath.Join(commonVar.Context, ".odo", "odo-file-index.json")) | Expect(err).ToNot(HaveOccurred()) github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x2052365, 0xc0013907e0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [139.750 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/4654/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 ------------------------------ S ------------------------------ + [129.632 seconds] odo dev command tests when a component is bootstrapped ensure that index information is updated C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ S ------------------------------ + [74.232 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/4654/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 ------------------------------ S ------------------------------ + [77.715 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/4654/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 ------------------------------ + [4.380 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/4654/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 ------------------------------ + [76.721 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/4654/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 ------------------------------ SSSS ------------------------------ + [4.457 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/4654/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 ------------------------------ + [77.704 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/4654/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 ------------------------------ + [111.159 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/4654/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 ------------------------------ SS ------------------------------ + [83.733 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/4654/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 ------------------------------ S ------------------------------ + [2.828 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/4654/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 ------------------------------ + [3.736 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/4654/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 ------------------------------ + [55.732 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/4654/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 ------------------------------ + [107.666 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/4654/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 ------------------------------ + [55.399 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/4654/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 ------------------------------ + [117.199 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/4654/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\4654\bin\odo.exe dev --random-ports -v 4' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2675874726 << Captured StdOut/StdErr Output ------------------------------ + [3.670 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/4654/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 ------------------------------ + [115.980 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/4654/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.536 seconds] odo create/delete/list/set namespace/project tests create namespace should fail to create namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [116.057 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/4654/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 ------------------------------ S ------------------------------ + [67.620 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/4654/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 ------------------------------ + [109.085 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/4654/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 ------------------------------ SSS ------------------------------ + [58.572 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/4654/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 ------------------------------ SS ------------------------------ + [44.423 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/4654/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\4654\bin\odo.exe dev --random-ports' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1867151304 << Captured StdOut/StdErr Output ------------------------------ + [6.850 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/4654/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 ------------------------------ + [56.397 seconds] odo dev command tests when a component is bootstrapped should add annotation to use ImageStreams C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ S ------------------------------ + [4.773 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/4654/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 ------------------------------ + [4.445 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/4654/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 ------------------------------ + [5.246 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/4654/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 ------------------------------ SS ------------------------------ + [108.495 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/4654/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 ------------------------------ SSS ------------------------------ + [2.739 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/4654/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 ------------------------------ + [3.099 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/4654/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 ------------------------------ SS ------------------------------ + [4.111 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/4654/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 ------------------------------ SSSS ------------------------------ + [15.065 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/4654/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 ------------------------------ S ------------------------------ + [26.159 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/4654/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.291 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/4654/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 ------------------------------ + [10.492 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/4654/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 ------------------------------ SS ------------------------------ + [144.277 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/4654/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 ------------------------------ SSS ------------------------------ + [85.439 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/4654/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 ------------------------------ SS ------------------------------ + [5.619 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/4654/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 ------------------------------ + [117.483 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/4654/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 ------------------------------ + [35.411 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/4654/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 ------------------------------ + [57.782 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/4654/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 ------------------------------ + [23.739 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/4654/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 ------------------------------ Progress Report for Ginkgo Process #4 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.012s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:1077 In [BeforeEach] (Node Runtime: 2m0.005s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:1050 Begin Captured GinkgoWriter Output >> ... [odo] I1025 02:47:01.622057 2472 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 02:47:01.629973 2472 port.go:319] port 8080 not listening in container "runtime" [odo] I1025 02:47:05.370509 2472 exec.go:37] Executing command [/bin/sh -c cat /proc/net/tcp /proc/net/udp /proc/net/tcp6 /proc/net/udp6 || true] for pod: wbpuwo-app-847bd98447-vkdbl in container: runtime [odo] I1025 02:47:05.617197 2472 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1025 02:47:05.617197 2472 exec.go:96] 0: F40811AC:9D78 23011068:01BB 06 00000000:00000000 03:00000E5A 00000000 0 0 0 3 0000000000000000 [odo] I1025 02:47:05.617197 2472 exec.go:96] sl local_address rem_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 02:47:05.617197 2472 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode [odo] I1025 02:47:05.617197 2472 exec.go:96] 0: 00000000000000000000000000000000:0BB8 00000000000000000000000000000000:0000 0A 00000000:00000000 00:00000000 00000000 1002670000 0 1530458465 1 0000000000000000 100 0 0 10 0 [odo] I1025 02:47:05.617197 2472 exec.go:96] sl local_address remote_address st tx_queue rx_queue tr tm->when retrnsmt uid timeout inode ref pointer drops [odo] I1025 02:47:05.631268 2472 port.go:319] port 8080 not listening in container "runtime" << End Captured GinkgoWriter Output Spec Goroutine goroutine 635 [select, 2 minutes] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0000bc9a0, {0x2a08dc8?, 0xc000c408a0}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0000bc9a0, {0x2a08dc8, 0xc000c408a0}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x262ef94, 0x8}, 0xc000429400?, 0xc0004293e0?, 0xc0012d8f60) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc0005bad80) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:279 > github.com/redhat-developer/odo/tests/integration.glob..func7.5.1.1() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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({0xbe315e, 0xc000ca9620}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [6.590 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/4654/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.615 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/4654/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 ------------------------------ + [68.718 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/4654/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 ------------------------------ SSSSSSSSS ------------------------------ + [67.981 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/4654/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 ------------------------------ + [57.496 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/4654/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 ------------------------------ + [66.518 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/4654/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 ------------------------------ + [57.445 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/4654/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 ------------------------------ + [57.597 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/4654/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 ------------------------------ + [4.546 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/4654/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 ------------------------------ + [5.342 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/4654/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 ------------------------------ SSS ------------------------------ + [2.646 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/4654/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 ------------------------------ + [97.938 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/4654/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 ------------------------------ + [55.753 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/4654/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.852 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/4654/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 ------------------------------ S ------------------------------ + [87.193 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/4654/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 ------------------------------ SSS ------------------------------ + [56.320 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/4654/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 ------------------------------ + [3.842 seconds] odo generic executing odo version command should only print client info when using --client flag C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/generic_test.go:201 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [4.507 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/4654/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 ------------------------------ SSSS ------------------------------ + [3.490 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/4654/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 ------------------------------ SS ------------------------------ + [56.744 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/4654/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 ------------------------------ SS ------------------------------ + [5.677 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/4654/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 ------------------------------ + [47.542 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/4654/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 ------------------------------ + [56.603 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/4654/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 ------------------------------ SSS ------------------------------ + [9.972 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/4654/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 ------------------------------ + [3.553 seconds] odo create/delete/list/set namespace/project tests create namespace should successfully create the namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ S ------------------------------ + [58.711 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/4654/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 ------------------------------ + [3.515 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/4654/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 ------------------------------ + [206.616 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/4654/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 ------------------------------ SSSSSS ------------------------------ + [48.889 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/4654/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 ------------------------------ + [4.753 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/4654/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 ------------------------------ SS ------------------------------ + [95.579 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/4654/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 ------------------------------ + [66.500 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/4654/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 ------------------------------ + [26.584 seconds] odo dev interactive command tests when a component is bootstrapped should sync files when p is pressed C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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\4654\bin\odo.exe dev --random-ports --no-watch' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\173796504 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ S [1.998 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/4654/tests/integration/cmd_devfile_init_test.go:586 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_devfile_init_test.go:588 @ 10/25/23 02:49:02.924 ------------------------------ S [2.215 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/4654/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/4654/tests/integration/cmd_dev_test.go:93 @ 10/25/23 02:49:05.043 ------------------------------ + [66.703 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/4654/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 ------------------------------ + [57.297 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/4654/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 ------------------------------ + [117.533 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/4654/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 ------------------------------ S [56.999 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/4654/tests/integration/cmd_dev_test.go:1353 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:1356 @ 10/25/23 02:48:55.453 ------------------------------ + [116.544 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/4654/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 ------------------------------ + [3.605 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/4654/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 ------------------------------ + [56.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=true, customPortForwarding=true, customAddress=false) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSSSS ------------------------------ + [56.250 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/4654/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 ------------------------------ + [117.732 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/4654/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 ------------------------------ + [136.914 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/4654/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 ------------------------------ S ------------------------------ Progress Report for Ginkgo Process #6 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: 3m53.012s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_debug_test.go:288 In [It] (Node Runtime: 2m0.012s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_debug_test.go:288 At [By Step] cleaning up the resources on ending the session (Step Runtime: 27.432s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_debug_test.go:326 Begin Captured GinkgoWriter Output >> ... [odo] I1025 02:49:24.270709 6868 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_start-debug.pid || true] for pod: aopdle-app-69ff9555cd-c8c5r in container: runtime [odo] I1025 02:49:24.271048 6868 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-debug-test288nzn/pods/aopdle-app-69ff9555cd-c8c5r/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Fopt%2Fodo%2F.odo_cmd_start-debug.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_start-debug.pid || true]' [odo] stdout: [] [odo] stderr: [] [odo] I1025 02:49:24.271156 6868 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] X Finished executing the application (command: start-debug) [1m] [odo] I1025 02:49:24.338988 6868 all.go:46] starting to concurrently query 200 APIs [odo] I1025 02:49:24.339571 6868 all.go:62] fired up all goroutines to query APIs [odo] I1025 02:49:25.067513 6868 all.go:67] all goroutines have returned in 728.5252ms [odo] I1025 02:49:25.067513 6868 all.go:76] query result: objects=652 << End Captured GinkgoWriter Output Spec Goroutine goroutine 455 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000304000, {0x2a08b88?, 0xc000126ae0}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000304000, {0x2a08b88, 0xc000126ae0}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc000097da0?, {0xc000aa4040?, 0x0?, 0x0?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:263 > github.com/redhat-developer/odo/tests/integration.glob..func6.7.2.8() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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(0xc00021c000, {0x268cbac, 0x2f}, {0xc0017b3e70, 0x1, 0xaf6ff8?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:309 github.com/onsi/ginkgo/v2.By({0x268cbac?, 0xadad9d?}, {0xc0017b3e70?, 0x1a8?, 0xc00005a6f0?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/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({0xbe315e, 0xc000ab1830}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [117.135 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/4654/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 ------------------------------ + [4.721 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/4654/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 ------------------------------ + [5.348 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/4654/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 ------------------------------ + [244.104 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/4654/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 ------------------------------ + [5.170 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/4654/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 ------------------------------ + [136.172 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/4654/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 ------------------------------ + [79.884 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/4654/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\4654\bin\odo.exe dev --random-ports' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1882412066 << Captured StdOut/StdErr Output ------------------------------ SSS ------------------------------ + [105.661 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/4654/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 ------------------------------ + [3.936 seconds] odo create/delete/list/set namespace/project tests set project should not succeed to set the project C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ S ------------------------------ + [5.445 seconds] odo devfile deploy command tests when recording telemetry data should record the telemetry data correctly C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [5.119 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/4654/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\4654\bin\odo.exe deploy -v 4' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1697169771 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [57.663 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/4654/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 ------------------------------ SSSSSSS ------------------------------ + [4.346 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/4654/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 ------------------------------ + [66.541 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/4654/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 ------------------------------ SSSS ------------------------------ + [57.249 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/4654/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 ------------------------------ S ------------------------------ + [5.267 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/4654/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 ------------------------------ + [2.245 seconds] odo create/delete/list/set namespace/project tests list project should successfully list all the projects C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SS ------------------------------ + [57.179 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/4654/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 ------------------------------ + [57.287 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/4654/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 ------------------------------ + [56.268 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/4654/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 ------------------------------ S ------------------------------ S [3.323 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/4654/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/4654/tests/integration/cmd_devfile_deploy_test.go:603 @ 10/25/23 02:50:41.232 ------------------------------ + [25.433 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/4654/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 ------------------------------ + [72.055 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/4654/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 [3.420 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/4654/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/4654/tests/integration/interactive_deploy_test.go:112 @ 10/25/23 02:50:51.949 ------------------------------ S ------------------------------ + [147.101 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/4654/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 ------------------------------ SSSS ------------------------------ + [57.242 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/4654/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 ------------------------------ + [4.798 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/4654/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 ------------------------------ + [57.058 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/4654/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 ------------------------------ + [118.423 seconds] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying name for container in Devfile should react on the Devfile modification (podman=false, manual=false, customPortForwarding=true, customAddress=true) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [61.210 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/4654/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 ------------------------------ SSS ------------------------------ + [4.043 seconds] odo create/delete/list/set namespace/project tests set namespace should not succeed to set the namespace C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ S ------------------------------ + [25.046 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/4654/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 ------------------------------ + [128.238 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/4654/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 ------------------------------ SSSS ------------------------------ + [57.179 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/4654/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 ------------------------------ + [66.630 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/4654/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 ------------------------------ S ------------------------------ + [89.618 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/4654/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 ------------------------------ + [48.105 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/4654/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 ------------------------------ SS ------------------------------ + [56.863 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/4654/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 ------------------------------ + [56.355 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/4654/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 ------------------------------ + [69.503 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/4654/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 ------------------------------ + [4.144 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/4654/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 ------------------------------ S ------------------------------ + [56.345 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/4654/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 ------------------------------ + [56.807 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/4654/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 ------------------------------ S ------------------------------ + [55.721 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/4654/tests/integration/cmd_dev_test.go:3622 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" PID: 6436 << Captured StdOut/StdErr Output ------------------------------ + [57.819 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/4654/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 ------------------------------ + [55.746 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/4654/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 ------------------------------ Progress Report for Ginkgo Process #13 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.967s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:4146 In [It] (Node Runtime: 2m0.001s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/integration/cmd_dev_test.go:4146 Begin Captured GinkgoWriter Output >> ... [odo] I1025 02:51:49.414509 6752 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: xczufd-app-54fbb7b5df-nv768 in container: runtime [odo] I1025 02:51:49.414957 6752 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-test4146alp/pods/xczufd-app-54fbb7b5df-nv768/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] I1025 02:51:49.415054 6752 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] X Finished executing the application (command: run) [1m] [odo] I1025 02:51:49.455252 6752 all.go:46] starting to concurrently query 200 APIs [odo] I1025 02:51:49.455370 6752 all.go:62] fired up all goroutines to query APIs [odo] I1025 02:51:50.078471 6752 all.go:67] all goroutines have returned in 623.2196ms [odo] I1025 02:51:50.078471 6752 all.go:76] query result: objects=615 << End Captured GinkgoWriter Output Spec Goroutine goroutine 659 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000552e00, {0x2a08b88?, 0xc0002b7818}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000552e00, {0x2a08b88, 0xc0002b7818}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/onsi/gomega/gexec.(*Session).Wait(0xc00125dd50?, {0xc000207cb0?, 0x2630c96?, 0x9?}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/gexec/session.go:144 github.com/redhat-developer/odo/tests/helper.DevSession.WaitEnd(...) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:263 github.com/redhat-developer/odo/tests/helper.RunDevMode.func1() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/helper/helper_dev.go:337 > github.com/redhat-developer/odo/tests/integration.glob..func7.64.2() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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({0x2052365, 0xc000cd1200}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [4.105 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/4654/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 ------------------------------ + [56.685 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/4654/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 ------------------------------ SSS ------------------------------ + [128.147 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/4654/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 ------------------------------ SS ------------------------------ + [4.373 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/4654/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 ------------------------------ SSS ------------------------------ + [57.700 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/4654/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 ------------------------------ + [82.829 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/4654/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 ------------------------------ + [4.620 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/4654/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 ------------------------------ + [17.913 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/4654/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 ------------------------------ + [76.349 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/4654/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 ------------------------------ + [5.550 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/4654/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 ------------------------------ SSSSSSSSSSSSS ------------------------------ + [35.946 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/4654/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.812 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/4654/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 ------------------------------ S ------------------------------ + [2.404 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/4654/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 ------------------------------ SSS ------------------------------ + [117.760 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/4654/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 ------------------------------ S ------------------------------ + [84.332 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/4654/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 ------------------------------ + [5.069 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/4654/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 ------------------------------ + [55.737 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/4654/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 ------------------------------ SSS ------------------------------ + [117.727 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/4654/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 [2.142 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/4654/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/4654/tests/integration/interactive_dev_test.go:115 @ 10/25/23 02:52:59.346 ------------------------------ S ------------------------------ + [4.249 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/4654/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 ------------------------------ + [3.876 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/4654/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 ------------------------------ + [34.168 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/4654/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 ------------------------------ SSSSS ------------------------------ + [77.887 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/4654/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 ------------------------------ + [53.372 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/4654/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 ------------------------------ S ------------------------------ + [5.076 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/4654/tests/integration/generic_test.go:132 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" << Captured StdOut/StdErr Output ------------------------------ SS ------------------------------ + [52.448 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/4654/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 ------------------------------ SS ------------------------------ + [136.954 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/4654/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 ------------------------------ SSS ------------------------------ S [2.752 seconds] odo dev command tests when a component is bootstrapped [It] should not set securitycontext for podsecurity admission C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:394 @ 10/25/23 02:53:20.716 ------------------------------ + [6.432 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/4654/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 ------------------------------ + [88.327 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/4654/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 ------------------------------ SS ------------------------------ + [67.929 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/4654/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 ------------------------------ SSSSS ------------------------------ + [6.669 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/4654/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 ------------------------------ SSS ------------------------------ + [2.920 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/4654/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 ------------------------------ + [5.392 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/4654/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 ------------------------------ + [2.924 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/4654/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 ------------------------------ + [3.996 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/4654/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 ------------------------------ + [60.314 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/4654/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 ------------------------------ + [56.880 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/4654/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 ------------------------------ + [7.354 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/4654/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 ------------------------------ S [66.449 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/4654/tests/integration/cmd_dev_test.go:746 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:748 @ 10/25/23 02:53:09.634 ------------------------------ S ------------------------------ + [138.212 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/4654/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 ------------------------------ + [23.980 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/4654/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 ------------------------------ + [28.307 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/4654/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 ------------------------------ + [57.155 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/4654/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 [56.230 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/4654/tests/integration/cmd_dev_test.go:1353 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:1356 @ 10/25/23 02:53:21.85 ------------------------------ + [4.835 seconds] odo describe component command tests should fail, with cluster C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SSS ------------------------------ S [3.418 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/4654/tests/integration/cmd_devfile_deploy_test.go:387 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_devfile_deploy_test.go:390 @ 10/25/23 02:54:00.189 ------------------------------ + [66.426 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/4654/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 ------------------------------ + [3.152 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/4654/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 ------------------------------ S ------------------------------ + [3.987 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/4654/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 ------------------------------ + [46.293 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/4654/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 ------------------------------ + [5.157 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/4654/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 ------------------------------ S ------------------------------ + [3.869 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/4654/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 ------------------------------ + [66.440 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/4654/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 ------------------------------ + [4.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 the component is deleted while having access to the devfile.yaml should have deleted the component C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ S [57.002 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/4654/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/4654/tests/integration/cmd_dev_test.go:1505 @ 10/25/23 02:53:45.296 ------------------------------ + [57.753 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/4654/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 ------------------------------ SSS ------------------------------ + [69.686 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/4654/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 ------------------------------ + [110.392 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/4654/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 ------------------------------ SSS ------------------------------ + [34.976 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/4654/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 ------------------------------ + [56.359 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/4654/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 ------------------------------ + [34.943 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/4654/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 ------------------------------ SSSS ------------------------------ + [55.367 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/4654/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 ------------------------------ + [57.864 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/4654/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 ------------------------------ S ------------------------------ + [5.255 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/4654/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 ------------------------------ SSS ------------------------------ + [44.817 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/4654/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 ------------------------------ + [58.183 seconds] odo dev command tests when a component is bootstrapped should not sync .git directory C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [4.357 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/4654/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 ------------------------------ SS ------------------------------ + [91.398 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/4654/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 ------------------------------ + [67.815 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/4654/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 ------------------------------ SSS ------------------------------ + [57.453 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/4654/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 ------------------------------ + [56.536 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/4654/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 ------------------------------ + [76.471 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/4654/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 ------------------------------ + [55.994 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/4654/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.456 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/4654/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 ------------------------------ SSS ------------------------------ + [129.720 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/4654/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 ------------------------------ SS ------------------------------ + [56.961 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/4654/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.497 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/4654/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 ------------------------------ S [56.811 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/4654/tests/integration/cmd_dev_test.go:746 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:748 @ 10/25/23 02:55:12.942 ------------------------------ + [14.634 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/4654/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 ------------------------------ + [120.304 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/4654/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 ------------------------------ S ------------------------------ S [3.452 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/4654/tests/integration/cmd_pref_config_test.go:377 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_pref_config_test.go:379 @ 10/25/23 02:55:47.84 ------------------------------ S ------------------------------ S [3.297 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/4654/tests/integration/cmd_dev_test.go:1815 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:1818 @ 10/25/23 02:55:49.465 ------------------------------ S ------------------------------ + [2.172 seconds] odo devfile deploy command tests when directory is empty should error C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ SS ------------------------------ + [3.561 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/4654/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 ------------------------------ + [48.370 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/4654/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 ------------------------------ + [65.681 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/4654/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 ------------------------------ + [3.508 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/4654/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 ------------------------------ SS ------------------------------ + [84.346 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/4654/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 ------------------------------ SS ------------------------------ + [3.754 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/4654/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 ------------------------------ S [2.431 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/4654/tests/integration/cmd_dev_test.go:1815 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:1818 @ 10/25/23 02:55:58.105 ------------------------------ SSS ------------------------------ + [3.986 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/4654/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 ------------------------------ SSSSS ------------------------------ + [138.543 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/4654/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 ------------------------------ + [5.856 seconds] odo generic When deleting two project one after the other should be able to delete sequentially C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ S [56.936 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/4654/tests/integration/cmd_dev_test.go:1353 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:1356 @ 10/25/23 02:55:39.782 ------------------------------ + [23.897 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/4654/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 ------------------------------ + [57.318 seconds] odo dev command tests when running odo dev with alternative commands - without metadata.name when running odo dev with a build command should execute the custom non-default build command successfully C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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 ------------------------------ + [4.942 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/4654/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.376 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/4654/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\4654\bin\odo.exe deploy' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1603017097 << Captured StdOut/StdErr Output ------------------------------ + [86.341 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/4654/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 ------------------------------ SS ------------------------------ + [127.842 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/4654/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 ------------------------------ SSSS ------------------------------ + [46.399 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/4654/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 ------------------------------ SS ------------------------------ + [6.157 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/4654/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 ------------------------------ + [55.741 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/4654/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 ------------------------------ + [56.434 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/4654/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 ------------------------------ + [5.455 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/4654/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\4654\bin\odo.exe deploy' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2047153063 << Captured StdOut/StdErr Output ------------------------------ S ------------------------------ + [3.465 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/4654/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 ------------------------------ + [55.633 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/4654/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 ------------------------------ + [76.288 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/4654/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 ------------------------------ + [55.987 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/4654/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 ------------------------------ + [4.198 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/4654/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 ------------------------------ S ------------------------------ S [3.362 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/4654/tests/integration/cmd_dev_test.go:1815 [It] C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/integration/cmd_dev_test.go:1818 @ 10/25/23 02:56:59.389 ------------------------------ SS ------------------------------ + [64.742 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/4654/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 ------------------------------ + [45.305 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/4654/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 ------------------------------ SSSS ------------------------------ + [25.114 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/4654/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 ------------------------------ + [4.647 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/4654/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 ------------------------------ S ------------------------------ + [4.189 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/4654/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 ------------------------------ + [5.725 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/4654/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 ------------------------------ + [57.232 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/4654/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 ------------------------------ + [94.619 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/4654/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 ------------------------------ + [116.118 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/4654/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 ------------------------------ + [47.354 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/4654/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 ------------------------------ + [23.571 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/4654/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 ------------------------------ + [58.051 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/4654/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 ------------------------------ + [56.529 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/4654/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 ------------------------------ + [56.294 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/4654/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 ------------------------------ + [58.862 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/4654/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 ------------------------------ + [56.247 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/4654/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.680 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/4654/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 ------------------------------ + [146.378 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/4654/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 ------------------------------ + [125.723 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/4654/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 ------------------------------ + [242.030 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/4654/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 ------------------------------ Ran 390 of 956 Specs in 1395.688 seconds SUCCESS! -- 390 Passed | 0 Failed | 0 Pending | 566 Skipped Ginkgo ran 1 suite in 23m33.6877764s Test Suite Passed go run -mod=vendor github.com/onsi/ginkgo/v2/ginkgo --randomize-all --poll-progress-after=120s --poll-progress-interval=120s -timeout 14400s --no-color -nodes=16 --junit-report="test-e2e.xml" tests/e2escenarios Running Suite: odo e2e scenarios - C:\Users\Administrator.ANSIBLE-TEST-VS\4654\tests\e2escenarios ================================================================================================= Random Seed: 1698220774 - will randomize all specs Will run 4 of 4 specs Running in parallel across 16 processes ------------------------------ + [117.085 seconds] E2E Test starting with non-empty Directory test debugging should verify developer workflow from non-empty Directory C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:316 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2470625795 << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #4 Automatically polling progress: E2E Test starting with empty Directory should verify developer workflow from empty Directory (Spec Runtime: 2m2.09s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:50 In [It] (Node Runtime: 2m0.019s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:50 Begin Captured GinkgoWriter Output >> ... [odo] I1025 03:01:48.952175 7000 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\2875817447\\.odo" [odo] I1025 03:01:48.958992 7000 file_watcher.go:101] ignoring watch on path C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2875817447\.odo [odo] I1025 03:01:48.958992 7000 watch.go:348] filesystem watch event: CREATE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\2875817447\\.odo\\odo-file-index.json" [odo] I1025 03:01:48.964159 7000 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\2875817447\\.odo\\odo-file-index.json" [odo] I1025 03:01:48.973254 7000 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\2875817447\\.odo" [odo] I1025 03:01:48.976129 7000 file_watcher.go:101] ignoring watch on path C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2875817447\.odo [odo] I1025 03:01:48.976129 7000 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\2875817447\\.odo\\devstate.json" [odo] I1025 03:01:48.978053 7000 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\2875817447\\.odo\\devstate.json" [odo] I1025 03:01:48.980317 7000 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\2875817447\\.odo\\devstate.7000.json" [odo] I1025 03:01:48.982012 7000 watch.go:348] filesystem watch event: WRITE "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\AppData\\Local\\Temp\\2875817447\\.odo\\devstate.7000.json" << End Captured GinkgoWriter Output Spec Goroutine goroutine 99 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000721570, {0x31c8ab0?, 0xc000ccd0e0}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000721570, {0x31c8ab0, 0xc000ccd0e0}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2e27f83, 0xf}, 0x0?, 0x3?, 0xc000ccd0b0) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/tests/helper/helper_dev.go:192 > github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.5.1() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:142 | | // start dev mode again > devSession, err = helper.StartDevMode(helper.DevSessionOpts{}) | Expect(err).ToNot(HaveOccurred()) | github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x1512ede, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ Progress Report for Ginkgo Process #1 Automatically polling progress: E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory (Spec Runtime: 2m3.226s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:186 In [It] (Node Runtime: 2m0.006s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:186 Begin Captured GinkgoWriter Output >> ... [odo] I1025 03:01:50.864529 2972 exec.go:37] Executing command [/bin/sh -c kill 364 || true] for pod: pysxlb-app-d957b7865-zxjgf in container: tools [odo] I1025 03:01:51.039837 2972 exec.go:96] /bin/sh: line 1: kill: (364) - No such process [odo] I1025 03:01:51.040162 2972 retry.go:48] waiting for 2 second(s) before trying task "status for remote process 364" [odo] I1025 03:01:53.055274 2972 exec.go:37] Executing command [/bin/sh -c kill -0 364; echo $?] for pod: pysxlb-app-d957b7865-zxjgf in container: tools [odo] I1025 03:01:53.296430 2972 exec.go:96] /bin/sh: line 1: kill: (364) - No such process [odo] I1025 03:01:53.296549 2972 exec.go:96] 1 [odo] I1025 03:01:53.300210 2972 kubeexec.go:54] StartProcessForCommand for "run" [odo] - Executing the application (command: run) ... [odo] I1025 03:01:53.300907 2972 retry.go:48] waiting for 5 second(s) before trying task "process for command \"run\"" [odo] I1025 03:01:53.300907 2972 exec.go:37] Executing command [/bin/sh -c echo $$ > /opt/odo/.odo_cmd_run.pid && cd ${PROJECT_SOURCE} && (mvn -Dmaven.repo.local=/home/user/.m2/repository spring-boot:run) 1>>/proc/1/fd/1 2>>/proc/1/fd/2; echo $? >> /opt/odo/.odo_cmd_run.pid] for pod: pysxlb-app-d957b7865-zxjgf in container: tools << End Captured GinkgoWriter Output Spec Goroutine goroutine 70 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000408150, {0x31c8ab0?, 0xc0007105a0}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000408150, {0x31c8ab0, 0xc0007105a0}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2e19f80, 0x8}, 0xc000672000?, 0xc0001061e0?, 0xc0008a4420) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc0001d1e28) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:279 > github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.6.2() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:233 | // "changes are made to the applications" | helper.ReplaceString(filepath.Join(commonVar.Context, "src", "main", "java", "com", "example", "demo", "DemoApplication.java"), "Hello updated World!", "Hello from an updated World!") > err = devSession.WaitSync() | Expect(err).ToNot(HaveOccurred()) | // "should deploy new changes" github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ Progress Report for Ginkgo Process #2 Automatically polling progress: E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop (Spec Runtime: 2m7.012s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:448 In [It] (Node Runtime: 2m0.014s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:448 Begin Captured GinkgoWriter Output >> ... [odo] I1025 03:01:57.800082 5068 copy.go:171] Corrected destinations: base: /projects file: .gitignore [odo] I1025 03:01:57.800373 5068 copy.go:127] Got abs path: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1356432984\main.go [odo] I1025 03:01:57.800373 5068 copy.go:128] Making C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1356432984 relative to C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1356432984\main.go [odo] I1025 03:01:57.800373 5068 copy.go:144] makeTar srcFile: 1356432984\main.go [odo] I1025 03:01:57.800545 5068 copy.go:145] makeTar destFile: main.go [odo] I1025 03:01:57.800545 5068 copy.go:165] recursiveTar arguments: srcBase: C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp, srcFile: 1356432984\main.go, destBase: \projects, destFile: main.go [odo] I1025 03:01:57.800545 5068 copy.go:171] Corrected destinations: base: /projects file: main.go [odo] V Syncing files into the container [442ms] [odo] I1025 03:01:57.866879 5068 kubeexec.go:40] GetProcessInfoForCommand for "run" [odo] I1025 03:01:57.866879 5068 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: zsjuze-app-59c9d68fd6-wmstc in container: runtime << End Captured GinkgoWriter Output Spec Goroutine goroutine 47 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc0009b60e0, {0x31c8ab0?, 0xc000380750}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc0009b60e0, {0x31c8ab0, 0xc000380750}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2e275d8, 0xf}, 0xc000b9e230?, 0xc000bf3600?, 0xc000870d20) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitRestartPortforward(0xc000c51e28) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:284 > github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.8.4() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:489 | | // Get new random port after restart > err = devSession.WaitRestartPortforward() | Expect(err).ToNot(HaveOccurred()) | github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x1512ede, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [147.222 seconds] E2E Test starting with empty Directory should verify developer workflow from empty Directory C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:50 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2875817447 Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4654\bin\odo.exe delete component' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\2875817447 << Captured StdOut/StdErr Output ------------------------------ + [176.343 seconds] E2E Test starting with non-empty Directory add Binding should verify developer workflow of using binding as env in innerloop C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:448 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\1356432984 << Captured StdOut/StdErr Output ------------------------------ Progress Report for Ginkgo Process #1 Automatically polling progress: E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory (Spec Runtime: 4m3.244s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:186 In [It] (Node Runtime: 4m0.023s) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:186 Begin Captured GinkgoWriter Output >> ... [odo] I1025 03:03:52.715547 6008 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: pysxlb-app-dfbc4bdfb-552tn in container: tools [odo] I1025 03:03:52.913374 6008 exec.go:96] 341 [odo] I1025 03:03:52.915360 6008 exec.go:37] Executing command [/bin/sh -c kill -0 341; echo $?] for pod: pysxlb-app-dfbc4bdfb-552tn in container: tools [odo] I1025 03:03:53.117072 6008 exec.go:96] 0 [odo] I1025 03:03:53.118453 6008 kubeexec.go:40] GetProcessInfoForCommand for "run" [odo] I1025 03:03:53.118957 6008 exec.go:37] Executing command [/bin/sh -c cat /opt/odo/.odo_cmd_run.pid || true] for pod: pysxlb-app-dfbc4bdfb-552tn in container: tools [odo] I1025 03:03:53.268302 6008 exec.go:96] 341 [odo] I1025 03:03:53.272076 6008 exec.go:37] Executing command [/bin/sh -c kill -0 341; echo $?] for pod: pysxlb-app-dfbc4bdfb-552tn in container: tools [odo] I1025 03:03:53.425588 6008 exec.go:96] 0 [odo] - Waiting for the application to be ready ... << End Captured GinkgoWriter Output Spec Goroutine goroutine 70 [select] github.com/onsi/gomega/internal.(*AsyncAssertion).match(0xc000408070, {0x31c8ab0?, 0xc0005da030}, 0x1, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:538 github.com/onsi/gomega/internal.(*AsyncAssertion).Should(0xc000408070, {0x31c8ab0, 0xc0005da030}, {0x0, 0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/gomega/internal/async_assertion.go:145 github.com/redhat-developer/odo/tests/helper.WaitForOutputToContain({0x2e19f80, 0x8}, 0xc000694a00?, 0xc0001061e0?, 0xc0007e0420) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_run.go:54 github.com/redhat-developer/odo/tests/helper.(*DevSession).WaitSync(0xc000e9fe28) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/helper/helper_dev.go:279 > github.com/redhat-developer/odo/tests/e2escenarios.glob..func1.6.2() C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:274 | // making changes to the project again | helper.ReplaceString(filepath.Join(commonVar.Context, "src", "main", "java", "com", "example", "demo", "DemoApplication.java"), "Hello from an updated World!", "Hello from an updated v2 World!") > err = devSession.WaitSync() | Expect(err).ToNot(HaveOccurred()) | github.com/onsi/ginkgo/v2/internal.extractBodyFunction.func3({0x0, 0x0}) C:/Users/Administrator.ANSIBLE-TEST-VS/4654/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/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:865 github.com/onsi/ginkgo/v2/internal.(*Suite).runNode C:/Users/Administrator.ANSIBLE-TEST-VS/4654/vendor/github.com/onsi/ginkgo/v2/internal/suite.go:852 ------------------------------ + [272.118 seconds] E2E Test starting with non-empty Directory should verify developer workflow from non-empty Directory C:/Users/Administrator.ANSIBLE-TEST-VS/4654/tests/e2escenarios/e2e_test.go:186 Captured StdOut/StdErr Output >> Using Devfile Registry URL at: "https://registry.stage.devfile.io" Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4654\bin\odo.exe init' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\379474175 Spawning 'C:\Users\Administrator.ANSIBLE-TEST-VS\4654\bin\odo.exe delete component' from C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\379474175 << Captured StdOut/StdErr Output ------------------------------ Ran 4 of 4 Specs in 272.144 seconds SUCCESS! -- 4 Passed | 0 Failed | 0 Pending | 0 Skipped Ginkgo ran 1 suite in 4m48.9153026s Test Suite Passed