-
-
Notifications
You must be signed in to change notification settings - Fork 555
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
Bug fix: Improve cracking integration tests and examples on M-series hardware #3372
Conversation
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3372 +/- ##
========================================
Coverage 99.58% 99.58%
========================================
Files 256 256
Lines 19998 19998
========================================
Hits 19915 19915
Misses 83 83 ☔ View full report in Codecov by Sentry. |
Lychee error is corrected in #3373 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks! It seems that the Lychee workflow is still causing problems, but that doesn't appear to be caused by the changes in this pull. It looks like there is a conflict to resolve, but as discussed in the dev meeting let's merge this fix and keep #3140 open.
Yeah lychee was unrelated to this change. I will fix the conflict so it can be merged. |
@BradyPlanden Should be good to go after the tests pass. It all worked locally after the merge |
Description
On apple m-series hardware, the cracking simulations fail in the examples and integration tests. The error message suggested adjusting dt_max, but I did not get that working. What worked instead was adjusting the size of the mesh used in the simulation. This change does not address the root cause of the issue, but can make the tests run. Having failing tests makes it difficult to see if new changes are causing issues.
Original:
New:
Related #3140
Type of change
Minor adjustment to the integration tests and examples to improve compatibility for Mac.
Key checklist:
$ pre-commit run
(or$ nox -s pre-commit
) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)$ python run-tests.py --all
(or$ nox -s tests
)$ python run-tests.py --doctest
(or$ nox -s doctests
)You can run integration tests, unit tests, and doctests together at once, using
$ python run-tests.py --quick
(or$ nox -s quick
).Further checks: