You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Adam Antal (JIRA)" <ji...@apache.org> on 2019/04/17 14:58:00 UTC
[jira] [Commented] (YARN-9495) Fix findbugs warnings in
hadoop-yarn-server-resourcemanager module
[ https://issues.apache.org/jira/browse/YARN-9495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820158#comment-16820158 ]
Adam Antal commented on YARN-9495:
----------------------------------
Thanks for noticing that.
It looks appropriate to add these to findbugs-exclude. Just for sure, could you trigger jenkins on your patch (setting this issue Patch available)?
> Fix findbugs warnings in hadoop-yarn-server-resourcemanager module
> ------------------------------------------------------------------
>
> Key: YARN-9495
> URL: https://issues.apache.org/jira/browse/YARN-9495
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Tao Yang
> Assignee: Tao Yang
> Priority: Minor
> Attachments: YARN-9495.001.patch, image-2019-04-17-18-22-40-624.png
>
>
> Recently there are 2 extant Findbugs warnings in hadoop-yarn-server-resourcemanager module according to the jenkins report of YARN-9439/YARN-9440 as follow:
> !image-2019-04-17-18-22-40-624.png!
> They seems not expect null input for com.google.common.util.concurrent.SettableFuture#set even through they are indeed declared as Nullable, perhaps since findbugs can support javax.annotation.Nullable but not org.checkerframework.checker.nullness.qual.Nullable.
> I think we should exclude these two warnings through adding them into hadoop-yarn/dev-support/findbugs-exclude.xml.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org