Re: One failed self test on Alpine Linux
Akim Demaille <[email protected]>
| Newsgroups | gmane.comp.parsers.bison.bugs |
|---|---|
| Message-ID | <[email protected]> |
Jeffrey, > Le 14 janv. 2021 à 20:41, Jeffrey Walton <[email protected]> a écrit : > > On Thu, Jan 14, 2021 at 12:44 AM Akim Demaille <[email protected]> wrote: > > The new run is available at https://www.cryptopp.com/271-2.log.zip. It > also used the directory bison-3.7.4.254-a0905 (and not > bison-3.7.4.254-82133), so don't be surprised. I believe these traces were not issued by the tarball I last gave you. I made a mistake in the generation of the traces, and your logs do not include that error. So please, let's try again. I have again prepared another tarball. https://www.lrde.epita.fr/~akim/private/bison/bison-3.7.4.273-d85e.tar.gz https://www.lrde.epita.fr/~akim/private/bison/bison-3.7.4.273-d85e.tar.lz https://www.lrde.epita.fr/~akim/private/bison/bison-3.7.4.273-d85e.tar.xz make check-local TESTSUITEFLAGS='271 -d' TIME_LIMIT=1 ./src/bison -Tcex -Wcex ./tests/testsuite.dir/271/input.y >/tmp/271.log 2>&1 > I also installed an Alpine Linux 3.12 system. It tests OK. That's good news. I wouldn't be surprised that the problem is actually coming from Alpine 3.10, but... > The issue is probably related to Alpine Linux 3.10. Probably something > to do with BusyBox. I'm not sure I understand what you mean. To me, busybox is sort of a shell with many standard Unix tools baked it, but since bison is independent of such tools, I do see what kind of problem you think about. Cheers!