beaker
beaker copied to clipboard
[BUG] bkr job-results ends with an ISE 500 traceback for jobs with too many results
Describe the bug
When a job contains a lot of reported results (7500), it can't be retrieved via cmdline, bkr job-results returns a non-descriptive ISE 500 traceback:
Traceback (most recent call last):
File "/usr/bin/bkr", line 11, in
Version-Release number
Beaker 28.2
To Reproduce
Schedule a job that reports more than 7500 results
Actual behavior
ISE 500 traceback from bkr client, WebUI loads, albeit slowly.
Expected behavior
Beaker should give users a descriptive error instructing them what went wrong and how to fix it (not an ISE 500), do so consistently (same behavior when using webui and api) and ideally do it in a timely manner and abort cleanly when limits are reached.
Yeah, I know the root cause here. The beaker server died when it tried to fetch all the data to memory. Workers killed by the system and resulting in 500. I will fix this when I rework API.