Hi! Please note that the current release is 3.6.4.
> Le 23 juin 2020 à 14:42, Ron Jr Esquivel <ron1...@hotmail.com> a écrit : > > Hello, > > Here is the testsuite.log from when I tried to make Bison. > There were a lot of errors and skipped tests. Is this normal? No :) > Is Bison still safe to use with these failures? AFAICT, all your failures look like: Next token is token '-' (1.1: ) Shifting token '-' (1.1: ) Entering state 16 Stack now 0 6/cygdrive/u/downloads/bison/bison-3.6.1/tests/testsuite.dir/at-groups/415/test-source: line 2180: 15289 Alarm clock $PREPARSER ./calc input ./calc.at:1077: exit code was 142, expected 0 415. calc.at:1077: 415. Calculator parse.trace (calc.at:1077): FAILED (calc.at:1077) i.e., the machine seems super slow when it comes to large output, and our timeout mechanism is fired. I see nothing weird about Bison itself here, it appears safe to me. But something is fishy about that machine. You also have a very large number of skipped tests, including 416: calc.at:1079 Calculator %defines Please run this: make check-local TESTSUITEFLAGS='416 -d' and send us tests/testsuite.dir/416/testsuite.log. Thanks!
