[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] tests: avoid spurious failure for each gnu-fortran-using test
From: |
Jim Meyering |
Subject: |
[PATCH] tests: avoid spurious failure for each gnu-fortran-using test |
Date: |
Tue, 17 Jan 2012 12:24:24 +0100 |
Surprised to see all fortran-running tests fail, I investigated...
>From 905b85a2060f600dbc21e262262f77c8074f7db1 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Tue, 17 Jan 2012 12:22:59 +0100
Subject: [PATCH] tests: avoid spurious failure for each gnu-fortran-using
test
The tests compare pre- and post-run lists of envvars, which must
be the same, modulo a list of known, filtered-out exceptions.
However, when running fortran-checking tests with GNU fortran, each
would fail due to the post-run addition of the GFC symbol added in
v2.68-97-gbd962ac.
* tests/local.at (AT_CHECK_ENV): Add GFC to the list of symbols
that we ignore in pre-/post-run environment diffs.
---
tests/local.at | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tests/local.at b/tests/local.at
index 8b73c94..cce24f0 100644
--- a/tests/local.at
+++ b/tests/local.at
@@ -316,7 +316,7 @@ if test -f state-env.before && test -f state-env.after; then
[(host|build|target)(_(alias|cpu|vendor|os))?],
[cross_compiling|U],
[interpval|PATH_SEPARATOR],
- [F77_DUMMY_MAIN|f77_(case|underscore)],
+ [GFC|F77_DUMMY_MAIN|f77_(case|underscore)],
[FC(_DUMMY_MAIN|FLAGS|LIBS|FLAGS_[fF]|_MODEXT|_MODINC|_MODOUT|_DEFINE)?],
[ALLOCA|GETLOADAVG_LIBS|KMEM_GROUP|NEED_SETGID|POW_LIB],
[AWK|LEX|LEXLIB|LEX_OUTPUT_ROOT|LN_S|M4|MKDIR_P|RANLIB|SET_MAKE|YACC],
--
1.7.9.rc1.2.gccfe4
- [PATCH] tests: avoid spurious failure for each gnu-fortran-using test,
Jim Meyering <=