You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Micah Whitacre (JIRA)" <ji...@apache.org> on 2015/09/09 14:30:46 UTC
[jira] [Comment Edited] (CRUNCH-559) Crunch-Spark Integration Tests
not executing
[ https://issues.apache.org/jira/browse/CRUNCH-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736756#comment-14736756 ]
Micah Whitacre edited comment on CRUNCH-559 at 9/9/15 12:30 PM:
----------------------------------------------------------------
Yes it does...
{noformat}
Results :
Tests run: 63, Failures: 0, Errors: 0, Skipped: 0
{noformat}
Merged your patch and pushed to master.
[~joshwills], did the solution of constraining the code cache size come from experience or is that a best practice for Spark in general?
was (Author: mkwhitacre):
Yes it does...
{noformat}
Results :
Tests run: 63, Failures: 0, Errors: 0, Skipped: 0
{noformat}
Merged your patch and pushed to master.
> Crunch-Spark Integration Tests not executing
> --------------------------------------------
>
> Key: CRUNCH-559
> URL: https://issues.apache.org/jira/browse/CRUNCH-559
> Project: Crunch
> Issue Type: Bug
> Components: Spark
> Reporter: Micah Whitacre
> Assignee: Micah Whitacre
> Fix For: 0.14.0
>
> Attachments: CRUNCH-559.patch, CRUNCH-559b.patch
>
>
> When working on CRUNCH-557, I was noticing that when building crunch-spark I was only seeing
> {quote}
> Results :
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
> {quote}
> Which is odd because there are a lot of tests under this directory:
> https://github.com/apache/crunch/tree/master/crunch-spark/src/it/java/org/apache/crunch
> The reason is that the failsafe plugin[1] is to only run the Scala tests and even if it included the Java ones it wouldn't match with their test names.
> [1] - https://github.com/apache/crunch/blob/19c0c2d8d78ebb490334bf019965e74b44ff49c4/crunch-spark/pom.xml#L189
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)