[
https://issues.apache.org/jira/browse/HDFS-17972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18111570#comment-18111570
]
ASF GitHub Bot commented on HDFS-17972:
---------------------------------------
pan3793 commented on PR #8712:
URL: https://github.com/apache/hadoop/pull/8712#issuecomment-5541657174
thanks, merged to trunk/branch-3.5
a side note: @joseluisll, since you have been working on the testing fix and
stability improvement recently, you may be interested in re-enabling the tests
excluded on GHA by `.github/gha-tests/exclude-tests.txt` - those tests were
disabled either because they were flaky or failed consistently when run on GHA,
I believe some tests can be re-enabled with the recent efforts on test
improvement
> TestDFSClientRetries#testLeaseRenewAndDFSOutputStreamDeadLock hangs the
> surefire fork instead of failing
> --------------------------------------------------------------------------------------------------------
>
> Key: HDFS-17972
> URL: https://issues.apache.org/jira/browse/HDFS-17972
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs, test
> Reporter: Jose Luis López
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.0, 3.5.2
>
>
> h2. Problem
> This problem has no production impact. It is limited to the test
> infraestructure.
> {{testLeaseRenewAndDFSOutputStreamDeadLock}} blocks indefinitely instead of
> failing at its 120s deadline. It converts a bounded 120-second test failure
> into a build-killing hang that destroys the test report for an entire module
> and leaves no machine-readable trace. Yetus emits no per-class failure table
> for the affected run, so the contributor loses the result for every test in
> hadoop-hdfs, not just this one.
> Observed in precommit as {{testLeaseRenewAndDFSOutputStreamDeadLock}} and
> {{testLeaseRenewSocketTimeout}} failing together, always as timeouts, never
> as assertions, and both passing when re-run individually. Worst case seen:
> PR-8634 build 3 ran ~24 hours and died with exit code 137.
> This problem hangs the test process for very long time instead of producing a
> failure in the timeout period of the test.
> The impact is that all tests from the hdfs module fail because of the hang,
> instead of failing just one test. The fix would turn every future occurrence
> from failing all tests back into a single failed test.
> h2. Root cause
> Two defects combine:
> # The timeout cannot interrupt a blocked test.
> # The test leaks a global fault injector.
> This conditions occur in heavy load of the testing infraestructure.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
