Re: pkg/56586: Support keeping worklog of succeeded packages in pbulk

[manphiz <manphiz%gmail.com@localhost>]

On Wed, Dec 29, 2021 at 5:55 AM Joerg Sonnenberger <joerg%bec.de@localhost> wrote:
>
> The following reply was made to PR pkg/56586; it has been noted by GNATS.
>
> From: Joerg Sonnenberger <joerg%bec.de@localhost>
> To: gnats-bugs%netbsd.org@localhost
> Cc: pkg-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, pkgsrc-bugs%netbsd.org@localhost
> Subject: Re: pkg/56586: Support keeping worklog of succeeded packages in pbulk
> Date: Wed, 29 Dec 2021 14:53:36 +0100
>
>  On Tue, Dec 28, 2021 at 11:50:00AM +0000, manphiz%gmail.com@localhost wrote:
>  >      Currently in pbulk only the logs of failed packages will be
>  >      kept by default, but here is no way to keep the logs of
>  >      successfully built packages, which may be useful for debugging
>  >      packages that experience runtime issues by inspecting build
>  >      logs such as CFLAGS/LDFLAGAS, or possible issues that didn't
>  >      fail the build process.
>
>  I haven't run into a case where I want to keep the work log for a
>  successful build in all my years and were I don't just rebuild the
>  package interactively. Given how much space this would consume for a
>  regular build, I really don't see the point.
>
>  Joerg
>

Hi Joerg,

My use case is for this issue[1].  For sudo it'll be easier to search
the problem with "-Wl,-zrelro" flag without a big enough page size.
And it'll help with the gnupg2 issue more.  If you check the build log
I attached in [2], one of the utilities it built ended up in
segmentation fault but didn't fail the build process, and the produced
gpg2 program will segfault in runtime randomly too.  Because I built
it using pbulk which didn't support keeping logs for successful
packages and used a different prefix for all its builds, I had to
rebuild everything in the pkgsrc tree to get this build log, and given
Loongson being a 15+ year machine which wasn't even performant back
then, it took me another whole day to build all the dependencies of
gnupg2 to get this log.  It would be much easier if pbulk can just
keep the build log for helping debugging runtime issues like this.

As for the space concern, what I'm suggesting here is just to keep the
build logs, and it's really not much compared with size of a work
directory which pbulk already supports to keep by the "keep_wrkdir"
options, so I wouldn't worry too much, especially when this is turned
off by default.  Actually, I may take a step further by gzipping all
the build logs to save more spaces if desired.

[1] https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=56559
[2] https://mail-index.netbsd.org/port-mips/2021/12/21/msg001201.html