Re: Unit Test Framework

2017-05-23 Thread Gancho Tenev
One framework and justice for all (or to rule them all) :) > One framework :) I think most of us already agree that we should have: 1 unit test framework and 1 integration test framework and have all the tests run as part of our build / verification stage. How to get to that point is where I t

Building on the CI

2017-05-23 Thread Leif Hedstrom
Couple of quick reminders: 1) If you are a committer, you don't have to [approve ci] on a PR, when you “git push”, it will trigger automatically. 2) You do however have to post a comment [approve ci] on non-committer PRs, to get them to trip. You can delete that comment after a few seconds if y

Proposal for how we implement QUIC

2017-05-23 Thread Masakazu Kitajo
Hi all, In the last summit, we discussed about how we implement QUIC. Masaori and I proposed 4 things below, and as my understanding, there's no -1 so far. I'd like to propose them again on this list to make it official. Background: We are about to start implementing QUIC. Since we faced many HTT

Re: Reloading remap.config without restarting trafficserver

2017-05-23 Thread Nishant Gaurav
Thank you, James and Leif for your reply. There are couple of problems that I had while using TSReconfigure (from mgmtapi.h). There are some functions which have been defined in both ‘ts.h’ and ‘mgmtapi.h’ with different argument types which leads to conflict as both of them are C APIs, and funct

Re: Unit Test Framework

2017-05-23 Thread Jason Kenny
I would suggest for unit testing. https://github.com/philsquared/Catch This has been nice to use. This does not require use to sync a bunch of binaries to get it to work. I think most the of the plugins will test better with AuTest. There will still be a need to unit test APIs in trafficserver or

Re: Unit Test Framework

2017-05-23 Thread Alan M. Carroll
For full up plugin testing we (Yahoo!) are using the AUTest framework. In fact there are already plugin based tests checked in to master (see tests/gold_tests/pluginTests/header_rewrite for an example). I think that is fine for testing the plugin in situ and we should adopt it as our preferred

Re: Build failed in Jenkins: osx-master » clang,osx,debug #1601

2017-05-23 Thread John Rushford
I've run the regression tests several times here on OSX and am not seeing any failures. not sure why it failed when Jenkins ran it. On Tue, May 23, 2017 at 7:43 AM, John Rushford wrote: > I'll look into that parent selection regression test failure. > > John > > On Mon, May 22, 2017 at 11:01 PM

Re: Build failed in Jenkins: osx-master » clang,osx,debug #1601

2017-05-23 Thread John Rushford
I'll look into that parent selection regression test failure. John On Mon, May 22, 2017 at 11:01 PM, Shu Kit Chan wrote: > I am not too sure why the parent selection regression test fails on > osx-master build. > Anyone? > > Kit > > > -- Forwarded message -- > From: > Date: Mo