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

If pabot process gets killed due to exceeding the maximum timeout it's left out of the report #572

Open
MattiJarvinen opened this issue Mar 1, 2024 · 0 comments

Comments

@MattiJarvinen
Copy link

What happended:
If Pabot suite hangs for some reason output.xml ends up faulty and the suite is left out of the end report. Resulting possibly a completely successful automation test end result

2024-02-29T17:49:19.3210294Z 2024-02-29 17:49:19.318149 [PID:9580] [2] [ID:9] Process GUI.Project.Step 1 killed due to exceeding the maximum timeout of 1800 seconds
2024-02-29T17:49:19.3216540Z 2024-02-29 17:49:19.318149 [PID:9580] [2] [ID:9] Execution failed in GUI.Project.Step 1 with -1 failing test(s)

...

2024-02-29T17:49:20.7292733Z Reading XML source 'robot_results\pabot_results\9\output.xml' failed: ParseError: no element found: line 4544, column 0
2024-02-29T17:49:20.7293595Z Skipping 'robot_results\pabot_results\9\output.xml' from final result

Expected:

A new output.xml would be written with suite setup failing with some appropriate error message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant