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

Continuous Testing on Windows 10 cmd hang #16865

Closed
loicmathieu opened this issue Apr 28, 2021 · 4 comments · Fixed by #16893
Closed

Continuous Testing on Windows 10 cmd hang #16865

loicmathieu opened this issue Apr 28, 2021 · 4 comments · Fixed by #16893
Labels
env/windows Impacts Windows machines kind/bug Something isn't working
Milestone

Comments

@loicmathieu
Copy link
Contributor

Describe the bug

When using the new continuous testing features on Windows 10 default terminal (cmd) the terminal hang and you cannot quit it via CTRL-C.

Expected behavior

CTRL-C exit the application.

Actual behavior

CTRL-C has no effect

To Reproduce

Simple project to reproduce the issue
try-continous-testing.zip

Steps to reproduce the behavior:

  1. Start a terminal on Windows 10 via cmd
  2. Start the application on dev mode : mvn quarkus:dev
  3. Enable continuous testing : e
  4. Disable continuous testing: d
  5. Try to quit the application via CTRL-C

Environment (please complete the following information):

Output of uname -a or ver: Microsoft Windows [version 10.0.19042.867]

Output of java -version: openjdk version "16" 2021-03-16

Quarkus version or git rev: 2.0.0.Alpha1

Build tool (ie. output of mvnw --version or gradlew --version): Apache Maven 3.6.3

@loicmathieu loicmathieu added the kind/bug Something isn't working label Apr 28, 2021
@quarkus-bot quarkus-bot bot added the env/windows Impacts Windows machines label Apr 28, 2021
@loicmathieu
Copy link
Contributor Author

/cc @stuartwdouglas

stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Apr 29, 2021
stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Apr 29, 2021
@quarkus-bot quarkus-bot bot added this to the 2.0 - main milestone Apr 29, 2021
@ghost
Copy link

ghost commented Jun 24, 2021

@loicmathieu
Have you (re)tested this with 2.0.0.CR3?
For me CTRL+c is still not working when Continous Testing is enabled. If disabled the application exits fine on CTRL+c.

@loicmathieu
Copy link
Contributor Author

@Axblu I do testing it OK. However I saw a small delay between hitting CTRL-C and the actual stop of the application.

@ghost
Copy link

ghost commented Jun 24, 2021

@loicmathieu
Ah! I have this issue with WSL in Windows, not cmd. Sorry for the wrong alert.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
env/windows Impacts Windows machines kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant