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

cleaned up lean mode build and test suite #1578

Merged
merged 1 commit into from Sep 30, 2015

Conversation

@doutriaux1
Copy link
Contributor

@doutriaux1 doutriaux1 commented Sep 30, 2015

fix #1575

@doutriaux1
Copy link
Contributor Author

@doutriaux1 doutriaux1 commented Sep 30, 2015

@sankhesh @aashish24 @dnadeau4 please review and merge

@doutriaux1
Copy link
Contributor Author

@doutriaux1 doutriaux1 commented Sep 30, 2015

@aashish24 @sankhesh @dnadeau4 should be good to merge

sankhesh added a commit that referenced this issue Sep 30, 2015
…ests_triggered

cleaned up lean mode build and test suite
@sankhesh sankhesh merged commit d10a675 into master Sep 30, 2015
7 of 9 checks passed
@sankhesh sankhesh deleted the issue_1575_lean_mode_too_many_tests_triggered branch Sep 30, 2015
@aashish24
Copy link
Contributor

@aashish24 aashish24 commented Sep 30, 2015

LGTM 👍 should we add a buildbot for leanmode?

@durack1
Copy link
Member

@durack1 durack1 commented Sep 30, 2015

@doutriaux1 the pcmdi10.llnl.gov - redhat7.1 machine is available and could be configured for LEAN..

@doutriaux1
Copy link
Contributor Author

@doutriaux1 doutriaux1 commented Sep 30, 2015

@aashish24 we already have one that's how I saw that it doesn't work, see: https://github.com/UV-CDAT/uvcdat/pull/1578/commits#

@doutriaux1
Copy link
Contributor Author

@doutriaux1 doutriaux1 commented Sep 30, 2015

@aashish24 this is what we have:

cont-int/LLNL/Linux-annie Ubuntu 15.04 (FULL/MESA) 
cont-int/LLNL/Darwin-Mac 10.10.5 (LEAN) 
cont-int/LLNL/Darwin-Mac1 10.10.5 (NOGUI) 
cont-int/LLNL/Darwin-Mac2 10.10.5 (FULL)
cont-int/LLNL/Linux-crunchy RH6 (FULL) 
cont-int/LLNL/Linux-oceanonly RH6 (MESA/NOGUI) 

@aashish24
Copy link
Contributor

@aashish24 aashish24 commented Oct 1, 2015

Cool!.. @doutriaux1 thanks. Should we document it somewhere?

@doutriaux1
Copy link
Contributor Author

@doutriaux1 doutriaux1 commented Oct 1, 2015

Hum... I don't know I guess it builds the user confidence to know it's systematically tested. @chaosphere2112 @mattben where do you think we should put this information?

@chaosphere2112
Copy link
Contributor

@chaosphere2112 chaosphere2112 commented Oct 1, 2015

@doutriaux1 That looks like the kind of information that would work nicely on the wiki, since it'll probably get updated over time.

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

Successfully merging this pull request may close these issues.

5 participants