Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-02-10 Thread Francois-Xavier Le Bail via tcpdump-workers
--- Begin Message --- On 03/02/2021 17:50, Francois-Xavier Le Bail via tcpdump-workers wrote: > These scripts can be used locally for build tests, used on other CI and > easily be updated to run new tests (32 bits builds, sanitizers, coverage, > etc). > > Next step is doing similar setup for

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-02-03 Thread Michael Richardson via tcpdump-workers
--- Begin Message --- Francois-Xavier Le Bail via tcpdump-workers wrote: > To save CI runtime, I have committed > a063c2d21417345ee583551ef2c07a0be6b32696 for libpcap. > This will currently run only five builders (amd64, arm64, ppc64le, > s390x and osx) and do the matrix

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-02-03 Thread Francois-Xavier Le Bail via tcpdump-workers
--- Begin Message --- On 01/02/2021 18:08, Denis Ovsienko via tcpdump-workers wrote: > On Mon, 18 Jan 2021 22:29:21 -0800 > Guy Harris via tcpdump-workers > wrote: > >> I guess we meet those requirements, although I'm not too keen on >> having to keep going hat-in-hand to them every time we run

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-02-01 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 18 Jan 2021 22:29:21 -0800 Guy Harris via tcpdump-workers wrote: > I guess we meet those requirements, although I'm not too keen on > having to keep going hat-in-hand to them every time we run out of > credits; hopefully, we can just get a renewable amount. I had

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-01-28 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 18 Jan 2021 22:29:21 -0800 Guy Harris via tcpdump-workers wrote: > So we can either migrate to travis-ci.com or use other providers. Travis has been downsizing the .org server pool for a couple weeks, so far it has went from 370 to 250 with apparent effect on the

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-01-21 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Thu, 21 Jan 2021 08:15:33 +0100 Dagobert Michelsen wrote: > Hi folks, > > Am 21.01.2021 um 04:24 schrieb Denis Ovsienko via tcpdump-workers > : > >>s390x (a/k/a z/Architecture, i.e. S/3x0-64) - a big-endian > >> platform, so we can do some testing of operation on

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-01-20 Thread Dagobert Michelsen via tcpdump-workers
--- Begin Message --- Hi folks, Am 21.01.2021 um 04:24 schrieb Denis Ovsienko via tcpdump-workers : >> s390x (a/k/a z/Architecture, i.e. S/3x0-64) - a big-endian >> platform, so we can do some testing of operation on big-endian >> machines. Just as a tiny comment: big-endian is also

Re: [tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-01-20 Thread Denis Ovsienko via tcpdump-workers
--- Begin Message --- On Mon, 18 Jan 2021 22:29:21 -0800 Guy Harris via tcpdump-workers wrote: > Travis CI is announcing on the travis-ci.org site that "... > travis-ci.org will be shutting down in several weeks, with all > accounts migrating to travis-ci.com. Please stay tuned here for more >

[tcpdump-workers] Stick with Travis for continuous integration, or switch?

2021-01-18 Thread Guy Harris via tcpdump-workers
--- Begin Message --- Travis CI is announcing on the travis-ci.org site that "... travis-ci.org will be shutting down in several weeks, with all accounts migrating to travis-ci.com. Please stay tuned here for more information." They don't provide any information there. However, at