Skye Wanderman-Milne 9aeb77023f IMPALA-2993: don't check for "Failed to allocate buffer for collection" error ...

This test query is supposed to check the error path for when a
collection buffer cannot be allocated. However, it's flaky because the
collection allocations are not very big (< 2KB), so it's possible for
a different operator to trigger OOM.

I think the correct solution is to create a test file that contains
very large collections, so a large collection allocation will trigger
OOM, rather than many small collection allocations. For now though,
let's disable the specific collection allocation check to unblock the
build, even though we risk losing coverage.

Change-Id: Iab4c9b605186926c522cf692246a37882fbdfcdb
Reviewed-on: http://gerrit.cloudera.org:8080/2208
Reviewed-by: Skye Wanderman-Milne <skye@cloudera.com>
Tested-by: Internal Jenkins

2016-02-18 01:25:10 -08:00

..

queries

IMPALA-2993: don't check for "Failed to allocate buffer for collection" error

2016-02-18 01:25:10 -08:00

functional-query_core.csv

Reorganize/reduce end to end test time.

2014-08-17 12:43:57 -07:00

functional-query_dimensions.csv

Treat HBase as a file format for functional tests

2014-01-08 10:52:36 -08:00

functional-query_exhaustive.csv

Reading compressed text.

2014-07-29 20:28:36 -07:00

functional-query_pairwise.csv

Treat HBase as a file format for functional tests

2014-01-08 10:52:36 -08:00