[Octave-bug-tracker] [bug #42779] [OF] odswrite: "zip I/O error" when in different directory

[Philip Nienhuis]

Update of bug #42779 (project octave):

                  Status:               Confirmed => In Progress            

    _______________________________________________________

Follow-up Comment #2:

ATM (with io-2.2.2) this works OK on my Windows 7 box. But I'll check again on
Linux later. When I'm back home I can also try network drives.

I suspect timing issues play some role here. While in the relevant private ods
write routine the zip command is invoked using eval() and eval() is instructed
to wait for zip's output status, nobody knows if the low-level I/O invoked by
zip might be scheduled for later (viz. "lazy write"). So zip itself can easily
get confused.

FYI: the io package contains a few test routines; you can see that in
io_ods_testscript.m (and the overall test script test_spsh.m) several sleep()
commands had to be inserted to allow the script to run properly, i.e., to
avoid zip to stumble over its own feet.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?42779>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/