[
https://issues.apache.org/jira/browse/HAMA-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jungblut updated HAMA-486:
---------------------------------
Attachment: HAMA-486.patch
This patch should be good for this problem. I refactored abit and made two
classes (one test / one bsp) obsolete by putting it into the already existing
testcase.
This should be bullet proof now.
BTW the randbench tests seems really verbose, let's set the log outputs to
DEBUG.
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Hama parent POM ............................ SUCCESS [2.257s]
[INFO] Apache Hama Core .................................. SUCCESS [1:53.250s]
[INFO] Apache Hama Graph Package ......................... SUCCESS [2.071s]
[INFO] Apache Hama Examples .............................. SUCCESS [1:40.458s]
[INFO] Apache Hama YARN .................................. SUCCESS [39.646s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{noformat}
> Add unit test to verify correctness of messages between supersteps
> ------------------------------------------------------------------
>
> Key: HAMA-486
> URL: https://issues.apache.org/jira/browse/HAMA-486
> Project: Hama
> Issue Type: Test
> Components: bsp, test
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Priority: Blocker
> Fix For: 0.4.0
>
> Attachments: HAMA-486.patch
>
>
> Sometimes, sent messages to the next superstep are appears at (next + 2)th
> superstep. We need to fix this problem and add unit test to verify
> correctness of messages between supersteps.
--
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
