allure-framework/allure-java

Allure processes leak when using allure:serve

karltiirik opened this issue · 2 comments

karltiirik commented

Describe the bug
Allure process not killed after Ctrl + C (leaks processes).

To Reproduce
Steps to reproduce the behavior:

  1. Use sample project: karltiirik/spock-restassured-allure@88de0e3
  2. Run tests: mvnw clean test
  3. Generate and serve Allure report: mvnw allure:serve
  4. Press <Ctrl+C> to exit

Expected behavior
The java process that serves the Allure report is killed. The same behavior that is when having Allure on your path and doing allure serve and after <Ctrl+C> to exit (then the process is killed).

Desktop (please complete the following information):

  • OS: Microsoft Windows 10 Enterprise 10.0.19044 Build 19044
baev commented

For allure-commandline we use default Gradle application plugin. Windows doesn't terminate child processes when the parent process dies. And there is no easy solution for that.

karltiirik commented

Hmm, that's sad. Do know of any workaround for this problem? Like a plugin that keeps track of all the spawned child process and can kill them when the maven build finishes or something along the lines?