-
Notifications
You must be signed in to change notification settings - Fork 27
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
Segfaults in version 4.3 #164
Comments
FYI, I tried adding -DDEBUG_ALLOCATION as suggested in #109, but it looks like an
|
Not sure if it has something to do, but as I can see here, the tests are running on Python 3.9, which is not even an official release: platform linux -- Python 3.9.0b5, pytest-5.4.3, py-1.9.0, pluggy-0.13.1 The DEBUG_ALLOCATION macro it's meant to print some debug information from the C++ fract4dc extension, but I think it won't help here since the errors you are getting are not related to that extension (apparently). Nevertheless we need to review those missing includes. |
Hey @jamesjer, do you have any kind of metrics about the use of the package like how many downloads/installations has? |
Sorry for the delay. No, I'm afraid the Fedora project doesn't have any reliable way of collecting such metrics. It would be interesting information to have, but I'm afraid I can't provide it. I will try building with python 3.8 and see what happens. |
A python 3.8 build finished flawlessly on all architectures. I'll see if I can figure out why python 3.9 is having issues, but this does seem to point away from gnofract4d and towards python as the cause of the problem. |
This turns out to be a gnofract4d bug after all. See #166 for an explanation. |
I am the Fedora maintainer of the gnofract4d package. I am working on updating our package to gnofract4d 4.3, but am seeing segfaults in the test suite. You can see an example here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=48696332
The segfaults appear to be random; i.e., on this run, it was the arm and ppc64le builders that hit the issue. On other runs, it is a different architecture or architectures. The only commonalities I have noted are:
The text was updated successfully, but these errors were encountered: