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.

Sign up for GitHub

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

Jump to bottom

fortran unit tests need to run on systems other than yellowstone #1297

Closed
jedwards4b opened this issue Apr 3, 2017 · 7 comments
Closed

fortran unit tests need to run on systems other than yellowstone #1297

jedwards4b opened this issue Apr 3, 2017 · 7 comments
Assignees
@jgfouca
Labels
tp: unit tests ty: enhancement

Comments

@jedwards4b
Copy link
Contributor

This involves installing PFUNIT https://sourceforge.net/projects/pfunit/
@billsacks
Copy link
Member

See also #1141 - which includes instructions for building pFUnit.

@jgfouca jgfouca changed the title fortran unit tests need to run on systems other than yellowstone fortran unit tests need to run on systems other than yellowstone Apr 6, 2017
@jgfouca jgfouca added the ready label Apr 6, 2017
@billsacks
Copy link
Member

@jgfouca - note that with #1396 you'll just need to provide a serial build of pFUnit - not an mpi-enabled build like we needed in the past. I'm working on the documentation of how to build pFUnit and set up a new machine for unit testing, which I'll push to the documentation page soon.

@jgfouca
Copy link
Contributor

jgfouca commented Apr 20, 2017

ok, thanks

@jgfouca
Copy link
Contributor

jgfouca commented May 4, 2017

@billsacks did you finish the documentation for pfunit?

@billsacks
Copy link
Member

@jgfouca - yes, this documentation should be correct now:

http://esmci.github.io/cime/doc/build/html/users_guide/unit_testing.html#how-to-add-unit-testing-support-on-your-machine

@rljacob rljacob assigned erichlf and unassigned jgfouca May 23, 2017
@erichlf erichlf added Assigned and removed ready labels Jun 29, 2017
@erichlf erichlf assigned jgfouca and unassigned erichlf Aug 1, 2017
@jgfouca
Copy link
Contributor

jgfouca commented Aug 21, 2017

@billsacks that link gives me a 404

@billsacks
Copy link
Member

Try http://esmci.github.io/cime/users_guide/unit_testing.html#adding-machine-support

@jgfouca jgfouca added ready and removed Assigned labels Aug 25, 2017
@jgfouca jgfouca mentioned this issue Aug 28, 2017
Merged
@ghost ghost added in progress and removed ready labels Aug 28, 2017
jedwards4b added a commit that referenced this issue Aug 30, 2017
@jedwards4b
Merge pull request #1844 from ESMCI/jgfouca/get_pfunit_working_on_melvin
751fd7a 
Get PFUnit working on melvin.
Fix up serial settings in melvin.
Need to explicitly declare PFUNIT_PATH in cmake calls in run_tests.py
Need to load env before making env XML files, some compiler vars pull from environment
Need to not crash when CMAKE_Fortran_COMPILER_ID is empty
Test suite: scripts_regression_tests.py N_TestUnitTest
Test baseline:
Test namelist changes:
Test status: bit for bit

Fixes #1297

User interface changes?: N

Update gh-pages html (Y/N)?: N

Code review: @billsacks @jedwards4b (confirmed N_TestUnitTest still works on cheyenne)
@ghost ghost removed the in progress label Aug 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgfouca jgfouca

Labels
tp: unit tests ty: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@rljacob @erichlf @jedwards4b @billsacks @jgfouca