From nobody Mon Jul 10 05:01:38 2023 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QzsLC26vCzZVVY for ; Mon, 10 Jul 2023 05:01:55 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QzsLC0T70z3P5J for ; Mon, 10 Jul 2023 05:01:55 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-c5f98fc4237so3838686276.2 for ; Sun, 09 Jul 2023 22:01:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688965314; x=1691557314; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/Dbq85BMZhJncxnmrFJJrG2WObiZ7kNWbRXoCUTy7C0=; b=nApZbCtj/gdEc+q77MpkoqeIcsDb+ewrrn6TuRUWjiTHYKKLSkZNwWIKmEoZEN14DE +XgryjrgBHQoSuiwIY6jRhAmHRZlm2IrSqnSCpM6kqGDaL14EPAIwUxJPzBblR4fBz7e /SgxbHwolguDHSE+xT/WN+1mSQeJyYbxk+hw+B+9K0+KpbP0ozbGlgz5VwsKyeDSzs6r S4xzk1i89RCKDpOCZ3+Gv/KlsO4Vhn/bnuDGTK+/TcN8Tu+fRjb9bl0p7TcRRKhPFC/S CPIyovxCMcYgb4fbbpwAbHHewB9k79qxCC7qZ4BApvoZiqtL8cOuoYYNaKyvTJlMojiC +K8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688965314; x=1691557314; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=/Dbq85BMZhJncxnmrFJJrG2WObiZ7kNWbRXoCUTy7C0=; b=fTxQc7WCbRID4ymnIs0ZGkveaeQJt9d9ooiDvo0BdgCMlsGvp9onmICR4o3SwTo6RW L9lihLuPUwNag8hwYQOkov1bu9cw6cwUjHKFnrQdpCxXTw8xzFq7/g4tSaIYDw1LX81K ORzoQuulCO+AeiK3f4Pdee+Ew/Whz+aQIAeP4865Yx3EHAotHakz1utIyTrWvrz1iaFy hjMWa6gF3V5vjDxYSQdN18aMsjGpq9DDDfGNmV7feXpKC+KfxLwVrfR0gbyS073vt/gG mFQ5SryXLGngKeJ1mVEs2Wb5ymI+2Gqw6pJTkQZdo6M1ZEyqGuzju4ra61tyiLLpML0w 7y2g== X-Gm-Message-State: ABy/qLbKDZ8cwl3QbZHZLKRQp/SCzByRYN+dxZNV1hsbu4Qf8BJcRVP5 ESZzdH82HebyZCzvIQbKficsU9adTE57kIHZ95wBUPOf X-Google-Smtp-Source: APBJJlF/EKvLcYifgPkdnMvDUaJCsWO4dHB9h1f//H/h8O/1+6SKtuQjZaWGZIkYHhRa1h9unmP8he+U0NOw7xC/Lgs= X-Received: by 2002:a25:a067:0:b0:c00:f1f1:ab0 with SMTP id x94-20020a25a067000000b00c00f1f10ab0mr9832451ybh.20.1688965314005; Sun, 09 Jul 2023 22:01:54 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Kevin Oberman Date: Sun, 9 Jul 2023 22:01:38 -0700 Message-ID: Subject: Re: Problem with the package builds To: Tatsuki Makino Cc: "ports@FreeBSD.org" Content-Type: multipart/alternative; boundary="000000000000944e0306001ae17f" X-Rspamd-Queue-Id: 4QzsLC0T70z3P5J X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000944e0306001ae17f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Jul 9, 2023 at 7:14=E2=80=AFPM 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 meaningless :) > For example, the following two > > poudriere bulk -j ... -C devel/llvm15 lang/gcc12 lang/rust > poudriere bulk -j ... -z somethingrandom -C x11-fonts/xorg-fonts > > The top line is outrageously evil, and the bottom line hits a ridiculous > number. :) > Indeed, those are extreme examples, but this is a build of 9514 packages that include a fairly random mix of all ports. This build should normally take between 50 and 70 hours. A build of all packages ran 90 hours starting back on June 22. A more typical build of 11111 packages took 52 hours. The current build continues at 10 packages an hour after almost 52 hours. Two facts clearly indicate that something is wrong: After 52 hours, when a build of this size of random packages should be close to finished, it has only completed 486, and almost all package build are getting dependencies. After a couple of yours, it is very unusual to see more than 4 jails in *-depends states. Right now, 9 jails are in lib-depends and 4 in build-depends. None are actually building the port. 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 I could go do a statistical analysis, but it is way beyond the need for that. I'm sorry, but this is clearly broken. Can't say whether it is hardware or software, but the numbers have moved far beyond reasonable. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000944e0306001ae17f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Jul 9, 2023 at 7:14=E2= =80=AFPM Tatsuki Makino <t= atsuki_makino@hotmail.com> 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 i= f

The numbers in that area are meaningless :)
For example, the following two

poudriere bulk -j ... -C devel/llvm15 lang/gcc12 lang/rust
poudriere bulk -j ... -z somethingrandom -C x11-fonts/xorg-fonts

The top line is outrageously evil, and the bottom line hits a ridiculous nu= mber. :)

Indeed, those are extreme= examples, but this is a build of 9514 packages that include=C2=A0 a fairly= random mix of all ports. This build should normally take between 50 and 70= hours. A build of all packages ran 90 hours starting back on June 22. A mo= re typical build of 11111 packages took 52 hours. The current build continu= es at 10 packages an hour after almost 52 hours.

Two facts clearly indicate that something is wrong: After 52 = hours, when a build of this size of random packages should be close to fini= shed, it has only completed 486, and almost all package build are getting d= ependencies. After a couple of yours, it is very unusual to see more than 4= jails in *-depends states. Right now, 9 jails are in lib-depends and 4 in = build-depends. None are actually building the port.

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 packag= es at a rate of 10 per hour which would still mean that the build will not = complete until late August. I guess I could go do a statistical analysis, b= ut it is way beyond the need for that.

I'm sorry, but this is clearly broken. Can't say whether it is h= ardware or software, but the numbers have moved far beyond reasonable.
<= /div>
--
Kevin Oberman, Part time kid herder= and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprin= t: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--000000000000944e0306001ae17f--