Q

[Ivan Wagner]

Issue #1 = expensive tests are not being run "./tail-2/inotify-race: skipping test: very expensive: disabled by default"

After some trial and error, I was able to run the expensive tests by running "export RUN_EXPENSIVE_TESTS=yes" prior to running the listed command. I unset RUN_EXPENSIVE_TESTS after the tests.

Issue #2 = rm/fail-eperm test is being skipped "fail-eperm: couldn't find a file not owned by you

in any of the following directories:

/tmp /var/tmp /usr/tmp

...so, skipping this test"

I ran "touch /tmp/coreutils-test" prior to running the tests.

Issue #3 = " mv/i-3, /dev/stdin is not readable"

I cheated by making whatever /dev/stdin pointed to readable before the test and switching it back after. But that seems like overkill for one test.

The misc/tty-eof is being skipped because it requires perl-Expect but I wasn't able to compile that.

[chris@…]

Replying to wagner17:

Issue #1 = expensive tests are not being run "./tail-2/inotify-race: skipping test: very expensive: disabled by default"

After some trial and error, I was able to run the expensive tests by running "export RUN_EXPENSIVE_TESTS=yes" prior to running the listed command. I unset RUN_EXPENSIVE_TESTS after the tests.

I think you're a bit confused. LFS already says to do RUN_EXPENSIVE_TESTS=yes. The test you are referring to (as well as a few others) is labeled "very expensive," not just "expensive", and would require setting "RUN_VERY_EXPENSIVE_TESTS=yes."

[bdubbs@…]

The tests run by LFS are basically confidence tests. Many times some developer tests are skipped due to a lack of prerequisites or other factors. A skipped test is not an error. If a user wants to run all tests as a developer, then those should be done after a full system is installed, not in Chapter 6.