-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix test references (assuming wrap around) #270
Conversation
launch jenkins spack |
launch jenkins icon |
launch jenkins spack spackProject=halungge/icon4py-merge-greenline-in-main |
launch jenkins spack spackProject=C2SM/icon4py_rebase |
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.
ILGTM
Mandatory Tests Please make sure you run these tests via comment before you merge!
Optional Tests In case your change might affect downstream icon-exclaim, please consider running
For more detailed information please look at CI in the EXCLAIM universe. |
This fixes test references where the current implementation assumes a certain behavior of the backend. Specifically, we used np.roll in the references and the backend (by chance) had the same wrap-around behavior. For an upcoming PR in GT4Py, we need to remove that expectation. --------- Co-authored-by: Jonas Jucker <jonas.jucker@c2sm.ethz.ch> Co-authored-by: juckerj <39263956+jonasjucker@users.noreply.github.com> Co-authored-by: Abishek Gopal <abishek.gopal@c2sm.ethz.ch>
This fixes test references where the current implementation assumes a certain behavior of the backend. Specifically, we used np.roll in the references and the backend (by chance) had the same wrap-around behavior. For an upcoming PR in GT4Py, we need to remove that expectation. --------- Co-authored-by: Jonas Jucker <jonas.jucker@c2sm.ethz.ch> Co-authored-by: juckerj <39263956+jonasjucker@users.noreply.github.com> Co-authored-by: Abishek Gopal <abishek.gopal@c2sm.ethz.ch>
This fixes some (not all) references where the current implementation assumes a certain behavior of the backend.
Specifically, we used np.roll in the references and the backend (by chance) had the same wrap-around behavior. For an upcoming PR in GT4Py, we need to remove that expectation.