[
https://issues.apache.org/jira/browse/GIRAPH-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421878#comment-13421878
]
Avery Ching commented on GIRAPH-267:
------------------------------------
This looks good Jaeho, but is missing something.
Here's some info on contributing:
https://cwiki.apache.org/confluence/display/GIRAPH/How+to+Contribute
My build fails 'mvn clean verify'
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9.818s
[INFO] Finished at: Tue Jul 24 16:44:28 PDT 2012
[INFO] Final Memory: 17M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile
(default-testCompile) on project giraph: Compilation failure: Compilation
failure:
[ERROR]
/Users/aching/Avery/source/giraph_trunk2/target/munged/test/org/apache/giraph/TestPredicateLock.java:[51,25]
cannot find symbol
[ERROR] symbol : constructor PredicateLock()
[ERROR] location: class org.apache.giraph.zk.PredicateLock
[ERROR]
/Users/aching/Avery/source/giraph_trunk2/target/munged/test/org/apache/giraph/TestPredicateLock.java:[61,25]
cannot find symbol
[ERROR] symbol : constructor PredicateLock()
[ERROR] location: class org.apache.giraph.zk.PredicateLock
[ERROR]
/Users/aching/Avery/source/giraph_trunk2/target/munged/test/org/apache/giraph/TestPredicateLock.java:[77,25]
cannot find symbol
[ERROR] symbol : constructor PredicateLock()
Can you please fix the unittests?
> 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
>
>
> 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
