-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dxtbx.serialize.filename.resolve_path
fails on Windows for data collected on a POSIX platform
#613
Comments
Actually it seems like this is delegated back to a
|
Ok, where it goes wrong is here: dxtbx/src/dxtbx/serialize/filename.py Lines 6 to 24 in 17a0af3
On entry:
Then
Finally,
|
Sorry, not quite right (I hate debugging on Windows). It's just the action of
|
ImageSet.get_path
broken on Windowsdxtbx.serialize.filename.resolve_path
fails on Windows for data collected on a POSIX platform
What is the intended behaviour of |
- Using prebuild CCTBX and the CMake builds of dxtbx and dials - Relax python-nunit constraint, which now causes errors fixed in the now-latest version of the package - XFail two tests that are failing on windows because of cctbx/dxtbx/issues/613
While investigating the DIALS test failure
tests/util/test_image_grouping.py::test_real_h5_example
on Windows, I found thatImageSet.get_path
gives a strange result on that platform. This can be demonstrated using thedtpb_serial_processed
dataset on dials-data, like this:Linux
Windows
This causes the test to fail here:
The text was updated successfully, but these errors were encountered: