Menu

#3631 fresh test failures

obsolete: 8.4.15
closed-invalid
2
2007-02-10
2007-01-25
Don Porter
No

These tests fail on
Fedora Core 6. I don't
believe they were failing
on the core-8-4-branch of
a few weeks ago.

==== fCmd-9.12 file rename: comprehensive: target exists FAILED
==== Contents of test case:

cleanup
file mkdir [file join td1 td2] [file join td2 td1]
if {$tcl_platform(platform) != "macintosh"} {
testchmod 555 [file join td2 td1]
}
file mkdir [file join td3 td4] [file join td4 td3]
file rename -force td3 td4
set msg [list [file exists td3] [file exists [file join td4 td3 td4]] [catch {file rename td1 td2} msg] $msg]
if {$tcl_platform(platform) != "macintosh"} {
testchmod 755 [file join td2 td1]
}
set msg

---- Result was:
1 1 1 {error renaming "td1" to "td2/td1": file already exists}
---- Result should have been (exact matching):
0 1 1 {error renaming "td1" to "td2/td1": file already exists}
==== fCmd-9.12 FAILED

==== fCmd-18.8 TclFileRenameCmd: rename dir on top of another empty dir w/ -force FAILED
==== Contents of test case:

catch {file delete -force -- tfa tfad}
file mkdir tfa tfad/tfa
file rename -force tfa tfad
set result [expr ![file isdir tfa]]
file delete -force tfad
set result

---- Result was:
0
---- Result should have been (exact matching):
1
==== fCmd-18.8 FAILED

Discussion

  • Don Porter

    Don Porter - 2007-01-26
    • priority: 5 --> 2
    • status: open --> pending-invalid
     
  • Don Porter

    Don Porter - 2007-01-26

    Logged In: YES
    user_id=80530
    Originator: YES

    It appears there have been no
    relevant changes to the
    core-8-4-branch in this interval,
    but the Fedora Core 6 system
    where testing was done has been
    "updated" in that time, so the
    fresh failures appear to originate
    in the system rather than in Tcl.

    Testing with the Tcl 8.4.14 release
    confirms this.

    These tests are disabled with the
    notNetworkFilesystem constraint
    in Tcl 8.5a6. When that disabling
    is undone, the same tests fail for
    Tcl 8.5a6 as well.

     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-invalid --> closed-invalid
     
MongoDB Logo MongoDB