-
Notifications
You must be signed in to change notification settings - Fork 99
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
got rid of travis stuff and added github actions badge to readme #729
Conversation
Exit code 134 on shallow spheres again. Stack overflow says this could mean buffer overflow? Oh dear. This has been broken a long time and deprioritized due to build system rework and CI migration. Doesn't seem like an easy fix, and the discussion over at #642 was inconclusive. This PR puts a big red reminder on the readme. I think that test should either be chased all the way down or be considered permanently broken and taken out of the flow. |
I do not think we should take it out but chase it down. Feel free to take the initiative if you are interested and you can reproduce the problem we can step through figuring out what is wrong. |
I'm not very interested lol. I'm only interested in
|
Okay, I actually was curious enough to run the pytests. I'm on a Mac, but old enough to be Intel silicon. I got a failure, but I don't think it's the same one. Interestingly, there are warnings for the shallow water test. Maybe the segfault has to do with taking the sqrt of a negative or something?
|
The problem above is a numerical artifact probably leading to a root of a negative number due to a near vacuum state. Almost certainly not anything related to a buffer overflow. The shallow water problem could be a memory problem. I would not say it has been deprioritized or that it is a build system problem though. Rather it has been hard to debug as most of the able developers have not been able to reproduce the problem. |
Thanks, @pavelkomarov . The test failure looks like a small enough difference to be due to rounding errors and not a code issue. We could loosen the test tolerance slightly to avoid this popping up. Please, let's keep discussion of the shallow water on the sphere test here: #642. Otherwise it gets too hard to track all of what is said. |
I was keeping some of this old Travis stuff around as a reminder that we still need to get parallel tests running on Github actions, but it's a good idea to remove these files so I've raised an issue as a reminder: #733. |
I heard we're not using travis anymore. Just some clean up.