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

Tighten tolerance for test that fails after compiler change #265

Closed
wants to merge 1 commit into from

Conversation

aeslaughter
Copy link
Contributor

(refs #183)

@aeslaughter
Copy link
Contributor Author

I was just trying to see if I could improve these quickly, I think there is more work do be done. Do you really need to test so many timesteps?

@cbolisetti
Copy link
Contributor

I'm still surprised this is failing with such tight tolerance. We might be able to reduce the number of time steps. My moose/mastodon are broken right now and Im not sure why. I'll take another look at it later.

@aeslaughter
Copy link
Contributor Author

Perhaps the timestep tolerance is the real culprit.

@aeslaughter
Copy link
Contributor Author

This can be re-opened when needed.

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 this pull request may close these issues.

2 participants