beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-491) Reuse context and disable UI in the Spark runner tests
Date Tue, 26 Jul 2016 21:00:22 GMT


ASF GitHub Bot commented on BEAM-491:

GitHub user amitsela opened a pull request:

    [BEAM-491]-Reuse context and disable UI in the Spark runner tests

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    Rename dataflow to beam.

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

    $ git pull BEAM-491

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

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

    This closes #736
commit e62bfdb16dddfd19fc881e8a78df956bd0ef0ff1
Author: Sela <>
Date:   2016-07-26T20:47:06Z

    Reuse context and disable UI.
    Rename dataflow to beam.


> Reuse context and disable UI in the Spark runner tests 
> -------------------------------------------------------
>                 Key: BEAM-491
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>    Affects Versions: 0.1.0-incubating
>            Reporter: Amit Sela
>            Assignee: Amit Sela
>            Priority: Minor
>             Fix For: 0.2.0-incubating
> Currently, only RunnableOnService tests reuse the context for some reason, although surefire
is using 1 fork (no reuse). I don't see a reason why not to reuse in all surefire executions.
> UI could be disabled for test executions as well. This could also help with Jenkins ports
issues we've been experiencing. 

This message was sent by Atlassian JIRA

View raw message