tests: Make predicate out-of-memory test less aggressive

Currently this test has very large runtime and relies on the fact that
the first memory allocation error causes the test to terminate. This
does not work with new behavior of running the query through and
reporting the error at the end, so make the runtime reasonable but still
generate enough memory to blow past the budget.

0 files changed, 0 insertions, 0 deletions