Error in Path Constraints

[Charlie Poole]

SamePathConstraint reports all of the following as being the same path

/path/to/assembly/
/path/to/assembly
path/to/assembly
//path/to/assembly
/path//to/assembly (invalid path, of course)

Only the first two should be equivalent

This is due to an error in the PathConstraint.Canonicalize method, which disregards all "extra" separators, including those at the beginning and the end of a path. Only an extra slash at the end of a path should be ignored.

[Jv (jv-ravichandran)]

Why is it changed to "In Progress" when the fix was committed?

On Sun, Dec 23, 2012 at 6:10 AM, Charlie Poole <email address hidden> wrote:

> ** Changed in: nunitv2
> Status: Triaged => In Progress
>
> --
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
> https://bugs.launchpad.net/bugs/1071861
>
> Title:
> Error in Path Constraints
>
> Status in NUnit Test Framework:
> Triaged
> Status in NUnitLite Testing Framework:
> Fix Committed
> Status in NUnit V2 Test Framework:
> In Progress
>
> Bug description:
> SamePathConstraint reports all of the following as being the same path
>
> /path/to/assembly/
> /path/to/assembly
> path/to/assembly
> //path/to/assembly
> /path//to/assembly (invalid path, of course)
>
> Only the first two should be equivalent
>
> This is due to an error in the PathConstraint.Canonicalize method,
> which disregards all "extra" separators, including those at the
> beginning and the end of a path. Only an extra slash at the end of a
> path should be ignored.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunit-3.0/+bug/1071861/+subscriptions
>

--
Regards,

*Ravichandran J.V.*
http://ravichandranjv.blogspot.com
XO 1.75 - 12.1, 0.96, Build 21, Q4D17

[Charlie Poole (charlie.poole)]

If you look above, you'll see the bug applies to three different projects and has a different status in each.