The patch helps here too. I could not reproduce build failures coming
from NUL byte files yet (260 ports and counting).
I had another spurious build failure though, but I think this is unrelated:
===> Building for mpfr-4.1.0_1
Making all in doc
restore=: && backupdir=".am$$" && am__cwd=`pwd` &&
## Christoph Moench-Tegeder (c...@burggraben.net):
> I'm now going back to releng/13.0 and check if that still produces
> the broken files "sometimes" (in the true nature of a concurrency
> issue, the failure is somewhat stochastic).
That was quick: less than 15 minutes into that, I see the the f
## Christoph Moench-Tegeder (c...@burggraben.net):
> ## Mark Johnston (ma...@freebsd.org):
> > Mark or Thomas, if you're able
> > to build a new kernel from the releng/13.0 branch and test it, could you
> > please try this patch?
>
> I'm running that right now, building some 300+ ports (firefox
Testing the kernel patch right now, will report back asap.
Re mplayer warnings: That's on my todo list, thanks for the ping. It
has been fairly low prio though, since these errors are about no-ops
and transitive dependencies which qa.sh is overly eager to report.
On 2022-Mar-19, at 14:34, Mark Millard wrote:
> On 2022-Mar-19, at 14:24, Mark Millard wrote:
>
>> On 2022-Mar-19, at 12:54, Mark Johnston wrote:
>>
>>> On Sat, Mar 19, 2022 at 12:00:20PM -0700, Mark Millard wrote:
On 2022-Mar-19, at 11:07, Thomas Zander wrote:
> On Sat, 19 Ma
On 2022-Mar-19, at 14:24, Mark Millard wrote:
> On 2022-Mar-19, at 12:54, Mark Johnston wrote:
>
>> On Sat, Mar 19, 2022 at 12:00:20PM -0700, Mark Millard wrote:
>>> On 2022-Mar-19, at 11:07, Thomas Zander wrote:
>>>
On Sat, 19 Mar 2022 at 18:32, Mark Millard wrote:
> May be repo
## Mark Johnston (ma...@freebsd.org):
> > The primary difference is that I've never used ccache and
> > did not try to do so here. The "zfs pool is a single disk,
> > no raid, mirror or anything fancy" is accurate, as is the
> > use of ALLOW_MAKE_JOBS= .
That's basically my setup: "single-SSD zpo
On 2022-Mar-19, at 12:54, Mark Johnston wrote:
> On Sat, Mar 19, 2022 at 12:00:20PM -0700, Mark Millard wrote:
>> On 2022-Mar-19, at 11:07, Thomas Zander wrote:
>>
>>> On Sat, 19 Mar 2022 at 18:32, Mark Millard wrote:
May be report to Mark J. how to run the same test builds
that fail
On Sat, Mar 19, 2022 at 12:00:20PM -0700, Mark Millard wrote:
> On 2022-Mar-19, at 11:07, Thomas Zander wrote:
>
> > On Sat, 19 Mar 2022 at 18:32, Mark Millard wrote:
> >> May be report to Mark J. how to run the same test builds
> >> that failed for -p8 but worked for -p7?
> >
> > Sure, good po
The reports of corrupted files with zero-bytes seemed vaguely
familiar, including my own addition to the list. Turns out I'd
reported such for main [so: 14] back in 2021-Nov. My context
at the time was aarch64.
The following has my report sequence, including where I
got past the problem vs. before
On 2022-Mar-19, at 11:07, Thomas Zander wrote:
> On Sat, 19 Mar 2022 at 18:32, Mark Millard wrote:
>> May be report to Mark J. how to run the same test builds
>> that failed for -p8 but worked for -p7?
>
> Sure, good point.
> A build that reliably causes broken packages on p8 but not on p7 for
> From: Mark Johnston
> Date: Sat, 19 Mar 2022 12:42:59 -0400
> On Sat, Mar 19, 2022 at 12:40:45PM +0100, Thomas Zander wrote:
> > On Sat, 19 Mar 2022 at 12:11, Rene Ladan wrote:
> > >
> > > On Sat, Mar 19, 2022 at 11:04:58AM +0100, Thomas Zander wrote:
> > > > On Sat, 19 Mar 2022 at 09:00, Matt
12 matches
Mail list logo
