parallel: Bug fixed if first jobs fills $TMPDIR. Passes testsuite.

This commit is contained in:
Ole Tange 2013-12-21 01:49:17 +01:00
parent bfb01e89df
commit f1ad123e52
5 changed files with 15 additions and 8 deletions

View file

@ -5071,7 +5071,9 @@ sub set_exitsignal {
} }
my $pos = tell $disk_full_fh; my $pos = tell $disk_full_fh;
print $disk_full_fh "x"x8193; print $disk_full_fh "x"x8193;
if(tell $disk_full_fh == $pos) { if(not $disk_full_fh
or
tell $disk_full_fh == $pos) {
::error("Output is incomplete. Cannot append to buffer file in \$TMPDIR. Is the disk full?\n"); ::error("Output is incomplete. Cannot append to buffer file in \$TMPDIR. Is the disk full?\n");
::error("Change \$TMPDIR with --tmpdir.\n"); ::error("Change \$TMPDIR with --tmpdir.\n");
::wait_and_exit(255); ::wait_and_exit(255);

Binary file not shown.

View file

@ -3646,7 +3646,8 @@ installed software that is not in the VirtualBox images.
If you cannot reproduce the error on any of the VirtualBox images If you cannot reproduce the error on any of the VirtualBox images
above, you should assume the debugging will be done through you. That above, you should assume the debugging will be done through you. That
will put more burden on you and it is extra important you give any will put more burden on you and it is extra important you give any
information that help. information that help. In general the problem will be fixed faster and
with less work for you if you can reproduce the error on a VirtualBox.
=head1 AUTHOR =head1 AUTHOR

View file

@ -3870,7 +3870,7 @@ should preferably be small and simple. A combination of @strong{yes},
your example requires large files, see if you can make them by your example requires large files, see if you can make them by
something like @strong{seq 1000000} > @strong{file} or @strong{yes | head -n 10000000} > something like @strong{seq 1000000} > @strong{file} or @strong{yes | head -n 10000000} >
@strong{file}. If your example requires remote execution, see if you can @strong{file}. If your example requires remote execution, see if you can
use @strong{localhost}. use @strong{localhost} - maybe using another login.
@item The output of your example. If your problem is not easily reproduced @item The output of your example. If your problem is not easily reproduced
by others, the output might help them figure out the problem. by others, the output might help them figure out the problem.
@ -3893,7 +3893,8 @@ installed software that is not in the VirtualBox images.
If you cannot reproduce the error on any of the VirtualBox images If you cannot reproduce the error on any of the VirtualBox images
above, you should assume the debugging will be done through you. That above, you should assume the debugging will be done through you. That
will put more burden on you and it is extra important you give any will put more burden on you and it is extra important you give any
information that help. information that help. In general the problem will be fixed faster and
with less work for you if you can reproduce the error on a VirtualBox.
@chapter AUTHOR @chapter AUTHOR
@anchor{AUTHOR} @anchor{AUTHOR}

View file

@ -1,13 +1,16 @@
testsuite: ../src/parallel tests-to-run/* wanted-results/* prereqlocal startdb prereqremote testsuite: 3
time sh Start.sh || true true
date
make stopvm
3: ../src/parallel tests-to-run/* wanted-results/* startdb prereqlocal prereqremote 3: ../src/parallel tests-to-run/* wanted-results/* startdb prereqlocal prereqremote
TRIES=3 time sh Start.sh || true TRIES=3 time sh Start.sh || true
date date
make stopvm make stopvm
1: ../src/parallel tests-to-run/* wanted-results/* prereqlocal startdb prereqremote
time sh Start.sh || true
date
make stopvm
testdb: ../src/parallel tests-to-run/*sql* wanted-results/*sql* prereqdb testdb: ../src/parallel tests-to-run/*sql* wanted-results/*sql* prereqdb
time sh Start.sh sql time sh Start.sh sql
date date