[
https://issues.apache.org/jira/browse/IMPALA-6968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463166#comment-16463166
]
Tim Armstrong commented on IMPALA-6968:
---------------------------------------
I tried the obvious thing of looping a release version of this test and it
passed consistently. Could be specific to the environment its running in
somehow.
It doesn't make a whole lot of sense to me why this would be flaky, unless the
write to the file failed somehow.
{code}
// Modify the data in the scratch file and check that a read error occurs.
FILE* file = fopen(file_path.c_str(), "rb+");
fputc('?', file);
fclose(file);
vector<uint8_t> tmp;
tmp.resize(data.size());
Status read_status = file_group.Read(handle.get(), MemRange(tmp.data(),
tmp.size()));
LOG(INFO) << read_status.GetDetail();
EXPECT_EQ(TErrorCode::SCRATCH_READ_VERIFY_FAILED, read_status.code())
<< read_status.GetDetail();
{code}
I'll try to reproduce and maybe add some additional checks.
> TestBlockVerificationGcmDisabled failure in exhaustive
> ------------------------------------------------------
>
> Key: IMPALA-6968
> URL: https://issues.apache.org/jira/browse/IMPALA-6968
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: Impala 2.13.0
> Reporter: Sailesh Mukil
> Assignee: Tim Armstrong
> Priority: Critical
> Labels: flaky
>
> {code:java}
> /data/jenkins/workspace/impala-cdh5-trunk-exhaustive-release-thrift/repos/Impala/be/src/runtime/tmp-file-mgr-test.cc:550
> Value of: read_status.code()
> Actual: 0
> Expected: TErrorCode::SCRATCH_READ_VERIFY_FAILED
> Which is: 118
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
