You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "David Knupp (JIRA)" <ji...@apache.org> on 2017/08/22 23:04:00 UTC
[jira] [Closed] (IMPALA-5820)
test_scanners_fuzz.py::TestScannersFuzzing failing on non-debug builds
[ https://issues.apache.org/jira/browse/IMPALA-5820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Knupp closed IMPALA-5820.
-------------------------------
Resolution: Fixed
IMPALA-5820: Fix string format() syntax in test_scanners_fuzz.py
Make the call to format() compatible with older versions of python
(< 2.7), which expect an indices in the string being formatted,
e.g. "{0} {1} {2}".format('foo', 'bar', 'baz'). Without the numbers,
format() raises an exception.
Tested by running this test suite using python 2.6.6. Before the
patch, the tests failed. After the patch, they pass.
Change-Id: I5384aaf83a6a1f3c7643ed9f15de2dba1a5913a5
Reviewed-on: http://gerrit.cloudera.org:8080/7761
Reviewed-by: Alex Behm <al...@cloudera.com>
Tested-by: Impala Public Jenkins
> test_scanners_fuzz.py::TestScannersFuzzing failing on non-debug builds
> ----------------------------------------------------------------------
>
> Key: IMPALA-5820
> URL: https://issues.apache.org/jira/browse/IMPALA-5820
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 2.10.0
> Reporter: David Knupp
> Assignee: David Knupp
> Priority: Critical
>
> I'm seeing multiple tests failing fromthe {{TestScannersFuzzing}} suite when running exhaustive tests on the release build. There are no crashes or backtraces, but that test suite was last touched as part of the patch for IMPALA-5776, and there appear to be HdfsScanNode-related errors in log files that correspond with the time of the test failures, e.g.
> {noformat}
> I0819 03:07:39.673249 11999 hdfs-scan-node.cc:160] Max row batch queue size for scan node '0' in fragment instance 'fc4b4ab7293a90fd:cda7b65d00000002': 60
> I0819 03:07:39.710546 11965 status.cc:122] Not implemented for this format.
> @ 0x845479 impala::Status::Status()
> @ 0xc474bd impala::HdfsScanNodeBase::Codegen()
> @ 0xa56eb1 impala::FragmentInstanceState::Prepare()
> @ 0xa57531 impala::FragmentInstanceState::Exec()
> @ 0xa34078 impala::QueryState::ExecFInstance()
> @ 0xbd8c82 impala::Thread::SuperviseThread()
> @ 0xbd93e4 boost::detail::thread_data<>::run()
> @ 0xe6120a thread_proxy
> @ 0x3395007851 (unknown)
> @ 0x3394ce894d (unknown)
> {noformat}
> This makes me wonder if these might also be related to IMPALA-5819.
> Taras, who submitted the patch for IMPALA-5776 is away, so assigning to [~alex.behm] who reviewed the patches for both IMPALA-5776 and IMPALA-5819. Please reassign as you see fit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)