From nobody Mon Dec 12 06:50:51 2022 X-Original-To: freebsd-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 4NVsjB5dGxz4k536 for ; Mon, 12 Dec 2022 06:51:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb34.google.com (mail-yb1-xb34.google.com [IPv6:2607:f8b0:4864:20::b34]) (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 4NVsjB3jRsz3MDH for ; Mon, 12 Dec 2022 06:51:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb34.google.com with SMTP id i186so12467787ybc.9 for ; Sun, 11 Dec 2022 22:51:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=EbTaX27sgLGh6x90qXlSZwW2OLW8jTiufjd515EiGRQ=; b=BBW8O0oh6LebLuaXjOliYrYk3+t76DJsNI147DjobFaNvFFJZ8FvF/coRauWYNXK9E aad6TpPAcl+sgd51BXObpflYS2ifzyGsm3q1IPxGEbL8CvnnUCiSdsOt3Wsf5LdaetyL hFqCLdkphviCYG7CWmLQ+vJ4znDveS0GfgkbQddveukKZLgKqCB6JJypdNRABRmK92J3 /a5DvNNuIE1IAypg2zoEYQuDMUXeQugojFNm5aKmwDO8/dPIrNf/rSgpCO6sF/Ze3m0O DglhuHVBe4pfplwB0Lft7liYzVYK4XgDyBHbmgbHsAcqPG4rFT4pgJ4DAYt6AvUJbUj/ gsQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=EbTaX27sgLGh6x90qXlSZwW2OLW8jTiufjd515EiGRQ=; b=imyTS2aJaWGgjZW1xkvPkYoTcn7LJ8IsLrO7JuQ9E6uice+RHwA53RAAqTh7lTQZ2a 52HzdA1UIUj/qWTL0l6jp/kW8Qf+9Rmemn8Ss3CFcjlCgr7Y8umaJf8zVLcvu2sLxE7t FFm8L4+0u6O3XeXWNq+y6C4hKwi9hdomcnPWa3YrnfoixmukaNPjuRcyJ5lrmsld2hRF iwK6YrSwH9ThXu79kP4EExpo1BEUO6wOgBRhTfKzKWcFtZ2HPW+F8DqSpm8cvjF+DlVS eBdSPi8fijZ9NV8nZmddlL/kSRAH5wS1mAVa/DMY8iAZgDTK2Dnoqonwt70o7vvC3Gf+ 15oA== X-Gm-Message-State: ANoB5plaMV19CuW+FL8vhJnyO13vfInUUuQWVIe/kQD6Ohsf4SJI+iaW jtd8FGX644WGLlnFMYP26q3cOcMM5uevTI2YH3frr4JW X-Google-Smtp-Source: AA0mqf6BpmzWOeQdAOsYjK2pPRe3LDemadZmCZOhrtdycEeveCl+3i4aC7FaIvUhnC6FuejLr4N9/ekmdRIKP0ChCLk= X-Received: by 2002:a25:606:0:b0:725:3de:e98f with SMTP id 6-20020a250606000000b0072503dee98fmr460200ybg.573.1670827867661; Sun, 11 Dec 2022 22:51:07 -0800 (PST) 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: <2D9B9846-413A-4BFA-A80C-107ED1E3C83D.ref@yahoo.com> <2D9B9846-413A-4BFA-A80C-107ED1E3C83D@yahoo.com> <41bf3921-67e4-ee44-eff5-d4a73563ca5a@gmx.net> In-Reply-To: <41bf3921-67e4-ee44-eff5-d4a73563ca5a@gmx.net> From: Kevin Oberman Date: Sun, 11 Dec 2022 22:50:51 -0800 Message-ID: Subject: Re: Differing status reports fro the package build cluster To: Simon Wright Cc: FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000886c8205ef9bedc7" X-Rspamd-Queue-Id: 4NVsjB3jRsz3MDH 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 --000000000000886c8205ef9bedc7 Content-Type: text/plain; charset="UTF-8" On Sun, Dec 11, 2022 at 7:35 PM Simon Wright wrote: > On 2022-12-12 10:36, Mark Millard wrote: > > Simon Wright wrote on > > Date: Mon, 12 Dec 2022 00:13:20 UTC : > > > >> If I look at the report on: > >> > >> > https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package&all=1 > >> > >> the status on 131amd64 default (on beefy16) is: parallel_build, started > >> 10 December. > > > > When I just looked at 86b787b900a8 (a default Ports), it still listed > 1126 > > Remaining: so not done. > > > > The prior completed one (0 Remaining) is listed as 908640ce3450 . > > > > > >> If I look at the same url but with the "latest only" filter, the same > >> jail has a status of stopped:done with a started date of 6 December. > > > > https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package > shows: > > > > 908640ce3450 as well, the same completed one as on the other page. > > > >> I'm assuming that the "all" view is current but does anyone know why > >> they show differently? > > > > They agree about what has completed, at least for now. > > OK, I get it; the report filtered on "View latest only" is only updated > when the build for that git hash is complete however the current status > of the build boxes - including builds in progress - is shown on the > "View All" filter. > > Thanks for the insight Mark. > This is close, but you need to realize that the packages will only be available when they have been copied to all global distribution sites, so the fact that the run has been completed does not mean that the packages built on htat run are available. The time to distribute varies with the size of the run and network performance. It has greatly improved during hte past year as mirrors in some places are getting higher speed connections. I should also note that pkg-status data only updates the display on a reload. Updates from the IPv6-onlybuild systems do update every 10 seconds. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000886c8205ef9bedc7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Dec 11, 2022 at 7:35 PM= Simon Wright <simon.wright@gmx.= net> wrote:
On 2022-12-12 10:36, Mark Millard wrote: > Simon Wright <simon.wright_at_gmx.net> wrote on
> Date: Mon, 12 Dec 2022 00:13:20 UTC :
>
>> If I look at the report on:
>>
>> htt= ps://pkg-status.freebsd.org/builds?jailname=3D131amd64&type=3Dpackage&a= mp;all=3D1
>>
>> the status on 131amd64 default (on beefy16) is: parallel_build, st= arted
>> 10 December.
>
> When I just looked at 86b787b900a8 (a default Ports), it still listed = 1126
> Remaining: so not done.
>
> The prior completed one (0 Remaining) is listed as 908640ce3450 .
>
>
>> If I look at the same url but with the "latest only" fil= ter, the same
>> jail has a status of stopped:done with a started date of 6 Decembe= r.
>
> https://pkg-status.= freebsd.org/builds?jailname=3D131amd64&type=3Dpackage shows:
>
> 908640ce3450 as well, the same completed one as on the other page.
>
>> I'm assuming that the "all" view is current but does= anyone know why
>> they show differently?
>
> They agree about what has completed, at least for now.

OK, I get it; the report filtered on "View latest only" is only u= pdated
when the build for that git hash is complete however the current status
of the build boxes - including builds in progress - is shown on the
"View All" filter.

Thanks for the insight Mark.

This = is close, but you need to realize that the packages will only be available = when they have been copied to all global distribution sites, so the fact th= at the run has been completed does not mean that the packages built on htat= run are available. The time to distribute varies with the size of the run = and network performance. It has greatly improved during hte past year as mi= rrors in some places are getting higher speed connections.
=
I should also note that pkg-status data only updates=C2= =A0 the display on a reload. Updates from the IPv6-onlybuild systems do upd= ate every 10 seconds.
--
Kevin Oberman, Part time kid herder and retired Network= Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78= C1694B318AB39EF1B055683
--000000000000886c8205ef9bedc7--