Just an update: we've hooked our regression system into the github
mirror and are now running minimal regression tests on bgpd. The tests
start at a commit and move to the head of the branch, commit by commit
-- pretty simple approach.
Each run does a compile, basic adjacency checks, some unicast and VRF
route distributions and checks the results against a reference (known
good run). Each run takes about 4 minutes and there are about 160
commits in /8/proposed/ff - currently has about 150 to go.
I'll provide an update once we have interesting results.
Lou
PS I rebased the following commits to be 1st in order to get the
regression environment running:
Author: Lou Berger <lber...@labn.net>
Date: Tue May 17 07:10:37 2016 -0400
bgpd: Add flag to not change e{u,g}id on startup and run as
unprivileged user
* bgp_main.c: add -S / --skip_runas flag to not change effective
user/group
on start up. Enables bgpd to be run by unprivileged user.
Author: Lou Berger <lber...@labn.net>
Date: Tue May 17 07:10:36 2016 -0400
bgp: add "debug bgp allow-martians" next hops and related code/commands
Author: Lou Berger <lber...@labn.net>
Date: Tue May 17 12:19:51 2016 -0400
lib: change command logging to be off by default
* lib/vty.c: add 'log_command' to enable logging of vty commands
executed.
Default command logging to off.
On 7/11/2016 5:44 AM, Lou Berger wrote:
>> > Any luck pinning down what commits are causing which issues for you?
>> >
> Not yet. Thinking I'll try to wire into our regression system in some way...
>
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-dev
