[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-cssc] CSSC test binary/auto.sh:fa11

From: Joerg Schilling
Subject: Re: [Bug-cssc] CSSC test binary/auto.sh:fa11
Date: Sun, 22 May 2011 21:35:37 +0200
User-agent: nail 11.22 3/20/05

James Youngman <address@hidden> wrote:

> > From everything you wrote, this test is expected to fail with both SCCS and
> > CSSC.
> At the time the test was written, I had not seen any version of SCCS
> which supported binary files and actually turned on encoding for this
> case.   IIRC, the behaviour I saw was mixed; probably some versions
> just failed and some generated an unencoded history file (that is,
> none automatically went to binary mode).   So I picked one behaviour
> and followed it.
> > Question: why do you write a test that aborts the test suite because it
> > would require SCCS to encode a _binary_ file as text file in order to pass?
> I'm pretty sure I was simply following the version of SunOS I was then
> mostly testing against.   Most of the early functional testing of CSSC
> was done either by comparison with SunOS 4.1.x by myself, or against
> other versions of Unix by volunteers.

>From my experiences and recent tests, this cannot have been SunOS.

If CSSC accepts files that include null bytes as text files (whis seems to be 
required to pass this test), then CSSC seems to have a bug.

BTW: I just run this test with "admin" from CSSC and it _did_ actually put the
file into s.test as unencoded textfile. This is definitely a bug in CSSC.

May be you now understand why tests should be run by all implementations and 
why it may hide problems if some of the tests are only run by CSSC.

Tests that should be run by a selected number of implementations are only tests 
for enhanced features, but this test did not check for an enhanced feature but 
for the presence of a bug. Neither UNIX diff nor gdiff deal with files 
containing null bytes, so you cannot create deltas against such a SCCS history 


 EMail:address@hidden (home) Jörg Schilling D-13353 Berlin
       address@hidden                (uni)  
       address@hidden (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily

reply via email to

[Prev in Thread] Current Thread [Next in Thread]