-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
test/functional/test_image.py::TestCompareXLSXFiles::test_image58 failure on 32bit architectures #441
Comments
Thanks for the report. I'll look into it. |
I see changes in 42700ea , which has failed CI tests. If the variable to be printed has fixed length (e.g., In the meanwhile, the dirty hack of |
That was just a WIP attempt before I went to bed. :-)
I don't think any of those suggestions work with ANSI-C (whether I should still try to support that is a separate question). Anyway, I went with a fix based on a double conversion/format. That will work in the integer range required for those large uint64_t offsets. The test case that was failing is more or less the maximum value for that attribute. I tested it on a 32bit ubuntu system. Could you try it when you get a chance. |
Thanks, I will try it and the rebuild result for all architectures will be available in 24 hours. |
Ok. Let me know if you need it in a new release. |
I have added a 32bit github action to hopefully catch issues like this in future. |
Thanks, the new patch seems to have fixed the bug. I don't mind having a new release; if you feel like postponing the release, I can always backport the patch only. |
I'm still accumulating fixes for a new release so it is probably best to work with the patch/fix for now. I'll let you know when there is an update. |
https://buildd.debian.org/status/fetch.php?pkg=libxlsxwriter&arch=armhf&ver=1.1.7-1%7Eexp1&stamp=1714910384&raw=0
The problem is the following code commit 31b3314 added in src/xmlwriter.c:
value
is now a 64bit variable, but it is printed aslong
which is 32bit.@hosiet FYI
The text was updated successfully, but these errors were encountered: