LinuxQuestions.org - Bash test suite is locking up.

- Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)

- - Bash test suite is locking up. (https://www.linuxquestions.org/questions/linux-from-scratch-13/bash-test-suite-is-locking-up-819019/)

Bash test suite is locking up.

In "6.29 Bash-4.1" of the LFS book (6.6) when I get to the bash test suite, it keeps freezing up (I'm very sure) here:

Quote:

run-coproc
warning: the process IDs printed will differ on every run
warning: and generate diffs

It stayed right there for quite a long time. When I hit Ctrl-C, it moved on like it was working and went on to finish the rest of the tests (without any apparent problems). I could print more output, but I'm in the middle of trying it again. Now I'm just letting it sit there and seeing if anything happens. I don't think it's supposed to take a very long time though, so it must be some sort of problem I'm having. This is the second time I'm attempting it (after rm -rf-ing the directory and starting at the top of the page again. Right now it seems to be doing nothing again. If it appears to be working other than getting hung up here (which it does), should I just ignore it and move forward?
I've followed the instructions in the handbook perfectly up to this point as far as I know (and I've paid very close attention and have had no problems so far).
The output I mentioned (to do with this specific part of the test) looked like it looked in successful builds that I found when googling. (Except the ^C immediately after the above point).

I'm using a good HT Pentium 4 processor (3.4 GHz) and have 1 GB of RAM.

Hi,

What do you consider to be "for quite a long time"? The building of bash takes about 1.4 SBU, which isn't the longest but it does take some time. Compare it to gcc (1.1 SBU) and binutils (2.2 SBU).

You do mention that you followed the instructions, but are you sure you didn't forget/mis-typed this part:

Quote:

To prepare the tests, ensure that the locale setting from our environment will be used and that the nobody user can read the standard input device and write to the sources tree:

sed -i 's/LANG/LC_ALL/' tests/intl.tests
sed -i 's@tests@& </dev/tty@' tests/run-test
chown -Rv nobody ./

BTW: Here's a link to the output that should be shown when running the tests: Bash build-logs (LFS 6.6).

Hope this helps.

Yes, I did do that both times - definitely. Look here:

Quote:

run-coproc
warning: the process IDs printed will differ on every run
warning: and generate diffs
^C1c1
< 25401
---
> 84575
4c4
< 25403
---
> 84577
6a7,13
> ./coproc.tests: line 22: 84577 Terminated coproc REFLECT { cat -; }
> 84579
> 63 60
> FOO
> 63 60
> root
> -1 -1
run-cprint

I made the ^C red so it stands out more easily. And I mean I've let it run for a very, very long time and nothing happens. Everything else compiles real quickly and test quickly other than the obvious exceptions like GCC. Notice that:

Quote:

> ./coproc.tests: line 22: 84577 Terminated coproc REFLECT { cat -; }

shows up once and not twice. I just took the (I think) out of the title of this thread, also.
EDIT: I installed it and moved on and so far it seems to be working fine.

I'm on 6.33 Perl-5.10.1 after ignoring that one hangup. Like I said, after Ctrl+C, the rest of the test finished with no problems. So far I haven't had any problems at all.