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

Pabot fails to execute robot through Jenkins #554

Open
Prashant1781 opened this issue Sep 20, 2023 · 1 comment
Open

Pabot fails to execute robot through Jenkins #554

Prashant1781 opened this issue Sep 20, 2023 · 1 comment

Comments

@Prashant1781
Copy link

Objective is to run test cases/suites in parallel using Pabot configured in Jenkins pipeline. The below command configured in Jenkins fails to run/execute robot:
python3 -m pabot.pabot --testlevelsplit -v V_ENVIRONMENT:$environment -v V_REMOTE_URL:$remoteURL -v V_BROWSER:$browser -v V_DESIRED_CAPABILITIES:$desiredCapabilities --nostatusrc --outputdir /reports/ *-/.robot
This command starts pabot with multiple processes, creates workspace + seperate folders for robot output files for each process but fails to write/create the files: output.xml, log.html, report.html at the project level folder. The process specific folders has error logged "/bin/sh: 1: robot: not found" . It appears that the pabot command fails to locate robot script and execute it

@linh-eureka
Copy link

Objective is to run test cases/suites in parallel using Pabot configured in Jenkins pipeline. The below command configured in Jenkins fails to run/execute robot: python3 -m pabot.pabot --testlevelsplit -v V_ENVIRONMENT:$environment -v V_REMOTE_URL:$remoteURL -v V_BROWSER:$browser -v V_DESIRED_CAPABILITIES:$desiredCapabilities --nostatusrc --outputdir /reports/ *-/.robot This command starts pabot with multiple processes, creates workspace + seperate folders for robot output files for each process but fails to write/create the files: output.xml, log.html, report.html at the project level folder. The process specific folders has error logged "/bin/sh: 1: robot: not found" . It appears that the pabot command fails to locate robot script and execute it

Hi, I met the same issue, do you have some workaround for it?

@mkorpela Could you take a look?

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

2 participants