Date: Mon, 27 Apr 2026 10:51:48 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 294259] devel/capnproto: Update to 1.4.0 Message-ID: <bug-294259-7788-KRyc901Gvm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-294259-7788@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294259 --- Comment #11 from Vasil Dimov <vd@FreeBSD.org> --- Committed the update, thanks! The port is still marked as BROKEN on FreeBSD 15 and 16. Given the comments above: > There are only 2 tests that fail with that error out of hundreds. > It does not justify marking the whole port as BROKEN ... I think > we should just commit this update and add TESTING_UNSAFE with > the upstream issue URL. > Instead of blindly committing with the "its probably fine" > I'd rather see these at least being looked into. I think that should be reconsidered, best if we have more information on how severe the test failures are. I am looking at the tests in work/capnproto-c++-1.4.0/src/kj/async-unix-test.c++ but it is all new to me, can't make a good judgement. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-294259-7788-KRyc901Gvm>