[jira] [Work logged] (BEAM-11436) Nullness checks are excessive for test classes

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BEAM-11436?focusedWorklogId=560184&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-560184 ]

ASF GitHub Bot logged work on BEAM-11436:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 02/Mar/21 22:57
            Start Date: 02/Mar/21 22:57
    Worklog Time Spent: 10m 
      Work Description: TheNeuralBit commented on pull request #14101:
URL: https://github.com/apache/beam/pull/14101#issuecomment-789284072


   Retest this please


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 560184)
    Time Spent: 5h  (was: 4h 50m)

> 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: Brian Hulette
>            Priority: P2
>              Labels: stale-assigned
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> 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)