[
https://issues.apache.org/jira/browse/HBASE-12187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169991#comment-14169991
]
stack commented on HBASE-12187:
-------------------------------
[~d.yuan] Thank you for paper, your findings, your previous patches, and your
now showing up to offer help. Much appreciated. We have a bunch of work to do
to address items raised in your paper.
Currently we run findbugs and other checks out of a script as part of precommit
test on patches. The script we run is at ./dev-test/test-patch.sh. We could
add stuff in here but looking at aspirator as-is, it looks a bit tough to
integrate (build Chord then put in place files...). How hard to integrate into
findbugs? Then your work would get wide dissemination?
> Review in source the paper "Simple Testing Can Prevent Most Critical Failures"
> ------------------------------------------------------------------------------
>
> Key: HBASE-12187
> URL: https://issues.apache.org/jira/browse/HBASE-12187
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Critical
>
> Review the helpful paper
> https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-yuan.pdf
> It describes 'catastrophic failures', especially issues where exceptions are
> thrown but not properly handled. Their static analysis tool Aspirator turns
> up a bunch of the obvious offenders (Lets add to test-patch.sh alongside
> findbugs?). This issue is about going through code base making sub-issues to
> root out these and others (Don't we have the test described in figure #6
> already? I thought we did? If we don't, need to add).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
