On 06/01/2018 09:59 AM, Ken Moffat wrote:
What goes around comes around :-(

A year ago (well technically it was 2nd June), my build of the vim
version/patches we were using at that time started to hang at the
end of the tests, so I stopped running the tests.

On 1st March I decided to retry the tests and it was back to normal
(failed, but exited).

Today I've just had my first build of 8.1.  I had interpreted the
book as suggesting all tests might pass, so I removed my '|| true'
after the test invocation:

   Vim: Error reading input, exiting...^M
^M
Vim: Finished.^M
^[[24;1Hmake[2]: *** [Makefile:81: test44.out] Error 1
make[2]: *** Waiting for unfinished jobs....

similarly tests 39, 29, 14.

So, I reinstated '|| true' in my package script.  That then got as
far as the end:

# Check if the test.out file matches test.ok.
2,7c2,33
< ×<91>
[snip a lot, it thinks the files differ]
. line 12 ZYXWVUTSRQPONMLKJIHGREDCBA9876543210 12
rm -rf X* test.ok viminfo
make[2]: Leaving directory '/building/vim81/src/testdir'

And at that point it again hung.  Trying to stop the main script for
chapter 6 with Ctrl-C failed, but I was able to find the process for
the package script and kill that.

As you know, I test LFS packages in jhalfs. I did get an error in the chroot environment:

From test_terminal.vim:
Found errors in Test_terminal_composing_unicode():

and a lot of things like

Pattern 'echo abc ̈' does not match 'がぎぐげご'

I attributed that to not building all of the glibc locales.

I have not 'test44' in my log at all.

-------

Testing with a full environment, I just ran 'make test' I did not capture a test log, but the tests appear to pass and not hang. I did run the test over ssh.

Since I use konsole, it is relatively simple to save the screen output after the tests complete. Grepping (is that a word?) that output for Error only gives:

Executing Test_CmdErrors()

  -- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to