[ https://issues.apache.org/jira/browse/IMPALA-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Jeges updated IMPALA-10054: ---------------------------------- Labels: broken-build flaky (was: broken-build) > test_multiple_sort_run_bytes_limits fails in parallel-all-tests-nightly > ----------------------------------------------------------------------- > > Key: IMPALA-10054 > URL: https://issues.apache.org/jira/browse/IMPALA-10054 > Project: IMPALA > Issue Type: Improvement > Affects Versions: Impala 4.0 > Reporter: Attila Jeges > Assignee: Riza Suminto > Priority: Blocker > Labels: broken-build, flaky > Fix For: Impala 4.0 > > > test_multiple_sort_run_bytes_limits introduced in IMPALA-6692 seems to be > flaky. > Jenkins job that triggered the error: > https://jenkins.impala.io/job/parallel-all-tests-nightly/1173 > Failing job: > https://jenkins.impala.io/job/ubuntu-16.04-dockerised-tests/2899/testReport/ > {code} > Stacktrace > query_test/test_sort.py:89: in test_multiple_sort_run_bytes_limits > assert "SpilledRuns: " + spilled_runs in query_result.runtime_profile > E assert ('SpilledRuns: ' + '3') in 'Query > (id=404da0b1e56e7248:120789cd00000000):\n DEBUG MODE WARNING: Query profile > created while running a DEBUG buil... 27.999ms\n - WriteIoBytes: > 0\n - WriteIoOps: 0 (0)\n - WriteIoWaitTime: > 0.000ns\n' > E + where 'Query (id=404da0b1e56e7248:120789cd00000000):\n DEBUG MODE > WARNING: Query profile created while running a DEBUG buil... 27.999ms\n > - WriteIoBytes: 0\n - WriteIoOps: 0 (0)\n - > WriteIoWaitTime: 0.000ns\n' = > <tests.beeswax.impala_beeswax.ImpalaBeeswaxResult object at > 0x7f51da77fb50>.runtime_profile > {code} -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org