[jira] [Commented] (GIRAPH-48) All tests failing under non-secure build
[
https://issues.apache.org/jira/browse/GIRAPH-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123926#comment-13123926
]
Jakob Homan commented on GIRAPH-48:
---
+1 on the fix, although most of the patch appears to be whitespace changes...
> All tests failing under non-secure build
>
>
> Key: GIRAPH-48
> URL: https://issues.apache.org/jira/browse/GIRAPH-48
> Project: Giraph
> Issue Type: Bug
>Reporter: Jakob Homan
>Priority: Critical
>
> After GIRAPH-12, quite a lot of tests are failing when run under non-secure
> hadoop:
> {noformat}mvn -Dhadoop=non_secure clean test{noformat}
> results in:
> {noformat}Failed tests:
> testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer)
> testBspCheckpoint(org.apache.giraph.TestManualCheckpoint)
> testBspSuperStep(org.apache.giraph.TestBspBasic)
> testBspMsg(org.apache.giraph.TestBspBasic)
> testBspCombiner(org.apache.giraph.TestBspBasic)
> testBspPageRank(org.apache.giraph.TestBspBasic)
> testBspShortestPaths(org.apache.giraph.TestBspBasic)
> testMutateGraph(org.apache.giraph.TestMutateGraphVertex)
> testContinue(org.apache.giraph.TestJsonBase64Format){noformat}
> rolling back to the previous commit, the tests pass.
--
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
[jira] [Commented] (GIRAPH-48) All tests failing under non-secure build
[
https://issues.apache.org/jira/browse/GIRAPH-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123935#comment-13123935
]
Avery Ching commented on GIRAPH-48:
---
Yeah, Eclipse automatically does that. The main change is very small:
int numWorkers = conf.getInt(GiraphJob.MAX_WORKERS, numTasks);
-// if the number of flush threads is unset, it is set to
-// the number of max workers.
-int numFlushThreads = conf.getInt(GiraphJob.MSG_NUM_FLUSH_THREADS,
numWorkers-1);
+// If the number of flush threads is unset, it is set to
+// the number of max workers - 1 or a minimum of 1.
+int numFlushThreads =
+ Math.max(conf.getInt(GiraphJob.MSG_NUM_FLUSH_THREADS,
+ numWorkers - 1),
+ 1);
Thanks for the quick review! I've check it in.
> All tests failing under non-secure build
>
>
> Key: GIRAPH-48
> URL: https://issues.apache.org/jira/browse/GIRAPH-48
> Project: Giraph
> Issue Type: Bug
>Reporter: Jakob Homan
>Priority: Critical
>
> After GIRAPH-12, quite a lot of tests are failing when run under non-secure
> hadoop:
> {noformat}mvn -Dhadoop=non_secure clean test{noformat}
> results in:
> {noformat}Failed tests:
> testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer)
> testBspCheckpoint(org.apache.giraph.TestManualCheckpoint)
> testBspSuperStep(org.apache.giraph.TestBspBasic)
> testBspMsg(org.apache.giraph.TestBspBasic)
> testBspCombiner(org.apache.giraph.TestBspBasic)
> testBspPageRank(org.apache.giraph.TestBspBasic)
> testBspShortestPaths(org.apache.giraph.TestBspBasic)
> testMutateGraph(org.apache.giraph.TestMutateGraphVertex)
> testContinue(org.apache.giraph.TestJsonBase64Format){noformat}
> rolling back to the previous commit, the tests pass.
--
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
[jira] [Issue Comment Edited] (GIRAPH-48) All tests failing under non-secure build
[
https://issues.apache.org/jira/browse/GIRAPH-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123935#comment-13123935
]
Avery Ching edited comment on GIRAPH-48 at 10/10/11 7:40 AM:
-
Yeah, Eclipse automatically does that. The main change is very small:
int numWorkers = conf.getInt(GiraphJob.MAX_WORKERS, numTasks);
-// if the number of flush threads is unset, it is set to
-// the number of max workers.
-int numFlushThreads = conf.getInt(GiraphJob.MSG_NUM_FLUSH_THREADS,
numWorkers-1);
+// If the number of flush threads is unset, it is set to
+// the number of max workers - 1 or a minimum of 1.
+int numFlushThreads =
+ Math.max(conf.getInt(GiraphJob.MSG_NUM_FLUSH_THREADS,
+ numWorkers - 1),
+ 1);
Thanks for the quick review! I've checked it in.
was (Author: aching):
Yeah, Eclipse automatically does that. The main change is very small:
int numWorkers = conf.getInt(GiraphJob.MAX_WORKERS, numTasks);
-// if the number of flush threads is unset, it is set to
-// the number of max workers.
-int numFlushThreads = conf.getInt(GiraphJob.MSG_NUM_FLUSH_THREADS,
numWorkers-1);
+// If the number of flush threads is unset, it is set to
+// the number of max workers - 1 or a minimum of 1.
+int numFlushThreads =
+ Math.max(conf.getInt(GiraphJob.MSG_NUM_FLUSH_THREADS,
+ numWorkers - 1),
+ 1);
Thanks for the quick review! I've check it in.
> All tests failing under non-secure build
>
>
> Key: GIRAPH-48
> URL: https://issues.apache.org/jira/browse/GIRAPH-48
> Project: Giraph
> Issue Type: Bug
>Reporter: Jakob Homan
>Priority: Critical
>
> After GIRAPH-12, quite a lot of tests are failing when run under non-secure
> hadoop:
> {noformat}mvn -Dhadoop=non_secure clean test{noformat}
> results in:
> {noformat}Failed tests:
> testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer)
> testBspCheckpoint(org.apache.giraph.TestManualCheckpoint)
> testBspSuperStep(org.apache.giraph.TestBspBasic)
> testBspMsg(org.apache.giraph.TestBspBasic)
> testBspCombiner(org.apache.giraph.TestBspBasic)
> testBspPageRank(org.apache.giraph.TestBspBasic)
> testBspShortestPaths(org.apache.giraph.TestBspBasic)
> testMutateGraph(org.apache.giraph.TestMutateGraphVertex)
> testContinue(org.apache.giraph.TestJsonBase64Format){noformat}
> rolling back to the previous commit, the tests pass.
--
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
[jira] [Assigned] (GIRAPH-48) All tests failing under non-secure build
[
https://issues.apache.org/jira/browse/GIRAPH-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Avery Ching reassigned GIRAPH-48:
-
Assignee: Avery Ching
> All tests failing under non-secure build
>
>
> Key: GIRAPH-48
> URL: https://issues.apache.org/jira/browse/GIRAPH-48
> Project: Giraph
> Issue Type: Bug
>Reporter: Jakob Homan
>Assignee: Avery Ching
>Priority: Critical
>
> After GIRAPH-12, quite a lot of tests are failing when run under non-secure
> hadoop:
> {noformat}mvn -Dhadoop=non_secure clean test{noformat}
> results in:
> {noformat}Failed tests:
> testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer)
> testBspCheckpoint(org.apache.giraph.TestManualCheckpoint)
> testBspSuperStep(org.apache.giraph.TestBspBasic)
> testBspMsg(org.apache.giraph.TestBspBasic)
> testBspCombiner(org.apache.giraph.TestBspBasic)
> testBspPageRank(org.apache.giraph.TestBspBasic)
> testBspShortestPaths(org.apache.giraph.TestBspBasic)
> testMutateGraph(org.apache.giraph.TestMutateGraphVertex)
> testContinue(org.apache.giraph.TestJsonBase64Format){noformat}
> rolling back to the previous commit, the tests pass.
--
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
[jira] [Resolved] (GIRAPH-48) All tests failing under non-secure build
[
https://issues.apache.org/jira/browse/GIRAPH-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Avery Ching resolved GIRAPH-48.
---
Resolution: Fixed
> All tests failing under non-secure build
>
>
> Key: GIRAPH-48
> URL: https://issues.apache.org/jira/browse/GIRAPH-48
> Project: Giraph
> Issue Type: Bug
>Reporter: Jakob Homan
>Assignee: Avery Ching
>Priority: Critical
>
> After GIRAPH-12, quite a lot of tests are failing when run under non-secure
> hadoop:
> {noformat}mvn -Dhadoop=non_secure clean test{noformat}
> results in:
> {noformat}Failed tests:
> testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer)
> testBspCheckpoint(org.apache.giraph.TestManualCheckpoint)
> testBspSuperStep(org.apache.giraph.TestBspBasic)
> testBspMsg(org.apache.giraph.TestBspBasic)
> testBspCombiner(org.apache.giraph.TestBspBasic)
> testBspPageRank(org.apache.giraph.TestBspBasic)
> testBspShortestPaths(org.apache.giraph.TestBspBasic)
> testMutateGraph(org.apache.giraph.TestMutateGraphVertex)
> testContinue(org.apache.giraph.TestJsonBase64Format){noformat}
> rolling back to the previous commit, the tests pass.
--
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
[jira] [Commented] (GIRAPH-48) All tests failing under non-secure build
[
https://issues.apache.org/jira/browse/GIRAPH-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123936#comment-13123936
]
Hudson commented on GIRAPH-48:
--
Integrated in Giraph-trunk-Commit #15 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/15/])
GIRAPH-48: numFlushThreads is 0 when doing a single worker
unittest. Changing the minimum to 1. (aching)
aching : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180805
Files :
* /incubator/giraph/trunk/CHANGELOG
*
/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/BasicRPCCommunications.java
> All tests failing under non-secure build
>
>
> Key: GIRAPH-48
> URL: https://issues.apache.org/jira/browse/GIRAPH-48
> Project: Giraph
> Issue Type: Bug
>Reporter: Jakob Homan
>Assignee: Avery Ching
>Priority: Critical
>
> After GIRAPH-12, quite a lot of tests are failing when run under non-secure
> hadoop:
> {noformat}mvn -Dhadoop=non_secure clean test{noformat}
> results in:
> {noformat}Failed tests:
> testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer)
> testBspCheckpoint(org.apache.giraph.TestManualCheckpoint)
> testBspSuperStep(org.apache.giraph.TestBspBasic)
> testBspMsg(org.apache.giraph.TestBspBasic)
> testBspCombiner(org.apache.giraph.TestBspBasic)
> testBspPageRank(org.apache.giraph.TestBspBasic)
> testBspShortestPaths(org.apache.giraph.TestBspBasic)
> testMutateGraph(org.apache.giraph.TestMutateGraphVertex)
> testContinue(org.apache.giraph.TestJsonBase64Format){noformat}
> rolling back to the previous commit, the tests pass.
--
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
[jira] [Commented] (GIRAPH-47) Export Worker's Context/State to vertices through pre/post/Application/Superstep
[ https://issues.apache.org/jira/browse/GIRAPH-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124097#comment-13124097 ] Claudio Martella commented on GIRAPH-47: I've given a thought or two to this interface and I cannot really see an easy way to pass information to the WorkerContext, a part of the initialize(). For example, for my particular Emitter scenario, how would i pass at preSuperstep() or postSuperstep() data to write to the HDFS or in general some parameters that might be needed? One way would be to create at Vertex.preApplication() a shared List, where I'd put the data that the WorkerContext would then dump to disk. It's not the best way as it could potentially eat a lot of memory. Or, I could add an emit() method to the implementing class and call it directly in compute(), like: ((MyEmitterWorkerContext)this.getWorkerContext()).emit(mydata). The engineering should be able to handle this quite easily (except for the cast cost each time, which is something). Any idea? > Export Worker's Context/State to vertices through > pre/post/Application/Superstep > > > Key: GIRAPH-47 > URL: https://issues.apache.org/jira/browse/GIRAPH-47 > Project: Giraph > Issue Type: Improvement > Components: graph >Affects Versions: 0.70.0 >Reporter: Claudio Martella >Assignee: Claudio Martella > > It would be quite useful for vertices to reach some worker-related > information stored i.e. in the GraphState class. > This information could be exported as a parameter to > pre/post/Application/Superstep like this: > public void preApplication(Configurable workerObject); > public void postApplication(Configurable workerObject); > public void preSuperstep(Configurable workerObject); > public void postSuperstep(Configurable workerObject); > public Configurable getWorkerObject(); > Another possibility is to add a Context inner class to BasicVertex to store > this information. -- 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
[jira] [Created] (GIRAPH-50) package/test failure with maven 2.2.1
package/test failure with maven 2.2.1 - Key: GIRAPH-50 URL: https://issues.apache.org/jira/browse/GIRAPH-50 Project: Giraph Issue Type: Bug Environment: maven 2.2.1 Reporter: Mitul Tiwari Priority: Minor package/test works with maven 3.0.3, but package/test does not with maven 2.2.1. For example, the following command results in an error: $ /usr/bin/mvn221 -Dhadoop=non_secure package Last few lines of error: Results : Failed tests: testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer) testBspCheckpoint(org.apache.giraph.TestManualCheckpoint) testBspSuperStep(org.apache.giraph.TestBspBasic) testBspMsg(org.apache.giraph.TestBspBasic) testBspCombiner(org.apache.giraph.TestBspBasic) testBspPageRank(org.apache.giraph.TestBspBasic) testBspShortestPaths(org.apache.giraph.TestBspBasic) testMutateGraph(org.apache.giraph.TestMutateGraphVertex) testContinue(org.apache.giraph.TestJsonBase64Format) Tests run: 27, Failures: 9, Errors: 0, Skipped: 0 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /Users/mtiwari/pkgs/giraph/Apache/giraph/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Mon Oct 10 11:23:37 PDT 2011 [INFO] Final Memory: 51M/106M [INFO] -- 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
[jira] [Updated] (GIRAPH-50) package/test failure with maven 2.2.1
[ https://issues.apache.org/jira/browse/GIRAPH-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mitul Tiwari updated GIRAPH-50: --- Description: package/test works with maven 3.0.3, but package/test does not work with maven 2.2.1. For example, the following command results in an error: $ /usr/bin/mvn221 -Dhadoop=non_secure package Last few lines of error: Results : Failed tests: testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer) testBspCheckpoint(org.apache.giraph.TestManualCheckpoint) testBspSuperStep(org.apache.giraph.TestBspBasic) testBspMsg(org.apache.giraph.TestBspBasic) testBspCombiner(org.apache.giraph.TestBspBasic) testBspPageRank(org.apache.giraph.TestBspBasic) testBspShortestPaths(org.apache.giraph.TestBspBasic) testMutateGraph(org.apache.giraph.TestMutateGraphVertex) testContinue(org.apache.giraph.TestJsonBase64Format) Tests run: 27, Failures: 9, Errors: 0, Skipped: 0 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /Users/mtiwari/pkgs/giraph/Apache/giraph/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Mon Oct 10 11:23:37 PDT 2011 [INFO] Final Memory: 51M/106M [INFO] was: package/test works with maven 3.0.3, but package/test does not with maven 2.2.1. For example, the following command results in an error: $ /usr/bin/mvn221 -Dhadoop=non_secure package Last few lines of error: Results : Failed tests: testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer) testBspCheckpoint(org.apache.giraph.TestManualCheckpoint) testBspSuperStep(org.apache.giraph.TestBspBasic) testBspMsg(org.apache.giraph.TestBspBasic) testBspCombiner(org.apache.giraph.TestBspBasic) testBspPageRank(org.apache.giraph.TestBspBasic) testBspShortestPaths(org.apache.giraph.TestBspBasic) testMutateGraph(org.apache.giraph.TestMutateGraphVertex) testContinue(org.apache.giraph.TestJsonBase64Format) Tests run: 27, Failures: 9, Errors: 0, Skipped: 0 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced a shutdown hook kill of the ZooKeeper process. 11/10/10
[jira] [Commented] (GIRAPH-50) package/test failure with maven 2.2.1
[ https://issues.apache.org/jira/browse/GIRAPH-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124379#comment-13124379 ] Jakob Homan commented on GIRAPH-50: --- This is due to the munging plugin not playing nice with Maven 2. I'd suggest we just update the requirements section to include Maven 3 rather than Maven 2. No sense living in the past. Mitul, can you come up with a patch for this? > package/test failure with maven 2.2.1 > - > > Key: GIRAPH-50 > URL: https://issues.apache.org/jira/browse/GIRAPH-50 > Project: Giraph > Issue Type: Bug > Environment: maven 2.2.1 >Reporter: Mitul Tiwari >Priority: Minor > > package/test works with maven 3.0.3, but package/test does not work with > maven 2.2.1. For example, the following command results in an error: > $ /usr/bin/mvn221 -Dhadoop=non_secure package > Last few lines of error: > Results : > Failed tests: > testSuperstepBalancer(org.apache.giraph.TestVertexRangeBalancer) > testBspCheckpoint(org.apache.giraph.TestManualCheckpoint) > testBspSuperStep(org.apache.giraph.TestBspBasic) > testBspMsg(org.apache.giraph.TestBspBasic) > testBspCombiner(org.apache.giraph.TestBspBasic) > testBspPageRank(org.apache.giraph.TestBspBasic) > testBspShortestPaths(org.apache.giraph.TestBspBasic) > testMutateGraph(org.apache.giraph.TestMutateGraphVertex) > testContinue(org.apache.giraph.TestJsonBase64Format) > Tests run: 27, Failures: 9, Errors: 0, Skipped: 0 > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > 11/10/10 11:23:37 WARN zk.ZooKeeperManager: onlineZooKeeperServers: Forced > a shutdown hook kill of the ZooKeeper process. > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > Please refer to > /Users/mtiwari/pkgs/giraph/Apache/giraph/target/surefire-reports for the > individual test results. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 23 seconds > [INFO] Finished at: Mon Oct 10 11:23:37 PDT 2011 > [INFO] Final Memory: 51M/106M > [INFO] > -- 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
[jira] [Created] (GIRAPH-51) Provide unit testing tool for Giraph algorithms
Provide unit testing tool for Giraph algorithms --- Key: GIRAPH-51 URL: https://issues.apache.org/jira/browse/GIRAPH-51 Project: Giraph Issue Type: Improvement Reporter: Jakob Homan It would be nice to have a little tool, similar to MRUnit, that would allow Giraph application writers to quickly unit test their algorithms. The tool could take a Vertex implementation, a set of input and expected output and verify that after the specified number of supersteps, we've gotten what we expect. -- 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
[jira] [Commented] (GIRAPH-51) Provide unit testing tool for Giraph algorithms
[ https://issues.apache.org/jira/browse/GIRAPH-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124553#comment-13124553 ] Sebastian Schelter commented on GIRAPH-51: -- It would be great to have something like this, I have my students look at giraph currently and one of their first problems was how to write a simple unit case for some algorithm they wanna implement. > Provide unit testing tool for Giraph algorithms > --- > > Key: GIRAPH-51 > URL: https://issues.apache.org/jira/browse/GIRAPH-51 > Project: Giraph > Issue Type: Improvement >Reporter: Jakob Homan > > It would be nice to have a little tool, similar to MRUnit, that would allow > Giraph application writers to quickly unit test their algorithms. The tool > could take a Vertex implementation, a set of input and expected output and > verify that after the specified number of supersteps, we've gotten what we > expect. -- 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
