This is a quick fix to make the test suite green again. However, as you can see the path normalization handling has always been dependent on the adapter that you used. I wonder if we shouldn't rather remove these new tests to not make any misleading promises about how the resulting path will be represented.

Hm, very good point (and sorry that I missed the test failures).

Haven't looked into how these adapters are calling find, but from a naive approach on command line,find behaves exactly like the tests expect.

$ find ./../symfony -type d

Output:

..../../symfony/src..../../symfony/vendor...

Whether to remove the tests or not, depends on whether we agree Finder should fulfill their expectations.

The introduced expectations do make sense, as I pointed outhere.

But of course would be as well quite breaking for a bugfix version.

Last but not least, I haven't checked yet if the implementation would be reasonably doable at all.

I could help out in any direction, but obviously needs a decision from Symfony how to proceed.

seehttps://github.com/symfony/symfony/blob/2.7/src/Symfony/Component/Finder/Adapter/AbstractFindAdapter.php#L42 whererealpath() is called

Well, these adapters are deprecated though.

But rather than usingrealpath, these adapters could normalize paths by resolving../ parts in the path (removing the previous part of the path).

see /src/Symfony/Component/Finder/Adapter/AbstractFindAdapter.php@2.7#L42 whererealpath() is called

Hm, ok. Don't know why this was added. Can't confirm thatfind won't work for paths with../ in it.

Well, these adapters are deprecated though

Ah OK, then I would just go with skipping these tests, as the adapters are gone in master anyway.

Thank you@xabbuh.

Thanks@nicolas-grekas@xabbuh and everybody else involved.