-
Notifications
You must be signed in to change notification settings - Fork 166
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
Fixes SEGFAULT in integration_tests/elemental_01.py #2451
Conversation
Someone please help with failing checks, here's some information from a failing check: LPython CI / LPython CI (3.10, ubuntu-latest) (pull_request):
Do I need to change some hash? |
These tests don't fail on CI though. Check |
Sorry, I'm unable to understand. I cloned the |
Which OS, do you use? |
I use Ubuntu 22.04.3 LTS |
Any updates on this? |
If we are having memory overflow, then let's create smaller arrays. I would however keep the original types, to ensure they keep working. |
Should I change the test to one with smaller arrays and the original datatype as suggested? |
I think I accidentally closed this. |
Yes, I would do that. Make sure it works on your machine. If CI passes, then we can merge it. |
This change gets rid of the segfault, but ./runtests.py (in lpython directory) gives me this hash error, please let me know how the hashes are updated / how the reference files are updated. |
Please check this PR: #2452 Also, I noticed that the instructions given in README for Linux don't include |
Closing this PR as #2452 has been merged. Thanks! |
On running /integration_tests/run_tests.py, a SEGFAULT error occurs and the test fails:
Upon careful experimentation, I found that this is due to lines 106 and 107 in file elemental_01.py, where creating very large arrays of f64[256,64,16] causes memory overflow. The lines causing the issue are:
I have changed the datatype to f32 where needed. This allows the required large arrays can be created and tested. Alternatively, we can increase the memory limit of the test.