You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Bowen Li (JIRA)" <ji...@apache.org> on 2019/04/19 16:53:00 UTC

[jira] [Created] (FLINK-12265) link-table-planner-blink UT Failure: SortDistinctAggregateITCase.testSomeColumnsBothInDistinctAggAndGroupBy

Bowen Li created FLINK-12265:
--------------------------------

             Summary: link-table-planner-blink UT Failure: SortDistinctAggregateITCase.testSomeColumnsBothInDistinctAggAndGroupBy
                 Key: FLINK-12265
                 URL: https://issues.apache.org/jira/browse/FLINK-12265
             Project: Flink
          Issue Type: Bug
          Components: Table SQL / Planner
    Affects Versions: 1.9.0
            Reporter: Bowen Li
            Assignee: Jingsong Lee
             Fix For: 1.9.0


Seems to be a memory allocation issue but would be worth checking out if that's caused by the planner itself taking too much memory

https://travis-ci.org/apache/flink/jobs/522051049

11:41:37.461 [ERROR] Tests run: 23, Failures: 0, Errors: 1, Skipped: 2, Time elapsed: 73.859 s <<< FAILURE! - in org.apache.flink.table.runtime.batch.sql.agg.SortDistinctAggregateITCase
11:41:37.461 [ERROR] testSomeColumnsBothInDistinctAggAndGroupBy(org.apache.flink.table.runtime.batch.sql.agg.SortDistinctAggregateITCase)  Time elapsed: 6.274 s  <<< ERROR!
org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
Caused by: java.lang.RuntimeException: org.apache.flink.runtime.memory.MemoryAllocationException: Could not allocate 64 pages. Only 0 pages are remaining.
Caused by: org.apache.flink.runtime.memory.MemoryAllocationException: Could not allocate 64 pages. Only 0 pages are remaining.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)