-
Notifications
You must be signed in to change notification settings - Fork 1
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
JOSS: unit tests #35
Comments
During compilation I also ran into this problem: catchorg/Catch2#2421. |
I have a similar compilation error (and a few warnings) with
|
is a series of power-assignments, ending up with Will be fixed in a new branch 🆗 |
Alright, I have added |
Fixed on branch |
Works 👍 |
The compile time Catch2 error is now gone (in revision branch) but now I am getting a runtime |
For your reference this is the report from sanitizer
|
We are not getting any errors, neither in CI nor at the Gitpod test I yesterday added. EDIT:Do you get any errors when commenting out |
I was running the commands as posted in the comment above #35 (comment) |
Also it would be helpful to add in the documentation detailed instructions on how to build and run the tests locally. |
With the following information:
I am going to conclude that this is not a problem with the library itself, rather the stack size limit - exceeded by recursive calls of multiplications of big hypercomplex numbers. Seems other ppl experienced this issue too. Strangely enough valgrind did not report any errors. Moreover, this Documentation updated: I added one more line how to run the unit test script to test the installation. It is much easier to exclude test cases in Catch2 than to specify "to include all others by default". I have made sure that in all places I run unit test script I have Given both reviewers approved on the changes in the comments above I consider this thread finished. The issue will be closed on PR merge. For further revision please create new issues. |
While reviewing for JOSS (openjournals/joss-reviews#5272), I encountered the following errors in the unit tests:
After changing L1553 to Polynomial<9>, I got this output:
The text was updated successfully, but these errors were encountered: