On Sun, Sep 6, 2026 at 3:10 AM Philip Paeps <[email protected]> wrote: > On 2026-09-06 02:48:30 (+0800), Antoine Brodin wrote: > > On Sat, Sep 5, 2026 at 2:56 PM Philip Paeps <[email protected]> > > wrote: > >> On 2026-09-05 20:53:19 (+0800), Philip Paeps wrote: > >>> On 2026-09-05 19:03:36 (+0800), [email protected] wrote: > >>>> The other pkg-fallout message contained lines indicating an issue > >>>> starting > >>>> casper: > >>>> > >>>> sha256: Unable to initialize casper: Invalid argument (Invallid > >>>> pdflags at fork 0x4) > >>>> sha256: Unable to initialize casper: Invalid argument (Invallid > >>>> pdflags at fork 0x4) > >>> > >>> We're seeing this automation output too. > >>> > >>>> Are the package builders broken? > >>> > >>> I wonder if current is broken? This is a build from yesterday. > >> > >> Specifically: > >> > >> beefy24.chi building (1082 remaining) > >> FreeBSD 16.0-CURRENT #0 main-n288854-c5d9485e7d7f > > > > This was the kernel was not recent enough, it is now fixed > > So this build is ok?
Yes this build is ok, it is the one before that was not ok. > It's a bit strange to see that message the first time the clusteradm > automation runs. Any idea what causes it? (I could go read the source > but ... :)) On the userland side, the commit may be: https://cgit.FreeBSD.org/src/commit/?id=1a296762b3d093e1fed4e74f9251206102f68355 On the kernel side, the commit may be: https://cgit.FreeBSD.org/src/commit/?id=bcdb6ba94d08554eeb9bde4d2468707a612f5d90 Antoine
