[
https://issues.apache.org/jira/browse/HDFS-12711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226299#comment-16226299
]
Allen Wittenauer commented on HDFS-12711:
-----------------------------------------
For those playing at home:
YETUS-570 (in development) changes how precommit handles tests. It will now
seek out and kill processes that match a certain pattern after unit tests are
run. It reports the number that it had to kill:
| Stuck Test Processes | hadoop-hdfs-project/hadoop-hdfs:21 |
and generates a log to show which processes those were:
| Stuck Test Processes Log |
https://builds.apache.org/job/PreCommit-HDFS-Build2/9/artifact/out/reaper-hadoop-hdfs-project_hadoop-hdfs.log
|
It's supposed to do this after every individual module, but I've got a (simple)
bug to fix first. In any case, this should help give a metric as to just how
broken a particular set of tests actually are. Hopefully at some point we'll
have the logic to pinpoint it to individual tests, but using the actual unit
test log should be pretty helpful.
It's also worth pointing out that this change will also help the full qbt to
actually complete. But I need to fix that bug first.
> deadly hdfs test
> ----------------
>
> Key: HDFS-12711
> URL: https://issues.apache.org/jira/browse/HDFS-12711
> Project: Hadoop HDFS
> Issue Type: Test
> Affects Versions: 2.9.0, 2.8.2
> Reporter: Allen Wittenauer
> Priority: Critical
> Attachments: HDFS-12711.branch-2.00.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
