Apart from the idiot reasons, X11 tests can easily fail on an Apple laptop because the X server becomes unusable every time the IP changes, which is fairly frequently. I don't really use X a lot and thus do not restart the server every time I move the laptop, so these tests fail almost all the time (but I've learned to ignore those errors).
Boyana -- Boyana Norris, Computer Scientist, Argonne National Laboratory norris at mcs.anl.gov, +1.630.252.7908, http://www.mcs.anl.gov/~norris/ On Oct 28, 2009, at 6:49 PM, Barry Smith wrote: > > On Oct 28, 2009, at 6:41 PM, Satish Balay wrote: > >> Barry, >> >> any objections to removing the 'x11' test from 'make test?' >> >> It fails for significant numer of installs [for users without working >> x11 etc..]. And the c/fortran/parallel tests should be the primary >> tests anyway.. > > The make rule for make tests only runs this test when ./configure > has found X11 and tested that it compiles and links properly. > > Thus it is not failing because of a failed X11 install. > > My understanding is that it ONLY fails because people don't have > the proper DISPLAY variable set. That is either > 1) DISPLAY does not exist or has garbage or > 2) DISPLAY points to a proper X server but because of permission > issues or firewalls the X client cannot connect to the X server. > > Does it fail for any other reason? > > I hate to pander to complete idiots who cannot set up their X > system properly; but I guess you can move that test to a new test > called > testx11 > > Barry > >> >> thanks, >> Satish >
