-
Notifications
You must be signed in to change notification settings - Fork 94
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
Draft: add windows test runner #133
Draft: add windows test runner #133
Conversation
af10773
to
585c0dc
Compare
This branch would add two Windows runners, one with WinGetOpt and one without. The tests are executed for the former. For d_tests are segfaulting. As pointed out in #108, reverting cf93 fixes the issue. |
8e0a117
to
86d443e
Compare
All 4 versions should be correct now. Do you still see segfaults? |
Thank you for the promt reply. I rebased this branch to include your changes and dropped the reversal of the problematic patch from pull request 117. Unfortunately, we get even more segfaults, not only for double but also for the other types. |
The tests are fine with Linux and MacOS. I have no experience with Windows, so I don't know what goes wrong with Windows. |
Well I hope you are not suggesting to ignore the error. To tackle the problem, I'd suggest to focus on the test code first, then maybe the SuperLU code. dtest crashes for Lines 94 to 101 in f530ef3
For One might be lucky and the memory at |
Valgrind also catches this correctly:
That 4 bytes before a block ... sounds a lot like accessing an integer array at index -1. @gruenich Maybe add valgrind to the Ubuntu workflow? BTW, the test command line was |
Hopefully the will be resolved later. I don't want to block related improvements and fixes.
86d443e
to
0559d56
Compare
Moving the segfault issue out of the merge request. I opened #134 for this. I hoped we can fix this here, but I don't want to block other improvements in this merge requests. I propose to merge this. |
Open issues:
Until #131 is merged, this based on top of this branch.