Date: Wed, 26 Nov 2025 08:31:17 +0100 From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= <olivier@freebsd.org> To: freebsd-current@freebsd.org, src-committers@freebsd.org Cc: Gleb Smirnoff <glebius@freebsd.org> Subject: Re: November 2025 stabilization week Message-ID: <CA%2Bq%2BTcq61_-_pVtuBwFiAUb5sYOZyd9CD62g27hmMYftOY1AMw@mail.gmail.com> In-Reply-To: <CA%2Bq%2BTcpb2vdwym2BP5BcVp1YrqQU2b3y4mXv3tMDh-BCYuU_zw@mail.gmail.com> References: <aSQeqkR-G9VYKP4s@cell.glebi.us> <CA%2Bq%2BTcpb2vdwym2BP5BcVp1YrqQU2b3y4mXv3tMDh-BCYuU_zw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Hello everyone, There is a critical regression related to the zfsbootcfg/bectl utility. The issue was encountered when attempting to upgrade one of our clusters that was already running a Nov 2025 stabweek. The bug prevents successful activation of a new boot environment via bectl activate -t xxx. Given that this regression actively prevents system upgrades and new deployments, it appears to be a serious blocker. The issue match this Bugzilla: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291211 Regards, Olivier On Wed, Nov 26, 2025 at 12:31 AM Olivier Cochard-Labbé <olivier@freebsd.org> wrote: > Hello everyone, > > This is an update on the current November 2025 stabilization week on our > Netflix A/B test deployment. > We had one significant finding: > dhw@ noticed a regression (higher system CPU utilization), which was > quickly troubleshooted by gallatin@, patched by chs@, and pushed by imp@. > This was excellent teamwork! > The fix is in the following commit: > "git: 2b4dbad2db57 - main - nda: fix setting of unmappedio flag" > > On my end, my personal build machine, Workstation, NAS, and laptop have > all been upgraded, and I have not observed any further regressions. > > Separately, reading the -current mailing list, thj@ reported an issue > with the 20251124 16-CURRENT snapshot, which appears to be very close to > the stabweek state. You can view the report here: > https://lists.freebsd.org/archives/freebsd-current/2025-November/009491.html > > I will keep the stabilization window open for one more day to allow for > any final reports before officially closing the stabweek. > > Regards, > > Olivier > > On Mon, Nov 24, 2025 at 10:00 AM Gleb Smirnoff <glebius@freebsd.org> > wrote: > >> Hi FreeBSD/main users & developers: >> >> This is an automated email to inform you that the November 2025 >> stabilization week >> started with FreeBSD/main at main-n282109-a067eb525e10, which was tagged >> as >> main-stabweek-2025-Nov. >> >> Those who want to participate in the stabilization week are encouraged to >> update to the above revision/tag and test their systems. >> >> The tag main-stabweek-2025-Nov has been published at Gleb Smirnoff's >> github repo. >> To connect this repo as an additional remote you need to run: >> >> git remote add glebius https://github.com/glebius/FreeBSD >> >> Once remote is configured, to checkout the tag run: >> >> git fetch glebius --tags >> git checkout main-stabweek-2025-Nov >> >> If you want to use only the official FreeBSD repo, then update to >> the revision: >> >> git pull >> git checkout a067eb525e10 >> >> Developers are encouraged to avoid pushing new features to FreeBSD/main >> during >> the stabilization week, but focus on bugfixes instead. The stabilization >> week >> runs up to Friday 18:00 UTC, but if there is consensus that any >> regressions >> discovered by participants have been fixed, it will end early. >> >> Once that happens, the advisory freeze of FreeBSD/main branch is thawed. >> >> -- >> Gleb Smirnoff >> >> [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:"courier new",monospace">Hello everyone,<br><br>There is a critical regression related to the zfsbootcfg/bectl utility.<br><br>The issue was encountered when attempting to upgrade one of our clusters that was already running a Nov 2025 stabweek. The bug prevents successful activation of a new boot environment via bectl activate -t xxx.<br><br>Given that this regression actively prevents system upgrades and new deployments, it appears to be a serious blocker.<br><br>The issue match this Bugzilla:<br><a href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291211">https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291211</a><br><br>Regards,</div><div class="gmail_default" style="font-family:"courier new",monospace">Olivier</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Nov 26, 2025 at 12:31 AM Olivier Cochard-Labbé <<a href="mailto:olivier@freebsd.org">olivier@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-family:"courier new",monospace">Hello everyone,<br><br>This is an update on the current November 2025 stabilization week on our Netflix A/B test deployment.<br>We had one significant finding:<br>dhw@ noticed a regression (higher system CPU utilization), which was quickly troubleshooted by gallatin@, patched by chs@, and pushed by imp@. This was excellent teamwork!<br>The fix is in the following commit:<br>"git: 2b4dbad2db57 - main - nda: fix setting of unmappedio flag"<br><br>On my end, my personal build machine, Workstation, NAS, and laptop have all been upgraded, and I have not observed any further regressions.<br><br>Separately, reading the -current mailing list, thj@ reported an issue with the 20251124 16-CURRENT snapshot, which appears to be very close to the stabweek state. You can view the report here: <a href="https://lists.freebsd.org/archives/freebsd-current/2025-November/009491.html" target="_blank">https://lists.freebsd.org/archives/freebsd-current/2025-November/009491.html</a><br><br>I will keep the stabilization window open for one more day to allow for any final reports before officially closing the stabweek.<br><br>Regards,<br><br>Olivier</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 24, 2025 at 10:00 AM Gleb Smirnoff <<a href="mailto:glebius@freebsd.org" target="_blank">glebius@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Hi FreeBSD/main users & developers:<br> <br> This is an automated email to inform you that the November 2025 stabilization week<br> started with FreeBSD/main at main-n282109-a067eb525e10, which was tagged as<br> main-stabweek-2025-Nov.<br> <br> Those who want to participate in the stabilization week are encouraged to<br> update to the above revision/tag and test their systems.<br> <br> The tag main-stabweek-2025-Nov has been published at Gleb Smirnoff's github repo.<br> To connect this repo as an additional remote you need to run:<br> <br> git remote add glebius <a href="https://github.com/glebius/FreeBSD" rel="noreferrer" target="_blank">https://github.com/glebius/FreeBSD</a><br>; <br> Once remote is configured, to checkout the tag run:<br> <br> git fetch glebius --tags<br> git checkout main-stabweek-2025-Nov<br> <br> If you want to use only the official FreeBSD repo, then update to<br> the revision:<br> <br> git pull<br> git checkout a067eb525e10<br> <br> Developers are encouraged to avoid pushing new features to FreeBSD/main during<br> the stabilization week, but focus on bugfixes instead. The stabilization week<br> runs up to Friday 18:00 UTC, but if there is consensus that any regressions<br> discovered by participants have been fixed, it will end early.<br> <br> Once that happens, the advisory freeze of FreeBSD/main branch is thawed.<br> <br> --<br> Gleb Smirnoff<br> <br> </blockquote></div></div> </div> </div> </div> </div> </div> </blockquote></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bq%2BTcq61_-_pVtuBwFiAUb5sYOZyd9CD62g27hmMYftOY1AMw>