[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44007] test tar changes working directory in
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #44007] test tar changes working directory in MXE-Octave ver 4.1.0+ |
Date: |
Fri, 16 Jan 2015 11:46:09 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30 |
Update of bug #44007 (project octave):
Status: None => In Progress
Assigned to: None => philipnienhuis
_______________________________________________________
Follow-up Comment #1:
A few issues in one.
1. Apparently the unwind_protect block doesn't work as advertised; the command
to restore the old working directory in the unwind_protect_cleanup block
doesn't get executed, that's
why you're left in the temp subdir.
As to why the unwind_protect block fails (the actual bug), at least in
Windows, I don't know.
2. The actual test (yet an xtest) fails in tar.m in the "system" command on
line 61.
That issue is that mingw tar doesn't like pathnames with a leading Windows
style drive letter ("C:\blahblah...") and backslash fileseps, but insists on
mingw style leading drive letters ("/c/blahblah...") and forward slash
fileseps.
I suppose that's one of those creepy issues in the Windows/Mingw/Linux blend
constituting MXE that the core devs (who mostly develop on *nix) just cannot
foresee :-)
Maybe this also holds for other archivers (gzip, zip) as well.
Investigating a bit further I get the impression that this might be an old bug
that only comes to light now that tests have been made for tar.m in 4.1.0+.
I'll first try to prepare a fix for the Windows side so that the call to
"system" in tar.m works in mingw. But there's a risk that it'll break
MSVC-compiled MXE Octave as I cannot rule out that tar.exe does accept "C:\"
style drive letters there.
If time permits, I'll also try to see if I can fix the "xtest" as well so that
it becomes a genuine "test".
Thanks for your report, Avinoam.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44007>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/