[C-prog-lang-l] phase 1 testing

[Jan Pechanec]

On Tue, 21 Apr 2020, Tomáš Sláma wrote:

>> I have two questions.  First, do you have the latest reversion of the
> > tests (c-prog-lang repo)? And the other one - do you see the same
> > errors when you use GNU tar as the implementation?  If not, please see
> > README on how to do it.
>
> I do have the latest repository.
>
> As for checking the GNU tar implementation: it seems that I am unable to 
> (following the README tutorial), since it still looks for 'mytar.c', 
> even after setting STEF_REGFILE_LOCAL_VARS.
>
> The following script:
> ---
> #!/usr/bin/env fish 
>
>
> export STEF=/home/xiaoxiae/Documents/Temporary/tar/stef/stef.sh 
>
> export GNUTAR=/bin/tar 
>
> export STEF_REGFILE_LOCAL_VARS=" " 
>
> export MYGUTAR=/bin/tar 

s/MYGUTAR/MYGNUTAR/

Btw, in general, if something does not seem to be working, please see 
the test source code, fix it, and send me a pull request.

However, that's not this case :-)

Happy coding, Jan.

>
> 
>
> ./run-tests.sh (cat phase-1.tests)
> ---
>
> Yields:
> ---
> === [ NPRG099 Tar Unit Tests ] ===
> Checking configuration sanity.
> Checking existence of executables provided by the following variables: 
> GCC GNUTAR
> Checking existence of regular files provided by the following variables:
>
> --- [ Configuration Start ] ---
> Checking 'mytar.c' existence.
> The source code filename must be named: 'mytar.c'
> It is: 'set-me-to-mytar.c-see-README'
> Configuration failed, fix it and rerun.  Exiting.
> ---
>
> Sincerely,
> T. Sláma
>
> On 4/21/20 12:12 PM, Jan Pechanec wrote:
>> On Mon, 20 Apr 2020, Tomáš Sláma wrote:
>> 
>>> Hello,
>>>
>>> I've been working on my implementation of GNU TAR and got to a point
>>> where some of the test are still failing but they (in my opinion)
>>> shouldn't be.
>> 
>> Hi,
>> 
>> I have two questions.  First, do you have the latest reversion of the
>> tests (c-prog-lang repo)? And the other one - do you see the same
>> errors when you use GNU tar as the implementation?  If not, please see
>> README on how to do it.
>> 
>> If all tests pass with GNU tar then you will need to fix your
>> implementation.  Let us know if that's not the case.
>> 
>> Thanks, Jan.
>> 
>>   >
>>> Here's the condensed diff of those (2, 3, 4, 5, 6) that failed:
>>>
>>> -------------------------------------------
>>>
>>> 002
>>> ---
>>>   aaa-file
>>>   another-file2
>>>   empty.data
>>> -file.zero
>>>   file1.random
>>>   file2.zero
>>>   file3.zero
>>> +file.zero
>>>   hello-world
>>>   small-file
>>> ---
>>>
>>> 003
>>> ---
>>>   aaa-file
>>>   empty.data
>>> -file3.zero
>>> +file.zero
>>>   small-file
>>> ---
>>>
>>> 004
>>> ---
>>>   aaa-file
>>>   empty.data
>>> -file3.zero
>>> +file.zero
>>>   small-file
>>> ---
>>>
>>> 005
>>> ---
>>>   aaa-file
>>>   empty.data
>>> -file3.zero
>>> +file.zero
>>>   small-file
>>>   mytar: nonexistent1: Not found in archive
>>>   mytar: nonexistent2: Not found in archive
>>> ---
>>>
>>> 006
>>> ---
>>>   aaa-file
>>>   empty.data
>>> -file3.zero
>>> +file.zero
>>>   small-file
>>>   mytar: nonexistent1: Not found in archive
>>>   mytar: nonexistent2: Not found in archive
>>> ---
>>>
>>> -------------------------------------------
>>>
>>> I tried printing the bash variables from test-00x.sh variables and it
>>> seems that they don't match the test-output-00x.txt files. Am I missing
>>> something?
>>>
>>> Thanks (and sorry, if it's just me being confused :) )!
>>>
>>> T. Sláma
>>> _______________________________________________
>>> c-prog-lang-l mailing list
>>> c-prog-lang-l at mff.cuni.cz
>>> http://mbox.ms.mff.cuni.cz/listserv/listinfo/c-prog-lang-l
>>>
>> 
>> 
>> _______________________________________________
>> c-prog-lang-l mailing list
>> c-prog-lang-l at mff.cuni.cz
>> http://mbox.ms.mff.cuni.cz/listserv/listinfo/c-prog-lang-l
>> 
> _______________________________________________
> c-prog-lang-l mailing list
> c-prog-lang-l at mff.cuni.cz
> http://mbox.ms.mff.cuni.cz/listserv/listinfo/c-prog-lang-l
>

-- 
Jan Pechanec <jp (at) devnull (dot) cz>
http://www.devnull.cz