[
https://issues.apache.org/jira/browse/GIRAPH-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421988#comment-13421988
]
Avery Ching commented on GIRAPH-267:
------------------------------------
Looks like you fixed the tests, but mvn clean verify is showing some checkstyle
errors. Can you please fix them?
[INFO] --- maven-checkstyle-plugin:2.9:check (default) @ giraph ---
[INFO]
[INFO] There are 7 checkstyle errors.
cat target/munged/checkstyle-result.xml | grep error
<error line="45" column="3" severity="error" message="Variable access
definition in wrong order."
source="com.puppycrawl.tools.checkstyle.checks.coding.DeclarationOrderCheck"/>
<error line="46" severity="error" message="Line matches the illegal pattern
'Trailing whitespace'."
source="com.puppycrawl.tools.checkstyle.checks.RegexpCheck"/>
<error line="50" column="6" severity="error" message="Unused @param tag for
'used'."
source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocMethodCheck"/>
<error line="52" column="37" severity="error" message="Expected @param tag for
'progressable'."
source="com.puppycrawl.tools.checkstyle.checks.javadoc.JavadocMethodCheck"/>
<error line="55" severity="error" message="Line matches the illegal pattern
'Trailing whitespace'."
source="com.puppycrawl.tools.checkstyle.checks.RegexpCheck"/>
<error line="130" severity="error" message="while child at indentation level 8
not at correct indentation, 6"
source="com.puppycrawl.tools.checkstyle.checks.indentation.IndentationCheck"/>
<error line="130" column="5" severity="error" message="File contains tab
characters (this is the first instance)."
source="com.puppycrawl.tools.checkstyle.checks.whitespace.FileTabCharacterCheck"/>
> Jobs can get killed for not reporting status during INPUT SUPERSTEP
> -------------------------------------------------------------------
>
> Key: GIRAPH-267
> URL: https://issues.apache.org/jira/browse/GIRAPH-267
> Project: Giraph
> Issue Type: Bug
> Components: graph
> Affects Versions: 0.2.0
> Environment: Facebook Hadoop
> Reporter: Jaeho Shin
> Assignee: Jaeho Shin
> Fix For: 0.2.0
>
> Attachments:
> 0001-Made-PredicateLock-report-progress-and-removed-Conte.patch,
> GIRAPH-267.patch
>
>
> Job with a skewed and long (>600secs in my case) INPUT_SUPERSTEP fails for
> some tasks not reporting their status. From BspServiceWorker#setup(), I
> could tell while some workers were still loading inputSplits, others finished
> theirs early and hanged on PredicateLock#waitForever(), and got killed after
> the timeout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
