Re: [GNU Bison 2.0] testsuite: 91 92 93 failed on GNU/Linux on Alpha

[Paul Eggert]

Re this bug report:

  http://lists.gnu.org/archive/html/bug-bison/2005-01/msg00023.html

which has failures like this:

  Shifting token "n./testsuite: line 62247: 29063 Alarm clock

All that I can think of offhand is that it's an old slow machine.
Does it fix things if you change the "alarm (10);" in tests/calc.at to
"alarm (100);", so that the test program gets 100 seconds instead of 10?

If not, can you change the alarm(100) to alarm(10000), and then use
GDB to attach to the program that's looping, and find out where it's
looping?  You might want to build with CFLAGS=-g first.