[
https://issues.apache.org/jira/browse/BEAM-11436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266840#comment-17266840
]
Beam JIRA Bot commented on BEAM-11436:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Nullness checks are excessive for test classes
> ----------------------------------------------
>
> Key: BEAM-11436
> URL: https://issues.apache.org/jira/browse/BEAM-11436
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Brian Hulette
> Assignee: Kenneth Knowles
> Priority: P2
> Labels: stale-assigned
>
> We don't have checkerframework nullness annotations for JUnit, which often
> leads to difficult nullness errors. The most onerous is that assertNotNull
> requires the argument to be NonNull already.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
