[
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=506313&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-506313
]
ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Oct/20 17:47
Start Date: 29/Oct/20 17:47
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-718917231
Yea on the bad run it is claiming that compiling the SDK took 16 minutes and
compiling the SDK's tests took 30 minutes. So that is orders of magnitude more
than what I can repro. Something is awry. I'm going to try a rebase which
should un-cache those and we can see if it was isolated. I suspect it was not.
----------------------------------------------------------------
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: 506313)
Time Spent: 10h 10m (was: 10h)
> [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: 10h 10m
> 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)
