beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From markflyhigh <>
Subject [GitHub] beam pull request #3688: [BEAM-1584] Add file clean up util for Python integ...
Date Fri, 04 Aug 2017 17:14:25 GMT
GitHub user markflyhigh opened a pull request:

    [BEAM-1584] Add file clean up util for Python integration tests

    Follow this checklist to help us incorporate your contribution quickly and easily:
     - [ ] Make sure there is a [JIRA issue](
filed for the change (usually before you start working on it).  Trivial changes like typos
do not require a JIRA issue.  Your pull request should address just this issue, without pulling
in other changes.
     - [ ] Each commit in the pull request should have a meaningful subject line and body.
     - [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in ApproximateQuantiles`,
where you replace `BEAM-XXX` with the appropriate JIRA issue.
     - [ ] Write a pull request description that is detailed enough to understand what the
pull request does, how, and why.
     - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
     - [ ] If this contribution is large, please file an Apache [Individual Contributor License
    - Wrap `FileSystems.delete` to do file cleanup in integration tests.
    - Add output cleanup to WordCountIT

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

    $ git pull cleanup-file

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 #3688
commit ca902351ce805e6a9b9860130bc0fb8eacaab3de
Author: Mark Liu <>
Date:   2017-08-03T23:33:07Z

    [BEAM-1584] Add file clean up util for integration tests


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 or file a JIRA ticket
with INFRA.

View raw message