[
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=508187&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-508187
]
ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Nov/20 16:58
Start Date: 05/Nov/20 16:58
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-722505029
OK this is finally healthy and ran in a normal amount of time (precommits
tend to be in the 30-60 minute range and this was 30). Only the tests for SDK
core are skipped. Hopefully we won't have to skip them forever, since
carelessness with nulls in tests is an annoying source of false issues. Going
to merge it!
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 508187)
Time Spent: 11h 50m (was: 11h 40m)
> [Umbrella] Eliminate nullability errors from Beam Java
> ------------------------------------------------------
>
> Key: BEAM-10402
> URL: https://issues.apache.org/jira/browse/BEAM-10402
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Kenneth Knowles
> Priority: P1
> Labels: Clarified, starter
> Time Spent: 11h 50m
> Remaining Estimate: 0h
>
> I enabled the checker framework and the core SDK exceeds 100 nullability
> errors immediately. We should make this number zero, since nullability errors
> are solved problem in computer science and they do periodically impact Beam.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
