Re: continuous integration status update

[Denis Ovsienko via tcpdump-workers <tcpdump-workers () lists tcpdump org>]

> --- Begin Message ---
>
>
> From: Denis Ovsienko <denis () ovsienko info>
>
> Date: Thu, 4 Mar 2021 19:06:17 +0000
>
> On Thu, 4 Mar 2021 00:42:23 -0800
> Guy Harris <gharris () sonic net> wrote:
>
> > On Mar 3, 2021, at 2:30 PM, Denis Ovsienko via tcpdump-workers
> > <tcpdump-workers () lists tcpdump org> wrote:
> >
> > > A partial replacement for that service is ci.tcpdump.org, which is a
> > > buildbot instance doing Linux AArch64 builds for the github.com
> > > repositories.  
> >
> > So where is that hosted?  Are you hosting it yourself or hosting it
> > on some cloud service?
>
> ci.tcpdump.org is a brand new €3/month Linux VM, it runs the buildbot
> master. The linux-aarch64 buildbot worker is running on a Raspberry Pi
> next to my desk. After getting the Pi setup right the time to complete
> build_matrix.sh went from 18 to 7 minutes for libpcap and from 81 to 34
> minutes for tcpdump.
>
> Looking at top output on the worker, this can be further improved
> because a lot of time is spent slowly making through configure or cmake
> tests on a single CPU core, and the main compilation stage is fast
> mainly because of ccache. So the same solution as what is currently used
> for Cirrus CI Linux (build matrix split into 2 or even 4) would likely
> make the process more parallel.
>
> One simple way to do that would be to have virtual workers (e.g.
> linux-aarch64-gcc and linux-aarch64-clang with MATRIX_CC nailed down to
> a local constant). I considered that, but realized that would be more
> difficult to maintain because this detail conceptually belongs to the
> "builder" component of buildbot master. So this space for improvement
> is going to remain for a bit longer.
>
> -- 
>     Denis Ovsienko
>
> --- End Message ---
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers