This test is cursed.

Yesterday I thought I committed the increased timeout and when the
test was still failing for the autotests n hours later I noticed
I had actually failed to commit it.  I did manage to commit something
in the evening, but the autotests were still failing this morning,
so I noticed I increased the timeout of the wrong test.  I wonder
what will go wrong this time...

(and p.s.: 10240 is probably slow because it's O(n^2) with a constant
of quite a few)
This commit is contained in:
pooka 2010-11-09 11:48:35 +00:00
parent b55225d99f
commit 92603a1ff0

View File

@ -1,4 +1,4 @@
/* $NetBSD: t_environment.c,v 1.6 2010/11/08 23:28:41 pooka Exp $ */
/* $NetBSD: t_environment.c,v 1.7 2010/11/09 11:48:35 pooka Exp $ */
/*-
* Copyright (c) 2010 The NetBSD Foundation, Inc.
* All rights reserved.
@ -32,7 +32,7 @@
*/
#include <sys/cdefs.h>
__RCSID("$NetBSD: t_environment.c,v 1.6 2010/11/08 23:28:41 pooka Exp $");
__RCSID("$NetBSD: t_environment.c,v 1.7 2010/11/09 11:48:35 pooka Exp $");
#include <atf-c.h>
#include <errno.h>
@ -48,13 +48,13 @@ ATF_TC_HEAD(t_setenv, tc)
{
atf_tc_set_md_var(tc, "descr",
"Test setenv(3), getenv(3), unsetenv(3)");
atf_tc_set_md_var(tc, "timeout", "300");
}
ATF_TC_HEAD(t_putenv, tc)
{
atf_tc_set_md_var(tc, "descr",
"Test putenv(3), getenv(3), unsetenv(3)");
atf_tc_set_md_var(tc, "timeout", "300");
}
ATF_TC_HEAD(t_clearenv, tc)