Re: Problem with the package builds

On Wed, Jul 12, 2023 at 1:09 AM Charlie Li wrote: > Kevin Oberman wrote: > > As I expected, each package install takes a very long time. It appears > > that the average time to install a package with 1.20.2 was running about > > 45-50 seconds. Hopefully this latest update will fix that. > It does

Re: Problem with the package builds

Kevin Oberman wrote: As I expected, each package install takes a very long time. It appears that the average time to install a package with 1.20.2 was running about 45-50 seconds. Hopefully this latest update will fix that. It doesn't. Some digging revealed that the new validating provides/requ

Re: Problem with the package builds

Guido Falsi wrote on 2023/07/11 16:27: > Anyway you can monitor "vfs.freevnodes" and "vfs.numvnodes" to discover if > that's an issue for you. If numvnodes is very near or above maxvnodes nad at > the same time freevnodes is very low you have a problem. Another indicator > could be vfs.vnodes_cr

Re: Problem with the package builds

On Tue, Jul 11, 2023 at 9:15 PM Mark Millard wrote: > On Jul 11, 2023, at 21:05, Kevin Oberman wrote: > > > On Tue, Jul 11, 2023 at 1:10 PM Mark Millard wrote: > > On Jul 11, 2023, at 12:57, Kevin Oberman wrote: > > > > > On Mon, Jul 10, 2023 at 9:42 PM Mark Millard > wrote: > > > On Jul 10,

Re: Problem with the package builds

On Jul 11, 2023, at 21:05, Kevin Oberman wrote: > On Tue, Jul 11, 2023 at 1:10 PM Mark Millard wrote: > On Jul 11, 2023, at 12:57, Kevin Oberman wrote: > > > On Mon, Jul 10, 2023 at 9:42 PM Mark Millard wrote: > > On Jul 10, 2023, at 21:27, Rainer Hurling wrote: > > > > > As I understand it

Re: Problem with the package builds

On Tue, Jul 11, 2023 at 1:10 PM Mark Millard wrote: > On Jul 11, 2023, at 12:57, Kevin Oberman wrote: > > > On Mon, Jul 10, 2023 at 9:42 PM Mark Millard wrote: > > On Jul 10, 2023, at 21:27, Rainer Hurling wrote: > > > > > As I understand it, the ports-mgmt/pkg of the system running Poudriere

Re: Problem with the package builds

On Jul 11, 2023, at 12:57, Kevin Oberman wrote: > On Mon, Jul 10, 2023 at 9:42 PM Mark Millard wrote: > On Jul 10, 2023, at 21:27, Rainer Hurling wrote: > > > As I understand it, the ports-mgmt/pkg of the system running Poudriere must > > be updated beforehand? > > > > At least on my side, t

Re: Problem with the package builds

On Mon, Jul 10, 2023 at 9:42 PM Mark Millard wrote: > On Jul 10, 2023, at 21:27, Rainer Hurling wrote: > > > As I understand it, the ports-mgmt/pkg of the system running Poudriere > must be updated beforehand? > > > > At least on my side, this seems to work as expected :) > > > > poudriere build

Re: Problem with the package builds

On Jul 10, 2023, at 21:27, Rainer Hurling wrote: > Am 10.07.23 um 23:26 schrieb Kevin Oberman: >> On Mon, Jul 10, 2023 at 10:31 AM Rainer Hurling > > wrote: >>Am 10.07.23 um 08:15 schrieb Rainer Hurling: >> > Am 10.07.23 um 08:08 schrieb Mark Millard: >> >> On

Re: Problem with the package builds

Am 10.07.23 um 23:26 schrieb Kevin Oberman: On Mon, Jul 10, 2023 at 10:31 AM Rainer Hurling > wrote: Am 10.07.23 um 08:15 schrieb Rainer Hurling: > Am 10.07.23 um 08:08 schrieb Mark Millard: >> On Jul 9, 2023, at 22:52, Rainer Hurling mailto:rhur...@gwdg.de>

Re: Problem with the package builds

Jan Beich wrote on 2023/07/11 12:51: > Even with pkg-1.20.2 many running jobs are stuck with *-depends in Status. > > https://pkg-status.freebsd.org/beefy18/build.html?mastername=main-amd64-default&build=pd6fe15e0ee7a_s1ec7cb1b5d At the time I started writing this email, several qt5-* and kf5-*s

Re: Problem with the package builds

Kevin Oberman writes: > On Mon, Jul 10, 2023 at 10:31 AM Rainer Hurling wrote: > >> Am 10.07.23 um 08:15 schrieb Rainer Hurling: >> > Am 10.07.23 um 08:08 schrieb Mark Millard: >> >> On Jul 9, 2023, at 22:52, Rainer Hurling wrote: >> >> >> >>> Am 10.07.23 um 06:53 schrieb Mark Millard: >>

Re: Problem with the package builds

Hello. Guido Falsi wrote on 2023/07/10 18:01: > This resonates with something I have observed from time to time on my build > machine. > Especially when using a big ccache (32 GiB or more, is what I can testify > about), but also when building ports with a big number of files like the > teTeX,

Re: Problem with the package builds

On Mon, Jul 10, 2023 at 10:31 AM Rainer Hurling wrote: > Am 10.07.23 um 08:15 schrieb Rainer Hurling: > > Am 10.07.23 um 08:08 schrieb Mark Millard: > >> On Jul 9, 2023, at 22:52, Rainer Hurling wrote: > >> > >>> Am 10.07.23 um 06:53 schrieb Mark Millard: > Konstantin Belousov wrote on > >

Re: Problem with the package builds

Am 10.07.23 um 08:15 schrieb Rainer Hurling: Am 10.07.23 um 08:08 schrieb Mark Millard: On Jul 9, 2023, at 22:52, Rainer Hurling wrote: Am 10.07.23 um 06:53 schrieb Mark Millard: Konstantin Belousov wrote on Date: Mon, 10 Jul 2023 01:18:05 UTC : On Sun, Jul 09, 2023 at 05:52:50PM -0700, Ke

Re: Problem with the package builds

On 7/10/23 02:28, Gleb Popov wrote: On Mon, Jul 10, 2023 at 3:53 AM Kevin Oberman wrote: Something looks really messed up on the beefy16 package builder for 13.1amd64. The main culprit is pkg 1.20: https://github.com/freebsd/pkg/issues/2155 https://github.com/freebsd/pkg/issues/2156 Dang,

Re: Problem with the package builds

Tatsuki Makino wrote: No, actually I suspect there is something wrong with the base as well. :) There must be something wrong with the area around the disk IO. It often goes to access as if the cache is not working and the HDD random access is unusually slow. I'm hesitant to move to version 13 s

Re: Problem with the package builds

On Mon, Jul 10, 2023 at 3:53 AM Kevin Oberman wrote: > > Something looks really messed up on the beefy16 package builder for 13.1amd64. The main culprit is pkg 1.20: https://github.com/freebsd/pkg/issues/2155 https://github.com/freebsd/pkg/issues/2156

Re: Problem with the package builds

Am 10.07.23 um 08:08 schrieb Mark Millard: On Jul 9, 2023, at 22:52, Rainer Hurling wrote: Am 10.07.23 um 06:53 schrieb Mark Millard: Konstantin Belousov wrote on Date: Mon, 10 Jul 2023 01:18:05 UTC : On Sun, Jul 09, 2023 at 05:52:50PM -0700, Kevin Oberman wrote: Something looks really mes

Re: Problem with the package builds

On Jul 9, 2023, at 22:52, Rainer Hurling wrote: > Am 10.07.23 um 06:53 schrieb Mark Millard: >> Konstantin Belousov wrote on >> Date: Mon, 10 Jul 2023 01:18:05 UTC : >>> On Sun, Jul 09, 2023 at 05:52:50PM -0700, Kevin Oberman wrote: Something looks really messed up on the beefy16 package bu

Re: Problem with the package builds

Am 10.07.23 um 06:53 schrieb Mark Millard: Konstantin Belousov wrote on Date: Mon, 10 Jul 2023 01:18:05 UTC : On Sun, Jul 09, 2023 at 05:52:50PM -0700, Kevin Oberman wrote: Something looks really messed up on the beefy16 package builder for 13.1amd64. It is building about 9500 packages and s

Re: Problem with the package builds

Kevin Oberman wrote on 2023/07/10 14:01: > I have been monitoring the builds of amd64 builds for at least two years > and this is way outside of the norm. It continues to build packages at a > rate of 10 per hour which would still mean that the build will not complete > until late August. I guess

Re: Problem with the package builds

On Sun, Jul 9, 2023 at 7:14 PM Tatsuki Makino wrote: > Hello. > > Kevin Oberman wrote on 2023/07/10 09:52: > > only completed 459 packages, a rate of 10 packages/hour and, if it > > continues at this rate, will not complete for about 40 days. Nt sure if > > The numbers in that area are meaningles

Re: Problem with the package builds

Konstantin Belousov wrote on Date: Mon, 10 Jul 2023 01:18:05 UTC : > On Sun, Jul 09, 2023 at 05:52:50PM -0700, Kevin Oberman wrote: > > Something looks really messed up on the beefy16 package builder for > > 13.1amd64. > > > > It is building about 9500 packages and started almost two days ago. I

Re: Problem with the package builds

Hello. Kevin Oberman wrote on 2023/07/10 09:52: > only completed 459 packages, a rate of 10 packages/hour and, if it > continues at this rate, will not complete for about 40 days. Nt sure if The numbers in that area are meaningless :) For example, the following two poudriere bulk -j ... -C devel

Re: Problem with the package builds

On Sun, Jul 09, 2023 at 05:52:50PM -0700, Kevin Oberman wrote: > Something looks really messed up on the beefy16 package builder for > 13.1amd64. > > It is building about 9500 packages and started almost two days ago. It has > only completed 459 packages, a rate of 10 packages/hour and, if it > co

Problem with the package builds

Something looks really messed up on the beefy16 package builder for 13.1amd64. It is building about 9500 packages and started almost two days ago. It has only completed 459 packages, a rate of 10 packages/hour and, if it continues at this rate, will not complete for about 40 days. Nt sure if this