mirror of
https://github.com/apache/impala.git
synced 2026-01-03 06:00:52 -05:00
82290d61ad
A recent change (IMPALA-3524) removed a 'CATCH' section for a mem limit exceeded error because the other changes in the patch reduced the memory requirements for that particular query and the error was no longer being hit. This seemed okay because the point of the test wasn't to trigger the mem limit exceeded error, and I manually verified that the situation was the test was addressing was still covered even without the error being hit. It turns out, though, that the test still hits the error in some situations (local-filesystem and non-partitioned-aggs-and-joins builds). The fix is to make the test more permissive by adding '__NO_ERROR_' as one of the options in the 'CATCH: ANY_OF' section, so that it passes whether or not the mem limit is exceeded. Change-Id: I4731a3e83dd2142a1d83be963f83cd1847472295 Reviewed-on: http://gerrit.cloudera.org:8080/5941 Reviewed-by: Dan Hecht <dhecht@cloudera.com> Tested-by: Impala Public Jenkins