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.

Sign up for GitHub

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

Jump to bottom

Allow the pabot results to be left without aggregating them. #571

Open
Zoupers opened this issue Mar 1, 2024 · 2 comments · May be fixed by #621
Open

Allow the pabot results to be left without aggregating them. #571

Zoupers opened this issue Mar 1, 2024 · 2 comments · May be fixed by #621
Assignees
@joonaskuisma
Labels
enhancement

Comments

@Zoupers
Copy link

Zoupers commented Mar 1, 2024

As the title suggests, merging logs in Robot Framework currently consumes a substantial amount of memory when dealing with large logs. Therefore, we could consider deferring the merge process to a later stage when adequate memery is available.

Thank you for your understanding and support. If possible, I can also do that by myself.
@Zoupers Zoupers changed the title Allow to leave the pabot result without agg them. Allow the pabot results to be left without aggregating them. Mar 1, 2024
@joonaskuisma
Copy link
Collaborator

Hi @Zoupers !

With a few lines of code, I can add a new argument to Pabot, so that giving the --no-rebot argument will leave the results unmerged. However, in that case, the summary line 12 tests, 12 passed, 0 failed, 0 skipped. cannot be printed to the command line.

What do you think about this?

Robot Framework remote server at 127.0.0.1:8270 started.
2025-02-07 06:47:34.778672 [PID:35924] [0] [ID:3] EXECUTING Data 1.suite D
2025-02-07 06:47:34.779677 [PID:43448] [2] [ID:0] EXECUTING Data 1.suite A
2025-02-07 06:47:34.780674 [PID:35164] [1] [ID:2] EXECUTING Data 1.suite C
2025-02-07 06:47:34.780674 [PID:40540] [3] [ID:1] EXECUTING Data 1.suite B
2025-02-07 06:47:37.604861 [PID:35924] [0] [ID:3] PASSED Data 1.suite D in 2.8 seconds
2025-02-07 06:47:37.911401 [PID:43448] [2] [ID:0] PASSED Data 1.suite A in 3.1 seconds
2025-02-07 06:47:38.241864 [PID:40540] [3] [ID:1] PASSED Data 1.suite B in 3.4 seconds
2025-02-07 06:47:40.642282 [PID:35164] [1] [ID:2] PASSED Data 1.suite C in 5.8 seconds
All tests were executed, but the --no-rebot argument was given, so the results were not compiled, and no summary was generated. All results have been saved in the .\pabot_results folder.
===================================================
Stopping PabotLib process
Robot Framework remote server at 127.0.0.1:8270 stopped.
PabotLib process stopped
Total testing: 15.10 seconds
Elapsed time:  6.59 seconds

@joonaskuisma joonaskuisma self-assigned this Feb 7, 2025
@Zoupers
Copy link
Author

Zoupers commented Feb 7, 2025

It's cool with the few lines of code! I can't wait to see it!

joonaskuisma added a commit to joonaskuisma/pabot that referenced this issue Feb 9, 2025
@joonaskuisma
Introduced --no-rebot argument (mkorpela#571)
c59af14 
- Added feature and updated documentation.
@joonaskuisma joonaskuisma linked a pull request Feb 15, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joonaskuisma joonaskuisma

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: Add --no-rebot option and #SLEEP keyword, fix caching bug joonaskuisma/pabot
2 participants
@Zoupers @joonaskuisma