To short timeout for generateReport method.

[Coder1304]

I'm submitting a ...

• bug report
• feature request
• support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

For large amount of test results, allure framework generates report longer than 60 sec which cause timeout of ExecuteWatchdog. Allure framework process is killed and report is only partially generated. Exception is thrown:

[ERROR] Can't generate allure report data
org.apache.commons.exec.ExecuteException: Process exited with an error: 143 (Exit value: 143)

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

To reproduce the bug you have to generate large amount of data for allure framework. For example: web application tests which stores each send and received messages.

What is the expected behavior?

Timeout for AllureCommandline::generateReport should be configurable just like in case of AllureCommandline::serve.

What is the motivation / use case for changing the behavior?

Fix the malfunction of the main functionality.

Please tell us about your environment:

• Allure version: 2.7.0
• Test framework: [email protected]
• Allure adaptor: [email protected]
• Generate report using: [email protected]
• Apache Maven 3.3.9
• maven-surefire-plugin 2.21.0

Other information

[korobochka]

+1, this completely blocks us from using allure-maven plugin in production.

[baev]

@korobochka could you please submit a pull request with the fix?

[korobochka]

Do you want the timeout to be separate from serveTimeout? I think it does not really make sense to have two, I'd rename serveTimeout -> timeout and use it for both generate and serve.

[Coder1304]

@korobochka I am OK with that. This will require update of configuration for serve users but I think it's low cost.