[
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=506456&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-506456
]
ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Oct/20 23:21
Start Date: 29/Oct/20 23:21
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #13134:
URL: https://github.com/apache/beam/pull/13134#issuecomment-719078555
On my idle desktop machine:
- `git checkout github/master && ./gradlew :javaPreCommit --continue
--no-build-cache --rerun-tasks --scan`
https://scans.gradle.com/s/cdfrii6qsopii/timeline?sort=longest
- `git checkout checkerframework-classlevel && ./gradlew :javaPreCommit
--continue --no-build-cache --rerun-tasks --scan`
https://scans.gradle.com/s/2r65rr5mflsro/timeline?sort=longest
Unfortunate that the build seems very unhealthy on master so I am just
looking at particular tasks. It does look like compile tasks are perhaps 5x as
slow but it does not affect the overall runtime very much. One option is to
cease analyzing test java. These seem to have a much greater slowdown factor. I
wonder if incorrect types are more expensive than correct ones...
----------------------------------------------------------------
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: 506456)
Time Spent: 10h 40m (was: 10.5h)
> [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 40m
> 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)
