-
Notifications
You must be signed in to change notification settings - Fork 244
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
Manual sync of files pressing p #6089
Manual sync of files pressing p #6089
Conversation
✅ Deploy Preview for odo-docusaurus-preview ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
7295473
to
39b10e1
Compare
Blocked by #6091 |
ce9abac
to
6462d62
Compare
25d9a3f
to
4feaaf8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your work on this. Added a few code-related comments I had so far.
7af8493
to
8f39f15
Compare
Thanks @rm3l for your review |
/hold Windows tests are failing on CI (non required) |
42f7717
to
a6cfb2e
Compare
0b45a78
to
406923f
Compare
Kudos, SonarCloud Quality Gate passed!
|
@anandrkskd I've added a PR to fix the problem of failing integration tests on Windows |
/override ci/prow/v4.10-integration-e2e |
@feloy: Overrode contexts on behalf of feloy: ci/prow/v4.10-integration-e2e In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this:
/kind feature
What does this PR do / why we need it:
This PR configures the terminal to work in Character mode, instead of the default Line mode. Read() will return as soon as a character is sent to the input stream, instead of waiting for a newline character.
code refactoring:
Which issue(s) this PR fixes:
Fixes #5634
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer:
odo dev
will fail to configure terminal on Windows/cygwin terminal.You can use
$ winpty odo dev
to fix the problemhttps://bryantson.medium.com/troubleshooting-make-raw-terminal-failed-the-handle-is-invalid-57b7e1d9b12b
Windows terminal seetings
https://docs.microsoft.com/en-us/windows/console/setconsolemode
Unix terminal settings:
https://man7.org/linux/man-pages/man3/termios.3.html
Refactoring integration tests
Some tests were calling devSession.Kill() (or Stop()) twice, which makes ginkgo stop abrupty during the second call on Windows.
In the following example, the Kill in AfterEach is necessary for the cleanup after test1, but is problematic for test2, as Stop has been called before.
As the AfterEach/BeforeEach are evaluated at the beginning, it is not possible to rely on a field in devSession to record if the method has already been called.
These tests have been split in two trees, separating test1 and test2, to be able to call Kill/Stop only once.