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

testreporter not catching failing NCK tests #1555

Closed
fischer-ncar opened this issue May 17, 2017 · 1 comment
Closed

testreporter not catching failing NCK tests #1555

fischer-ncar opened this issue May 17, 2017 · 1 comment
Assignees
Labels
Responsibility: CESM Responsibility to manage and accomplish this issue is through CESM tp: script tools ty: Bug

Comments

@fischer-ncar
Copy link
Contributor

The testreporter isn't parsing TestStatus correctly to report failed NCK tests.

@fischer-ncar fischer-ncar self-assigned this May 17, 2017
@fischer-ncar
Copy link
Contributor Author

fischer-ncar commented May 17, 2017

Need to add a check for "COMPARE_base_multiinst". Also need to add "COMPARE_base_test" and "COMPARE_base_single_thread"

@fischer-ncar fischer-ncar added the Responsibility: CESM Responsibility to manage and accomplish this issue is through CESM label May 17, 2017
@rljacob rljacob added in progress and removed ready labels May 25, 2017
jedwards4b added a commit that referenced this issue May 25, 2017
Update testreporter and change hobart queue to medium.
Update testreporter.py to handle compare failures that were being missed.
Remove tagname from the testdb comments that were added to the GENERATE and
BASLINE lines in TestStatus.
Change the default queue on hobart from short to medium to handle tests that were
running a little long.

Test suite: scripts_regression_tests.pr, populated testdb for alpha06m
Test baseline:
Test namelist changes:
Test status: bit for bit,

Fixes #1555

User interface changes?:

Code review:jedwards
@ghost ghost removed the in progress label May 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Responsibility: CESM Responsibility to manage and accomplish this issue is through CESM tp: script tools ty: Bug
Projects
None yet
Development

No branches or pull requests

3 participants