On Tue, Sep 29, 2015 at 10:47:56AM -0700, Joe Stringer wrote: > On 28 September 2015 at 20:27, Ben Pfaff <b...@nicira.com> wrote: > > On Mon, Sep 28, 2015 at 07:36:37PM +0100, Daniele Di Proietto wrote: > >> Recently some testcases have been failing in travis because of a warning > >> related to the use of an L3 device (OpenVZ specific) inside the workers. > >> > >> To get travis tests working again we can move to the newer container > >> infrastructure: this commit does that. > >> > >> The disadvantage is that there's no sudo access anymore, but we can > >> install packages with the apt plugin, and we shouldn't use root for > >> anything else > >> > >> Tested-at: https://travis-ci.org/ddiproietto/ovs/builds/81764972 > >> Signed-off-by: Daniele Di Proietto <diproiet...@vmware.com> > >> CC: Joe Stringer <joestrin...@nicira.com> > > > > Thanks for doing this! > > +1 Appreciate you looking into this Daniele, keen to get back to stable CI :-) > > There's a few failures remaining, mostly in backports at the moment. > This one looks different though: > > https://travis-ci.org/openvswitch/ovs/jobs/82728444 > > Seems that we're using 'bc' somewhere, but this isn't installed by > default in the travis environment. Perhaps should either figure out an > alternative way to do whatever we're using bc for, or install bc as > well.
Based on the log, my guess is that that is happening somewhere in the kernel build system, so it's probably easiest to add bc to the packages we install. I don't see use of "bc" inside the OVS build system or tests. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
