NetBSD Problem Report #56526

From  Sun Nov 28 13:12:05 2021
Return-Path: <>
Received: from ( [])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "", Issuer " CA" (not verified))
	by (Postfix) with ESMTPS id 3C8AF1A9239
	for <>; Sun, 28 Nov 2021 13:12:05 +0000 (UTC)
Message-Id: <>
Date: Sun, 28 Nov 2021 15:11:54 +0200 (EET)
From: (Andreas Gustafsson)
Reply-To: (Andreas Gustafsson)
Subject: Confusing ATF output when system clock is wrong
X-Send-Pr-Version: 3.95

>Number:         56526
>Category:       misc
>Synopsis:       Confusing ATF output when system clock is wrong
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 28 13:15:00 +0000 2021
>Originator:     Andreas Gustafsson
>Release:        NetBSD 9.2
System: NetBSD
Architecture: i386
Machine: i386

If you run the ATF tests with the system clock set to a time in the
past, before the modification time of /bin/sh, it results in the
usr.bin/make/t_make:meta_cmd_cmp test case failing, but no other
test failures or messages.

It would be helpful if a more specific diagnostic could be issued to
point the user at the actual problem, for example by adding a test
that specifically checks if /bin/sh or other system files are from
the future.


date 200001010000
cd /usr/tests
time atf-run | atf-report


NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.46 2020/01/03 16:35:01 leot Exp $
$NetBSD:,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2020 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.