Allow tests/overview page to handle more than 500 jobs with result filter conditions size: M
Since the patch from #110680 has been applied there are some use cases where the
tests/overview page no longer works as expected by our users. This link for example should not be showing the limit warning. But it does because the SQL queries retrieving the jobs (and which apply the limit) do not consider certain filter conditions such as result yet. Those are handled by the unoptimised pure Perl aggregate code in a later step.
- AC1: This link does not trigger the result limit warning anymore
- AC2: This link still does trigger the result limit warning
After running a bunch of experiments i located the problem, simply moving the condition to SQL does not work because of the duplicate removal code here. It depends on the presence of old jobs with different states. The multiple layers of SQL generation and Perl filtering make this a very complex issue. I will have to try to move the duplicate removal to SQL too, or find a different solution for the job limit.