Suggest removing an ambiguity from the poudriere/data/logs/bulk/.html/build.html presentation

[markmi]

Prerequisites

• [ Yes ] Have you checked for an existing issue describing your idea?

What is your proposal?

[Note: Olivier Certner olce@freebsd.org requested that I submit this based on FreeBSD 15 limiting his time. I was one of the folks in the exchange.]

Change some wording to eliminate confusions of 2 distinct counts in poudriere/data/logs/bulk/.html/build.html pages not matching despite both referencing "Queued" as the context. The presentation has confused some folks.

What is the existing behavior, if any?

Build of 24fedaeb4e97 on beefy21 is an example:

Queued Built Failed Skipped Ignored Fetched Remaining
992    373   152    121     346     0       0
. . .
Queued ports
Showing 1 to 10 of 37,164 entries

Note that 992 != 37164 (and the presentation has lead to confusions because of that).

(For bulk -ca builds or other forms of from-scratch builds, the figures will happen to be equal. But not for incremental builds. In the case above, the prior builds 9a9cbb37913d and d1f407b76f7a lead to a status of most port-packages having the implicit status "already built at start" instead of "not yet built at start".)

What is the motivation / use case for the change?

There are list exchanges tied to confusions about the distinction between 992 and 37,164 (as an example). Folks have inferred that such builds are probably broken by not building everything that it should have, for example. Clearly distinct naming for what can be distinct values would be less ambiguous.

Renaming "Queued Ports" to avoid appearing to also reference "# Queued Ports entries" could avoid this if a suitable alternate name is found.

Olivier C. has suggested: "Build scope"

One could imagine another column for the classification status "already built at start" vs. "not yet built at start". (Better specific naming?) But that would be less important than the replacement of the "Queued Ports" text.

Did you consider any alternatives?

I'll likely be submitting a less simple idea for the extra column that would have more information but involve dynamic updating of values in the column as the bulk build progresses.

Is this really a ports feature request?

The HTML pages are from poudriere(-devel).

Example

Queued Built Failed Skipped Ignored Fetched Remaining
992    373   152    121     346     0       0
. . .
Build Scope
Showing 1 to 10 of 37,164 entries

(I'll not make an example of adding the potential column.)

Additional context

None.