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-2529) SpannerWriteIT failing in postcommit
Date Wed, 28 Jun 2017 14:17:00 GMT


ASF GitHub Bot commented on BEAM-2529:

GitHub user kennknowles opened a pull request:

    [BEAM-2529] Only use letters to generate Spanner database names

    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`.
     - [ ] 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](
    We are seeing NPEs in SpannerWriteIT, [like this one]($beam-runners-google-cloud-dataflow-java/lastCompletedBuild/testReport/

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

    $ git pull SpannerWriteIT

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 #3459
commit f8fcd49cfb6bd8fb599846bc862a142f5e5e34d7
Author: Kenneth Knowles <>
Date:   2017-06-28T14:12:51Z

    Only use letters to generate Spanner database names


> SpannerWriteIT failing in postcommit
> ------------------------------------
>                 Key: BEAM-2529
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-gcp
>            Reporter: Kenneth Knowles
>            Assignee: Ismaël Mejía
>            Priority: Blocker
> There are some NPEs and some other issues after the upgrade of commons-lang3 in

This message was sent by Atlassian JIRA

View raw message