Re: [Bug-tar] sparse05.at with low disk space causes all later tests to fail

[Nathan Stratton Treadway]

On Fri, Mar 18, 2016 at 14:31:59 -0400, Nathan Stratton Treadway wrote:
> Specifically, my partition started out with 2.3G free.  The test tried
> to run, and managed to create a BIGFILE 4893794304 bytes in listed size
> before the partition filled up... at which point the test failed with:
> 
>   ./testsuite: line 1584: echo: write error: No space left on device 
>   142. sparse05.at:21: 142. listing sparse files bigger than 2^33 
> B(sparse05.at:21): FAILED (sparse05.at:31) 
> 

I noticed that testsuite line 1584 is actually the "case 77" line from
the at_fn_check_status() function -- or, in other words, the testsuite
script is getting the write error when it's trying to process the
AT_SKIP_TEST exit status from the sparse05.at test.

I tried the attached patch, which deletes the existing BIGFILE if the
attempt to create it ends with an error status.  It seemed to correctly
allow the test to go forward if the BIGFILE creation succeeds but skip
it (and allow later tests to proceed normally) if not.


I see that when the test is able to run successfully, BIGFILE's real
size is 9.76+ GiB ... and when it fails it can easily take more than 10
minutes to fill up the partition before aborting.  So I wonder if there
is any (portable) way to have the test check for free space right at the
start, and SKIP without trying to create BIGFILE if there's isn't
enough?

                                                Nathan


----------------------------------------------------------------------------
Nathan Stratton Treadway  -  address@hidden  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

gnutar_sparse05.at.patch
Description: Text Data