You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2015/07/22 19:28:04 UTC

[jira] [Updated] (THRIFT-3201) Capture github test artifacts for failed builds

     [ https://issues.apache.org/jira/browse/THRIFT-3201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James E. King, III updated THRIFT-3201:
---------------------------------------
    Description: 
I submitted a pull request (https://travis-ci.org/apache/thrift/jobs/68196878) which had a lot of failures.  I want to see the output from "make cross" tests that failed because it does not fail for me locally.  I have no way of knowing how these tests failed in the build environment.

Resolved: click on after_failure in travis at the end to get the client and server logs.

  was:I submitted a pull request (https://travis-ci.org/apache/thrift/jobs/68196878) which had a lot of failures.  I want to see the output from "make cross" tests that failed because it does not fail for me locally.  I have no way of knowing how these tests failed in the build environment.


> Capture github test artifacts for failed builds
> -----------------------------------------------
>
>                 Key: THRIFT-3201
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3201
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Build Process
>    Affects Versions: 0.9.2
>            Reporter: James E. King, III
>            Assignee: James E. King, III
>            Priority: Critical
>             Fix For: 0.9.3
>
>
> I submitted a pull request (https://travis-ci.org/apache/thrift/jobs/68196878) which had a lot of failures.  I want to see the output from "make cross" tests that failed because it does not fail for me locally.  I have no way of knowing how these tests failed in the build environment.
> Resolved: click on after_failure in travis at the end to get the client and server logs.



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