| 2015-01-10 18:02:26 |
Mark Harmer |
description |
Running the DirUtilTests under Windows produces the following failures:
./src/dir-util-test.h:29: Error: Expected (result == std::string(cases[i][2])), found ("/foo/bar" != "bar")
./src/dir-util-test.h:29: Error: Expected (result == std::string(cases[i][2])), found ("/foo/bar/baz" != "bar/baz")
./src/dir-util-test.h:29: Error: Expected (result == std::string(cases[i][2])), found ("/foo/bar/baz" != "foo/bar/baz")
This appears to be a result of assumptions made on the path separators.
I've attached a patch that resolves this failure under Windows. |
Running the DirUtilTests under Windows produces the following failures:
./src/dir-util-test.h:29: Error: Expected (result == std::string(cases[i][2])), found ("/foo/bar" != "bar")
./src/dir-util-test.h:29: Error: Expected (result == std::string(cases[i][2])), found ("/foo/bar/baz" != "bar/baz")
./src/dir-util-test.h:29: Error: Expected (result == std::string(cases[i][2])), found ("/foo/bar/baz" != "foo/bar/baz")
This appears to be a result of assumptions made on the path separators.
I've attached a patch that resolves this failure under Windows.
Reproduce Steps:
1. Run 'btool check' on the source checked out in Windows
2. This builds and runs the full CxxTest unittests, observe 10 test failures at the end. With the supplied patch this should drop to 9.
I wasn't able to specify the individual test directly with the cxxtests executable created so the output will be polluted with other tests that are failing. |
|
