Description of problem:
If a job includes a lot of test phases (few thousand), retrieving them using command line tool is not possible, the command timeouts or returns XML-RPC error
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a job that uploads few thousand results to beaker
2. try to retrieve it using bkr job-results
XML-RPC fault: <type 'exceptions.MemoryError'>
results of the job, like for smaller tasks
I believe we talked about this on the meetup.
You are already hitting memory limit on the server, there is very little we can do about it.
There are two workarounds:
1) Use bkr job-results <Job/Recipe/Task ID> --no-logs which will output the results without log info
2) Use bkr job-results <Recipe/Task ID> which will output info directly for the recipe/task you're asking for
You can pipe these two (job-results contains ID as well) and that way you can ask (for example) only for logs for aborted tasks.
Yes, I mentioned issues with those tasks on the meetup. No, I didn't hit this specific issue before the meetup.
I'm hitting it because I'm using tools like beaker-jobwatch or tcms-results. I don't use `bkr job-results` directly.
Then I recommend opening up an issue with them and pointing them to this ticket
Hubert, would you mind if I close this? I see that the provided workaround was implemented.
I'm sorry for the late reply.
Yes, it's fixed now; large jobs are handled correctly now.