NetBSD Problem Report #58992

From www@netbsd.org  Tue Jan 14 09:15:29 2025
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits)
	 client-signature RSA-PSS (2048 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id DF9FE1A923B
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 14 Jan 2025 09:15:28 +0000 (UTC)
Message-Id: <20250114091527.BB4B01A923C@mollari.NetBSD.org>
Date: Tue, 14 Jan 2025 09:15:27 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: pbulk machine-readable report should say which stage failed
X-Send-Pr-Version: www-1.0

>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.)

Home	PR Database Search