-
Notifications
You must be signed in to change notification settings - Fork 8
Update to GT4Py v1.1.4 #1018
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
base: main
Are you sure you want to change the base?
Update to GT4Py v1.1.4 #1018
Conversation
|
|
||
| # TODO(havogt): import will disappear after FieldOperators support `.compile` | ||
| from gt4py.next.ffront.decorator import FieldOperator | ||
| from gt4py.next.instrumentation import metrics as gtx_metrics |
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.
Mentioning this here so I don't forget. We have to check that the json file which is output by pytest-benchmark includes the gt4py metrics as before
Co-authored-by: Till Ehrengruber <till.ehrengruber@cscs.ch>
|
cscs-ci run default |
|
cscs-ci run distributed |
|
cscs-ci run dace |
|
cscs-ci run dace |
|
cscs-ci run default |
|
cscs-ci run dace |
|
cscs-ci run default |
|
cscs-ci run dace |
|
Mandatory Tests Please make sure you run these tests via comment before you merge!
Optional Tests To run benchmarks you can use:
To run tests and benchmarks with the DaCe backend you can use:
To run test levels ignored by the default test suite (mostly simple datatest for static fields computations) you can use:
For more detailed information please look at CI in the EXCLAIM universe. |
|
cscs-ci run dace |
No description provided.