Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows tests not running the right odo binary #5683

Closed
rm3l opened this issue Apr 21, 2022 · 0 comments · Fixed by #5702
Closed

Windows tests not running the right odo binary #5683

rm3l opened this issue Apr 21, 2022 · 0 comments · Fixed by #5702
Assignees
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/bug Categorizes issue or PR as related to a bug.

Comments

@rm3l
Copy link
Member

rm3l commented Apr 21, 2022

/kind bug
/area testing

First encountered this issue in #5675. The entire job logs are attached below.
windows-integration-test-log.txt

Context

Weirder than before. It can't find --no-watch flag! 😕

[14] [odo] Your new component 'qaymxq' is ready in the current directory.
[14] [odo] To start editing your component, use 'odo dev' and open this folder in your favorite IDE.
[14] [odo] Changes will be directly reflected on the cluster.
[14] Running odo.exe with args [odo dev --random-ports --no-watch]
[14] [odo] Error: unknown flag: --no-watch
[14] [odo] Usage:
[14] [odo]   odo dev [flags]
[14] [odo] 
[14] [odo] Examples:
[14] [odo]   # Deploy component to the development cluster
[14] [odo]   odo dev
[14] [odo] 
[14] [odo] Flags:
[14] [odo]   -h, --help           Help for dev
[14] [odo]   -f, --random-ports   Assign random ports to redirected ports
[14] [odo] 
[14] [odo] Additional Flags:
[14] [odo]       --kubeconfig string    Paths to a kubeconfig. Only required if out-of-cluster.
[14] [odo]   -v, --v Level              Number for the log level verbosity. Level varies from 0 to 9 (default 0).
[14] [odo]       --vmodule moduleSpec   Comma-separated list of pattern=N settings for file-filtered logging
[14] [odo] 
[14] [odo]  X  unknown flag: --no-watch

Originally posted by @dharmit in #5675 (comment)


Indeed, this is strange. As you said, it looks like a different binary was used. I can see the version is v2.5.0 in the CI job logs, while it should now be v3.0.0-alpha1 (since 946385b and #5677, and given that you rebased your branch onto main):

[14] [odo] I0421 03:47:24.159538   10020 implem.go:103] The path for preference file is C:\Users\Administrator.ANSIBLE-TEST-VS\AppData\Local\Temp\238738076\preference.yaml
[14] [odo]   __
[14] [odo]  /  \__     Initializing new component
[14] [odo]  \__/  \    
[14] [odo]  /  \__/    odo version: v2.5.0
[14] [odo]  \__/
[14] [odo] 
[14] [odo] Interactive mode enabled, please answer the following questions:
[14] [odo]  -  Copying devfile from "C:\\Users\\Administrator.ANSIBLE-TEST-VS\\651\\tests\\examples\\source\\devfiles\\nodejs\\devfile.yaml"  ...
[14] [odo]

Originally posted by @rm3l in #5675 (comment)

@openshift-ci openshift-ci bot added kind/bug Categorizes issue or PR as related to a bug. area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering labels Apr 21, 2022
@rm3l rm3l changed the title Windows tests might not run the right odo binary Windows tests not running the right odo binary Apr 21, 2022
@rm3l rm3l mentioned this issue Apr 21, 2022
3 tasks
@anandrkskd anandrkskd moved this to For Review in odo v3-beta1 Apr 28, 2022
Repository owner moved this from For Review to Done in odo v3-beta1 Apr 28, 2022
@rm3l rm3l added the v3 label Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/bug Categorizes issue or PR as related to a bug.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants