GitHub user willb opened a pull request:

    https://github.com/apache/spark/pull/415

    SPARK-1501: Ensure assertions in Graph.apply are asserted.

    The Graph.apply test in GraphSuite had some assertions in a closure in
    a graph transformation. As a consequence, these assertions never
    actually executed.  Furthermore, these closures had a reference to
    (non-serializable) test harness classes because they called assert(),
    which could be a problem if we proactively check closure serializability
    in the future.
    
    This commit simply changes the Graph.apply test to collect the graph
    triplets so it can assert about each triplet from a map method.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/willb/spark graphsuite-nop-fix

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/415.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #415
    
----
commit 0b636586b797546ce0cf78dbbfbe7462712aeaa4
Author: William Benton <[email protected]>
Date:   2014-03-14T16:40:56Z

    Ensure assertions in Graph.apply are asserted.
    
    The Graph.apply test in GraphSuite had some assertions in a closure in
    a graph transformation. As a consequence, these assertions never
    actually executed.  Furthermore, these closures had a reference to
    (non-serializable) test harness classes because they called assert(),
    which could be a problem if we proactively check closure serializability
    in the future.
    
    This commit simply changes the Graph.apply test to collect the graph
    triplets so it can assert about each triplet from a map method.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to