pkg/58992: pbulk machine-readable report should say which stage failed

[campbell+netbsd%mumble.net@localhost]

>Number:         58992
>Category:       pkg
>Synopsis:       pbulk machine-readable report should say which stage failed
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 14 09:20:00 +0000 2025
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
The NetPbulk Failedalog
>Environment:
>Description:
As far as I can tell, the pbulk machine-readable report doesn't say which stage of the package build failed for failed packages -- it just reports the overall build status (done, failed, prefailed, indirect-failed, &c.).  The HTML report combines the machine-readable report with file-existence tests to produce links to the log stages that exist, but remote consumers of the machine-readable report like bulktracker don't have access to this without scraping the HTML or querying URLs.

It would be nice if the machine-readable report included this information.
>How-To-Repeat:
Follow links from a bulktracker package build results page like https://releng.netbsd.org/bulktracker/pkg/46786788 and find some of them are 404 because bulktracker doesn't know in advance which logs exist.
>Fix:
Either put it in the pbuild report and transform that in create-report.awk, or put the file-existence tests in create-report.awk, to create a new property like BUILD_FAILED_STAGE=... or BUILD_STAGE_LOGS=... or something.  (And then use that in create-report-html.awk instead of doing file-existence tests there.)