NetBSD Problem Report #59292

From www@netbsd.org  Sun Apr 13 18:51:20 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) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id CCA511A9239
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 13 Apr 2025 18:51:19 +0000 (UTC)
Message-Id: <20250413185118.595321A923D@mollari.NetBSD.org>
Date: Sun, 13 Apr 2025 18:51:18 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: releng testbed: missing atf xml/html results
X-Send-Pr-Version: www-1.0

>Number:         59292
>Category:       port-arm
>Synopsis:       releng testbed: missing atf xml/html results
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-arm-maintainer
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 13 18:55:00 +0000 2025
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
Test ArmBSD Results Extraction
>Environment:
>Description:
As noted at the top of https://releng.netbsd.org/b5reports/evbarm-earmv7hf/:

> ATF HTML reports and XML files are missing due to the lack of support for more than one block device in VEXPRESS_A15, but the console output is available.

But we have now nixed the VEXPRESS_A15 kernel config in favour of (I assume) GENERIC.  Surely, even if the VEXPRESS_A15 kernel config didn't support more than one block device, GENERIC should?  Or is this a limitation in qemu's `-M vexpress-a15' machine, despite the apparently-unused virtio0-3 devices I see in the dmesg output?  If it's really a limitation on block devices, could we use vio9p to export the results instead?
>How-To-Repeat:
anita test arm32, probably
>Fix:
Yes, please!

Home	PR Database Search