[jira] [Commented] (BEAM-739) Log full exception stack trace in WordCountIT and BigQueryTornadoesIT

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563621#comment-15563621 ] 

ASF GitHub Bot commented on BEAM-739:
-------------------------------------

GitHub user peihe opened a pull request:

    https://github.com/apache/incubator-beam/pull/1079

    [BEAM-739] Log exceptions full stack track in IT tests

    R: @lukecwik @jasonkuster

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

    $ git pull https://github.com/peihe/incubator-beam log-stack-trace

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

    https://github.com/apache/incubator-beam/pull/1079.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 #1079
    
----
commit 3f70aeb2ba6a66b1b445253f5aba34e4074be6e8
Author: Pei He <pe...@google.com>
Date:   2016-10-10T21:39:55Z

    [BEAM-739] Log exceptions full stack track in IT tests

----


> Log full exception stack trace in WordCountIT and BigQueryTornadoesIT
> ---------------------------------------------------------------------
>
>                 Key: BEAM-739
>                 URL: https://issues.apache.org/jira/browse/BEAM-739
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Pei He
>            Assignee: Pei He
>            Priority: Minor
>
> When IT tests are broken, they don't provide the full stack trace, such as in:
> https://issues.apache.org/jira/browse/BEAM-736
> It makes investigating root causes slower.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)