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

Aki Sukegawa commented on THRIFT-4095:
--------------------------------------

[~jking3] tests for header servers are included in our CI.
https://travis-ci.org/apache/thrift/jobs/201991012#L7702
They are located in test/features and can be run by test/test.py --features or 
make crossfeature
I'm afraid that the only documentation available is a single sentence in 
test/test.py --help .

To add tests to existing or new jobs, any contributor or committer can edit 
.travis-ci.yml and issue a pull request.

> Add multiplexed and other missing protocols to Travis CI
> --------------------------------------------------------
>
>                 Key: THRIFT-4095
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4095
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Build Process
>    Affects Versions: 0.11.0
>         Environment: Travis CI
>            Reporter: James E. King, III
>            Assignee: Jake Farrell
>
> In THRIFT-3706 someone wants to contribute our first set of multiplexed cross 
> tests (c_glib client, java server).  These need to be represented in our 
> Travis CI builds, where we are limiting the protocols we test to keep build 
> jobs in a time box.
> Currently we have the following four build jobs running crosstest:
> * #1 uses the ubuntu image and runs "binary|header" on everything except 
> netcore and rust
> * #2 uses the debian image and does the same as #1
> * #3 uses the ubuntu image and runs "compact|json" on everything except 
> netcore and rust
> * #4 uses the debian image and does the same as #3
> The following protocols are not represented in the Travis CI builds and 
> should be added:
> * header
> * multiplexed
> There are not many of these.  They could be added to build job #2 which seems 
> to have enough headroom to run the few extra tests this would generate.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to