#6636: cvs-1.11.23: test suite problems and command explanations missing
--------------------+-------------------------
 Reporter:  fo      |      Owner:  blfs-book@…
     Type:  defect  |     Status:  new
 Priority:  normal  |  Milestone:  7.8
Component:  BOOK    |    Version:  SVN
 Severity:  normal  |   Keywords:
--------------------+-------------------------
 Test suit fails at basicb-21, less than 1 SBU from start. It is supposed
 to run for over one hour.

 I am using --with-rsh=ssh.

 This can be fixed by

 
[https://projects.archlinux.org/svntogit/packages.git/plain/trunk/cvs-1.11.23-sanity.patch?h=packages/cvs]

 Unfortunately, again, after a loooong time, it hangs for ate least two
 reasons.

 It tries to do an ssh connection to 127.0.0.1.

 First, I was in one terminal, following ''check.log'', because during the
 test no message goes to the console and didn't notice, when the standard
 ssh trust question appeared in the other terminal. After ''yes'', message
 was the expected ''broken pipe''.

 Second, it started asking my password and repeated about 10 times, and I
 stopped the test.

 One more problem is that the sed expression


 {{{
 's/g=rw,o=r$/g=r,o=r/'
 }}}

 does nothing.

 I replaced by

 {{{
 's/g=rw,o=rw/g=r,o=r/'
 }}}

 but have no idea if it is correct. Perhaps that is the reason for the hung
 up.

 Perhaps, the switches discussed for the tests and in Optional
 dependencies:

 {{{
 --with-editor=<desired text editor>

 --with-rsh=ssh or empty (?)
 }}}

 should be mentioned in ''Command Explanations''.

 Also the text explaining the tests problems could be improved.

 I think this is all.

 Please, I would really prefer somebody else to confirm or unconfirm the
 problems and fix the issues.

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/6636>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to