[darcs-devel] buildbot failure in darcs on ertai Linux-2.6.18 i686

[Matthias Kilian]

On Wed, Oct 15, 2008 at 07:25:20AM -0700, buildbot-darcs at allmydata.org wrote:
> The Buildbot has detected a new failure of ertai Linux-2.6.18 i686 on darcs.
> Full details are available at:
>  http://allmydata.org:13010/builders/ertai%20Linux-2.6.18%20i686/builds/50

WTF...

| test_line () {
|     rm -f a
|     echo $1 > a
|     darcs whatsnew | fgrep $2
| }
| 
| 
| # First check escaping and coloring.  Use whatsnew, since that is the
| # most common use of escapes.
| 
| # test the defaults
| # - no color to pipe
| # - don't escape 7-bit ASCII printables, \n,\t and space (we can't test \n)
| # - escape control chars with ^
| # - escape other chars with \xXX
| test_line " !#%&',-0123456789:;<=>"\
|           " !#%&',-0123456789:;<=>"
| fgrep: unrecognized option '--extended-regexp'
| Usage: fgrep [OPTION]... PATTERN [FILE]...
| Try `fgrep --help' for more information.

And the reason is in the environment:

	GREP_OPTIONS=--color=auto --extended-regexp

Yet another people of super-stupid breakage from the GNU people,
and even setting POSIXLY_CORRECT doesn't seem to fix it.

Is it possible to let the buildbot start with a *clean* environment.
Or could somebody name the minimum set environment variables needed
for the tests? Then we could scrub the environment with env(1).

Ciao,
	Kili