array aligned on a different byte-boundary than reported by dtype.alignment (travis-ci)
![](https://secure.gravatar.com/avatar/bf402f309d40d607a369395e32a984fc.jpg?s=120&d=mm&r=g)
I'm running some test code on travis-ci, which is currently failing, but passing locally. I've identified the problem as being that my code tests internally for the alignment of an array being its "natural alignment", which I establish by checking "data_pointer%test_array.dtype.alignment" (I do this actually on the pointer in Cython, but the same is true if I check .ctypes.data). The issue I'm having is that the array that is being created inside the travis-ci environment is _not_ naturally aligned. I don't do anything funny in creating the array - it comes from a .copy() of another array. Specifically, the problem is that .dtype.alignment is reporting 32 on a complex256 array, but the actual alignment is 16. My machine (running a much more up to date Ubuntu installation) reports 16 for the .dtype.alignment attribute on a similar array. Is this something that can be expected in some situation? Is there an explanation? Is this a bug? Cheers, Henry p.s. The error is raised here: https://github.com/hgomersall/pyFFTW/blob/travis-debug/pyfftw/pyfftw.pyx#L79... through https://github.com/hgomersall/pyFFTW/blob/travis-debug/pyfftw/builders/_util... in which the problematic input array is simply created as in https://github.com/hgomersall/pyFFTW/blob/travis-debug/test/test_pyfftw_buil... With output: https://travis-ci.org/hgomersall/pyFFTW/jobs/14739340 (the last line)
participants (1)
-
Henry Gomersall