Date: Mon, 22 Aug 2016 23:03:31 -0500 From: Karl Denninger <karl@denninger.net> To: freebsd-stable@freebsd.org Subject: Re: Delay with 11.0-RC2 builds Message-ID: <fc933f40-b289-5081-87df-58b1a2386044@denninger.net> In-Reply-To: <20160823040127.GG765@FreeBSD.org> References: <20160818233024.GZ765@FreeBSD.org> <20160823034319.GG54084@FreeBSD.org> <50aeed81-fdb2-83a4-10c8-d4e50b0d5684@denninger.net> <20160823040127.GG765@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 8/22/2016 23:01, Glen Barber wrote: > On Mon, Aug 22, 2016 at 10:53:06PM -0500, Karl Denninger wrote: >> On 8/22/2016 22:43, Glen Barber wrote: >>> On Thu, Aug 18, 2016 at 11:30:24PM +0000, Glen Barber wrote: >>>> Two issues have been brought to our attention, and as a result, 11.0-RC2 >>>> builds will be delayed a day or two while these are investigated. >>>> >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872 >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211926 >>>> >>>> An update will be sent if the delay is longer than anticipated. >>>> >>> Just an update, the 11.0-RC2 will be delayed at least two days. One of >>> the issues mentioned in the above PR URLs does not affect releng/11.0, >>> and is a non-issue, but we are awaiting one more change to the stable/11 >>> and releng/11.0 branches that we hope will be the final major changes to >>> 11.0. >>> >>> If this is the case, we may be able to eliminate 11.0-RC3 entirely, and >>> still release on time (or, on time as the current schedule suggests). >>> >>> However, as you know, FreeBSD releases prioritize quality over schedule, >>> so we may still need to adjust the schedule appropriately. >>> >>> So, help with testing 11.0-RC1 (or the latest releng/11.0 from svn) is >>> greatly appreciated. >>> >>> Glen >>> On behalf of: re@ >>> >> Has any decision been made on this? >> >> It is not local to me (others have reported problems with combination >> devices) and rolling back the change in question eliminates the >> problem. It remains un-triaged as of this point. >> >> Note that this impacts a system that is booting and needs manual >> intervention, which is not a good place to a have a problem.... >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211884 >> > Well, it's an EN candidate if we cannot get it fixed before the release. > But, I've put it on our radar, which it was not on mine previously... > > Glen Thank you. As far as I can tell reverting that one commit (which results in just one file being rolled back with a handful of lines) fixes it. The other PR (which is linked in this one) reporter also reported that reverting that same commit fixes the problem for him as well. -- Karl Denninger karl@denninger.net <mailto:karl@denninger.net> /The Market Ticker/ /[S/MIME encrypted email preferred]/ [-- Attachment #2 --] 0 *H 010 `He 0 *H _0[0C)0 *H 010 UUS10UFlorida10U Niceville10U Cuda Systems LLC10UCuda Systems LLC CA1"0 *H Cuda Systems LLC CA0 150421022159Z 200419022159Z0Z10 UUS10UFlorida10U Cuda Systems LLC10UKarl Denninger (OCSP)0"0 *H 0 X@vkY Tq/vE]5#֯MX\8LJ/V?5Da+ sJc*/r{ȼnS+ w")ąZ^DtdCOZ ~7Q '@a#ijc۴oZdB&!Ӝ-< ?HN5y 5}F|ef"Vلio74zn">a1qWuɖbFeGE&3(KhixG3!#e_XƬϜ/,$+;4y'Bz<qT9_?rRUpn5 Jn&Rx/p Jyel*pN8/#9u/YPEC)TY>~/˘N[vyiDKˉ,^" ?$T8 v&K%z8C @?K{9f`+@,|Mbia 007++0)0'+0http://cudasystems.net:88880 U0 0 `HB0U0, `HB OpenSSL Generated Certificate0U-h\Ff Y0U#0$q}ݽʒm50U0karl@denninger.net0 *H Owbabɺx&Uk[(Oj!%p MQ0I!#QH}.>~2&D}<wm_>V6v]f>=Nn+8;q wfΰ/RLyUG#b}n!Dր_up|_ǰc/%ۥ nN8:d;-UJd/m1~VނיnN I˾$tF1&}|?q?\đXԑ&\4V<lKۮ3%Am_(q-(cAeGX)f}-˥6cv~Kg8m~v;|9:-iAPқ6ېn-.)<[$KJtt/L4ᖣ^Cmu4vb{+BG$M0c\[MR|0FԸP&78"4p#}DZ9;V9#>Sw"[UP7100010 UUS10UFlorida10U Niceville10U Cuda Systems LLC10UCuda Systems LLC CA1"0 *H Cuda Systems LLC CA)0 `He M0 *H 1 *H 0 *H 1 160823040331Z0O *H 1B@`8a}.a$uWQ*CYy[Heqhũ(yI?:lBΔC0l *H 1_0]0 `He*0 `He0 *H 0*H 0 *H @0+0 *H (0 +710010 UUS10UFlorida10U Niceville10U Cuda Systems LLC10UCuda Systems LLC CA1"0 *H Cuda Systems LLC CA)0*H 1010 UUS10UFlorida10U Niceville10U Cuda Systems LLC10UCuda Systems LLC CA1"0 *H Cuda Systems LLC CA)0 *H (_CbK{ܳsU/拠g# F?T3HcESGUBUSwjL*L!\%lGWX@eih@y8(~psю.˥QqXL3'c%RxNme$pKǪ^BT@&bV" bb@s225/$'<?]%fwdEʽ2tɊNƓy0Ine&
