[
https://issues.apache.org/jira/browse/FLINK-14572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997416#comment-16997416
]
Yun Gao commented on FLINK-14572:
---------------------------------
Hi all, for this issue, I slightly doubt that the attach exception might not be
the one that cause _testBlobServerCleanupFinishedJob_ failed, since this test
is the fourth test of the test suite, all the four tests shares the same blob
server which increase the temp file id after creating each temp file. It can be
seen from the successful executions that the temp file id should be
temp-00000005 for _testBlobServerCleanupFinishedJob_ to receive the user jar.
Instead, it seems that the attached exception should be the one produced in
test _testBlobServerCleanupFailedSubmission_, which is thrown intentionally to
cause job submission fails.
Therefore, it seems no detailed logs still existed to analyze the reason that
the test fails. To further track this issue, I modified the travis scripts to
run only the BlobsCleanupITCase multiple times and submit the test to travis
periodically ([https://travis-ci.org/gaoyunhaii/flink/branches], branch
_fix_blobs_2_). However, the failure is still not reproduced after running the
tests for several days.
> BlobsCleanupITCase failed on Travis
> -----------------------------------
>
> Key: FLINK-14572
> URL: https://issues.apache.org/jira/browse/FLINK-14572
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination, Tests
> Affects Versions: 1.10.0
> Reporter: Gary Yao
> Assignee: Yun Gao
> Priority: Critical
> Labels: test-stability
> Fix For: 1.10.0
>
>
> {noformat}
> java.lang.AssertionError:
> Expected: is <true>
> but: was <false>
> at
> org.apache.flink.runtime.jobmanager.BlobsCleanupITCase.testBlobServerCleanup(BlobsCleanupITCase.java:220)
> at
> org.apache.flink.runtime.jobmanager.BlobsCleanupITCase.testBlobServerCleanupFinishedJob(BlobsCleanupITCase.java:133)
> {noformat}
> https://api.travis-ci.com/v3/job/250445874/log.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)