Skip to content
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

Tests failing for last merge #69

Closed
ZacharyWills opened this issue May 13, 2020 · 9 comments · Fixed by #71
Closed

Tests failing for last merge #69

ZacharyWills opened this issue May 13, 2020 · 9 comments · Fixed by #71

Comments

@ZacharyWills
Copy link
Contributor

Short description explaining the high-level reason for the new issue.

Current behavior

Tests run but fail

[----------] 1 test from ForcingTest
80
[ RUN ] ForcingTest.TestForcingDataRead
81
/home/Z/actions-runner/_work/_temp/1ac2add5-d50d-471a-994c-51763b638d59.sh: line 1: 5313 Segmentation fault (core dumped) ./cmake_build/test/test_all
82
##[error]Process completed with exit code 139.

Expected behavior

Tests should pass

Steps to replicate behavior (include URLs)

https://github.com/ZacharyWills/ngen/runs/671741082

Screenshots

@ZacharyWills
Copy link
Contributor Author

@ZacharyWills ZacharyWills reopened this May 18, 2020
@ZacharyWills
Copy link
Contributor Author

Screen Shot 2020-05-18 at 1 34 23 PM

@ZacharyWills
Copy link
Contributor Author

Tests are now failing to build, and do not make it to the run stage.

https://github.com/ZacharyWills/ngen/runs/691120396?check_suite_focus=true

@hellkite500
Copy link
Member

@ZacharyWills @jdmattern-noaa The issue is most likely the test data path is coded relative to the binary, so if the build doesn't make the binary in ngen/build/ or some other single subdir, the file isn't found, which causes a bug in Forcing.h to index a vector out of bounds.

@ZacharyWills
Copy link
Contributor Author

I changed the path to the root, which works manually but on attempting to get it to run automatedly I run into issues with include/core/catchment/giuh/GIUH.hpp

Not sure why and I'm going to keep dealing with the automation to try and get the tests to work at least. Any location on your caches locally? That would help

@ZacharyWills
Copy link
Contributor Author

Or post your local step-by-step and I can try it with no temp dir dancing.

@ZacharyWills
Copy link
Contributor Author

Tests are working macOS but not on Linux, I'll reference this here:#106 (comment)

@ZacharyWills
Copy link
Contributor Author

Conditions for closing this are simply one pass of tests passing for both platforms, that should suffice for compatibility.

@ZacharyWills
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants